Wrong priority of ceph-osd task that leads to deployment failure

[Tatyanka]

http://jenkins-product.srt.mirantis.net:8080/job/6.1.ubuntu.bvt_2/90/
Case: deploy_ha_vlan
 1. Create cluster
 2. Add 3 nodes with controller roles
 3. Add 2 nodes with compute roles
 4. Set up cluster to use Network VLAN manager with 8 networks
 5. Deploy the cluster
 6. Run network verification
 7. Run OSTF

Deployment on node-3 failed with next errors in puppet manifest:
http://paste.openstack.org/show/166168/

As we can see ceph-osd task were executed first(but global task should go first)

But in astute.yaml from node-3 ceph-osd task have priority 100 - that leads to the it execution as a first task

http://paste.openstack.org/show/166174/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/152511

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/152511
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=2147da0c583a7944f440ceb51236e7cb2e6610c9
Submitter: Jenkins
Branch: master

commit 2147da0c583a7944f440ceb51236e7cb2e6610c9
Author: Aleksandr Didenko <email address hidden>
Date: Tue Feb 3 15:39:51 2015 +0200

    Fix ceph-osd task dependency

    Wrong ceph-osd task dependency causes wrong tasks ordering.

    Change-Id: If00a7b99fa56fa5788d7418b7f4a6974306aefcb
    Closes-bug: #1417579

[Andrew Woodward (xarses)]

We remove the requirement for running after a controller. Can you comment as to why we can run ceph-osd prior to the monitor being installed? it was bundled into the controller task. If it's been moved else where it still needs to be setup prior

[Aleksandr Didenko (adidenko)]

> Can you comment as to why we can run ceph-osd prior to the monitor being installed?

We do not run ceph-osd prior to the monitor. Here's a tasks group dependencies (roles ordering):
http://i.imgur.com/wFNIWYK.png

So ceph-osd is deployed after ceph-mon.

> it was bundled into the controller task.

It still is.

[Andrey Sledzinskiy (asledzinskiy)]

verified on {

    "build_id": "2015-02-15_22-54-44",
    "ostf_sha": "f9c37d0876141e1550eb4e703a8e500cd463282f",
    "build_number": "126",
    "release_versions":

{

    "2014.2-6.1":

{

    "VERSION":

{

    "build_id": "2015-02-15_22-54-44",
    "ostf_sha": "f9c37d0876141e1550eb4e703a8e500cd463282f",
    "build_number": "126",
    "api": "1.0",
    "nailgun_sha": "1e3a40dd8a17abe1d38f42da1e0dc1a6d4572666",
    "production": "docker",
    "python-fuelclient_sha": "61431ed16fc00039a269424bdbaa410277eff609",
    "astute_sha": "1f87a9b9a47de7498b4061d15a8c7fb9435709d5",
    "feature_groups":

            [
                "mirantis"
            ],
            "release": "6.1",
            "fuelmain_sha": "2054229e275d08898b5d079a6625ffcc79ae23b8",
            "fuellib_sha": "7f8d4382abfcd4338964182ebfea1d539f963e66"
        }
    }

},
"auth_required": true,
"api": "1.0",
"nailgun_sha": "1e3a40dd8a17abe1d38f42da1e0dc1a6d4572666",
"production": "docker",
"python-fuelclient_sha": "61431ed16fc00039a269424bdbaa410277eff609",
"astute_sha": "1f87a9b9a47de7498b4061d15a8c7fb9435709d5",
"feature_groups":

    [
        "mirantis"
    ],
    "release": "6.1",
    "fuelmain_sha": "2054229e275d08898b5d079a6625ffcc79ae23b8",
    "fuellib_sha": "7f8d4382abfcd4338964182ebfea1d539f963e66"

}

[Stanislaw Bogatkin (sbogatkin)]

This bug refers to granular deployment blueprint that was started to implement in 6.1 release. So, releases below 6.1 shouldn't be targeted for it.