Plugin can only be enabled for environments created _after_ it is installed

Bug #1572481 reported by Matthew Mosesohn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Julia Aranovich
Mitaka
Fix Released
High
Julia Aranovich

Bug Description

Detailed bug description:
 Newly installed plugins are not available to be used on environments that were created before the plugin is installed.
Steps to reproduce:
 Create an empty environment with default settings
 Do not even add any nodes
 Install example v3 plugin (updating metadata.yaml as needed if using 10.0)
 Go to settings tab for new environment and look for the plugin to install it
Expected results:
 Example plugin should be installable
Actual result:
 It isn't visible
Reproducibility:
 Always
Workaround:
 If you delete your environment and then create a new one, it is installable.
Impact:
 This impacts user expectations for "unlock settings tab" feature for 9.0.
Description of the environment:
 Operation system: <put your information here>
 Versions of components: <put your information here>
 Reference architecture: <put your information here>
 Network model: <put your information here>
 Related projects installed: <put your information here>
Additional information:
 <put your information here>

Changed in fuel:
milestone: none → 10.0
assignee: nobody → Fuel Python Team (fuel-python)
status: New → Confirmed
importance: Undecided → High
tags: added: area-python feature-plugins
Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/newton
tags: added: team-enhancements
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Bulat Gaifullin (bgaifullin)
Revision history for this message
Bulat Gaifullin (bulat.gaifullin) wrote :

seems like the issue on UI side. The nailgun returns the all installed plugins in cluster editable attributes. but UI does not show them.
Also I see the following error in browser console:

TypeError: undefined is not an object (evaluating 'initialAttributes[sectionName].metadata')
Seems like bug because {plugin_name} does not present in deployed attributes.

Changed in fuel:
assignee: Bulat Gaifullin (bgaifullin) → Fuel UI Team (fuel-ui)
Revision history for this message
Julia Aranovich (jkirnosova) wrote :

Bulat, the bug you described looks like a separate issue that affects deployed environment.
I moved it out to a separate ticket: https://bugs.launchpad.net/fuel/+bug/1572906

tags: added: area-ui
removed: area-python
Changed in fuel:
assignee: Fuel UI Team (fuel-ui) → Julia Aranovich (jkirnosova)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-ui (stable/mitaka)

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

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-ui (master)

Reviewed: https://review.openstack.org/308903
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=0174716204af47e1a9e0011e983b9940b6eede63
Submitter: Jenkins
Branch: master

commit 0174716204af47e1a9e0011e983b9940b6eede63
Author: Julia Aranovich <email address hidden>
Date: Thu Apr 21 19:14:09 2016 +0300

    Support installing of new plugins to existing environment

    * hasChanges method of Settings model is fixed to support environment
      plugins which are installed after the environment creation or
      environment deployment

    Closes-Bug: #1572481
    Closes-Bug: #1572906

    Change-Id: If2f69a02537c84270f3699240b1e8c7c4cc7a578

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-ui (stable/mitaka)

Reviewed: https://review.openstack.org/309391
Committed: https://git.openstack.org/cgit/openstack/fuel-ui/commit/?id=ecb908c267d38d500d005078050ea792bc60bfd7
Submitter: Jenkins
Branch: stable/mitaka

commit ecb908c267d38d500d005078050ea792bc60bfd7
Author: Julia Aranovich <email address hidden>
Date: Thu Apr 21 19:14:09 2016 +0300

    Support installing of new plugins to existing environment

    * hasChanges method of Settings model is fixed to support environment
      plugins which are installed after the environment creation or
      environment deployment

    Closes-Bug: #1572481
    Closes-Bug: #1572906

    Change-Id: If2f69a02537c84270f3699240b1e8c7c4cc7a578

Revision history for this message
ElenaRossokhina (esolomina) wrote :

Verified on 417-mos iso and plugin example v3
cat /etc/fuel_build_id:
 417
cat /etc/fuel_build_number:
 417
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6347.noarch
 fuel-bootstrap-cli-9.0.0-1.mos284.noarch
 fuel-migrate-9.0.0-1.mos8398.noarch
 fuel-mirror-9.0.0-1.mos137.noarch
 fuel-notify-9.0.0-1.mos8398.noarch
 nailgun-mcagents-9.0.0-1.mos746.noarch
 python-fuelclient-9.0.0-1.mos316.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6347.noarch
 fuel-utils-9.0.0-1.mos8398.noarch
 fuel-setup-9.0.0-1.mos6347.noarch
 fuel-library9.0-9.0.0-1.mos8398.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-agent-9.0.0-1.mos284.noarch
 fuel-ui-9.0.0-1.mos2706.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 fuel-misc-9.0.0-1.mos8398.noarch
 python-packetary-9.0.0-1.mos137.noarch
 fuel-nailgun-9.0.0-1.mos8709.noarch
 rubygem-astute-9.0.0-1.mos746.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8709.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-openstack-metadata-9.0.0-1.mos8709.noarch

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.