[Upgrade] After creating cluster using Liberty release Fuel UI is unresponsive

Bug #1606577 reported by Alisa Tselovalnikova
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel UI Team

Bug Description

Detailed bug description:
 After upgrading of fuel master 8.0 -> 9.x and creating cluster with Liberty release Fuel UI is unresponsive(buttons are clickable, but no action is occurred).

Steps to reproduce:
 1. Deploy 8.0 Fuel cluster
 2. Upgrade Fuel master node from 8.0 to 9.x
 3. Create cluster with Liberty release
 4. Add nodes to created cluster
 5. Verify networks
After provided steps Fuel UI is unresponsive.

Expected results:
 Fuel UI is responsive.

Actual result:
 Fuel UI is unresponsive. Error:
 ReactReconciler.js:51 Uncaught TypeError: Cannot read property '_currentElement' of null

Reproducibility:
 100%

Description of the environment:
 8.0 - http://paste.openstack.org/show/539091/
 9.0 - http://paste.openstack.org/show/541615/
       https://custom-ci.infra.mirantis.net/view/9.0/job/9.0.custom.iso/275/

description: updated
Changed in fuel:
assignee: nobody → Fuel UI Team (fuel-ui)
status: New → Confirmed
importance: Undecided → High
Changed in fuel:
assignee: Fuel UI Team (fuel-ui) → Fuel Octane (fuel-octane-team)
summary: - [Upgrade] After adding cluster using Liberty release Fuel UI is
+ [Upgrade] After creating cluster using Liberty release Fuel UI is
unresponsive
Changed in fuel:
milestone: none → 9.1
tags: added: feature-upgrade
Ilya Kharin (akscram)
Changed in fuel:
assignee: Fuel Octane (fuel-octane-team) → Fuel UI Team (fuel-ui)
Changed in fuel:
status: Confirmed → Won't Fix
Revision history for this message
Alisa Tselovalnikova (atselovalnikova) wrote :

Liberty release is not deployable after the upgrade Fuel Master since 8.0 to 9.x

Revision history for this message
Vladimir Khlyunev (vkhlyunev) wrote :

According to https://bugs.launchpad.net/fuel/+bug/1607247 now its impossible to create new liberty cluster

Changed in fuel:
status: Won't Fix → Invalid
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.