Can not open deployed cluster page after plugin installation

Bug #1572906 reported by Julia Aranovich
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

Steps to reproduce in Fuel UI:

1. create environment (default wizard parameters), add some nodes and deploy the environment
2. go to Environments page
3. install some plugin compatible with the environment
4. go to the environment page

Expected result:
the environment page is open and the plugin settings are shown on Settings tab

Actual result: the environment page isn't open, user stays on Environments page. Also there is a JS exception in browser console.

Tags: area-ui
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-ui (master)

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

Changed in fuel:
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 with 417-mos iso and fuel_plugin_example_v4
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.