The backward capability for management of env with old plugins

[Sergey Novikov]

Detailed bug description:
 Nailgun of stable/mitaka version cannot manage environments with plugins if them version is <= 3.
 After the upgrade of Fuel Master 8->9 the attempt to manage an existing env with plugin fails with 400 response code from Nailgun.

Example of steps to reproduce:
        1. Install fuel_plugin_example_v3 plugin on master node
        2. Create cluster with NeutronTUN network provider
        3. Enable plugin for created cluster
        4. Add 1 node with controller role
        5. Add 1 node with fuel_plugin_example_v3 role
        6. Add 3 node with compute+ceph roles
        7. Verify networks
        8. Deploy cluster
        9. Install fuel-octane package
        10. Create backup file using 'octane fuel-backup'
        11. Download the backup to the host
        12. Revert "upgrade_plugin_backup" snapshot
        13. Reinstall Fuel master using iso given in ISO_PATH
        14. Install fuel-octane package
        15. Upload the backup back to reinstalled Fuel maser node
        16. Restore master node using 'octane fuel-restore'
        17. Add 1 fuel_plugin_example_v3 node
        18. Verify networks
        19. Deploy cluster

Additional information:
 Probably the following bug is a consequence of this issue https://bugs.launchpad.net/fuel/+bug/1620215
 For more details please take a look at attached logs in https://bugs.launchpad.net/fuel/+bug/1620215

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/366182

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/365687
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=f1000e0e7636a04f2db1aa650ef0aab8978237ae
Submitter: Jenkins
Branch: master

commit f1000e0e7636a04f2db1aa650ef0aab8978237ae
Author: Georgy Kibardin <email address hidden>
Date: Mon Sep 5 17:42:15 2016 +0300

    Forbid legacy tasks only in LCM enabled clusters

    In case we inherit old clusters, without LCM, we must not check their
    plugins for legacy tasks to prohibit them.

    Change-Id: I23dcc48cc1321d38666b8bcf7d435abd70ac9b61
    Closes-Bug: #1620321

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/366182
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=a1651a150b67fa8bbb89aea9384bccfdec8fe356
Submitter: Jenkins
Branch: stable/mitaka

commit a1651a150b67fa8bbb89aea9384bccfdec8fe356
Author: Georgy Kibardin <email address hidden>
Date: Mon Sep 5 17:42:15 2016 +0300

    Forbid legacy tasks only in LCM enabled clusters

    In case we inherit old clusters, without LCM, we must not check their
    plugins for legacy tasks to prohibit them.

    Change-Id: I23dcc48cc1321d38666b8bcf7d435abd70ac9b61
    Closes-Bug: #1620321
    (cherry picked from commit f1000e0e7636a04f2db1aa650ef0aab8978237ae)

[Sergey Novikov (snovikov)]

Verified on snapshot #311 of MOS 9.1
For now test fails with another bug https://bugs.launchpad.net/fuel/8.0.x/+bug/1620215

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-web 10.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-web 10.0.0 release.