After upgrade from 8.0 to 9.0 can not access old environment in Fuel UI

Bug #1595209 reported by Dmitry Mescheryakov
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Sergey Slipushenko
Mitaka
Fix Released
High
Sergey Slipushenko

Bug Description

Version: 8.0 -> 9.0

Steps to reproduce:
1. Install 8.0 master node
2. Install detach-rabbitmq plugin
3. Create a new environment consisting of 1 controller, 1 compute+cinder and 1 RabbitMQ node.
4. Deploy the environment.
5. Upgrade master node to 9.0 using procedure described in http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/upgrade/upgrade-fuel.html
6. Log into Fuel UI and click on environment created in step #3.

Expected result:
Environment screen appears

Actual result:
Nothing happens, I am left on general Home/Environments screen

Details:
After enabling debug in Nailgun, Chrome's developer tools show the following stack trace from the server: http://paste.openstack.org/show/521183/

description: updated
description: updated
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
milestone: none → 9.0-updates
milestone: 9.0-updates → 10.0
milestone: 10.0 → 9.0-updates
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Fuel Octane (fuel-octane-team)
tags: added: feature-upgrade team-upgrades
no longer affects: fuel/newton
no longer affects: fuel/newton
Changed in fuel:
milestone: next → 10.0
Ilya Kharin (akscram)
Changed in fuel:
assignee: Fuel Octane (fuel-octane-team) → Sergey Slipushenko (sslypushenko)
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

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

commit f1be069f5ee59127dedbed5bb8cc01feed3400f2
Author: sslypushenko <email address hidden>
Date: Tue Jun 21 18:57:30 2016 +0300

    Add default rules to pick boot disk

    Added migration from Fuel 8.0 to 9.0, which adds default rule
    to pick bootable disk in volume metadata of release.

    Change-Id: I5d151a29bf52ac3a519049c38b2b671c087f968f
    Closes-Bug: #1595209

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (stable/mitaka)

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

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

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

commit d37de23b380ecec888adfbe8dda148e370cda018
Author: sslypushenko <email address hidden>
Date: Tue Jun 21 18:57:30 2016 +0300

    Add default rules to pick boot disk

    Added migration from Fuel 8.0 to 9.0, which adds default rule
    to pick bootable disk in volume metadata of release.

    (cherry-picked from f1be069f5ee59127dedbed5bb8cc01feed3400f2)

    Change-Id: I5d151a29bf52ac3a519049c38b2b671c087f968f
    Closes-Bug: #1595209

description: updated
tags: added: on-verification
Revision history for this message
Dmitry Belyaninov (dbelyaninov) wrote :

Verified on 9.X snapshot #98

After steps from the description, deployed cluster is present on UI.

tags: removed: on-verification
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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