[mitaka] Hide nova lock/unlock if nova api <2.9 and when >= 2.9, "Lock/Unlock Instance" should not be shown at same time.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Mitaka |
Invalid
|
Medium
|
Unassigned | ||
horizon (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Medium
|
Shane Peters |
Bug Description
[Impact]
* Similar/related to lp:1505845, which was fixed for Newton.
Lock/unlock options are displayed in Horizon despite Nova API <2.9,
which causes user confusion.
* Additionally, when Nova API is >= 2.9, the actions "Lock Instance"
and "Unlock Instance" should not be shown at the same time.
[Test Case]
case 1:
1. Deploy nova and horizon both at mitaka level.
2. Log into Horizon dashboard.
3. Create new instance.
4. Wait for instance to switch to 'running' state.
5. On the newly created instance, under Actions, you'll
see both 'Lock Instance' and 'Unlock Instance' are
available, even after locking the instance.
case 2:
1. Deploy nova at kilo level and horizon at mitaka level (test with Nova API < 2.9)
2. Log into Horizon dashboard.
3. Create new instance.
4. Wait for instance to switch to 'running' state.
5. On the newly created instance, under Actions, you'll
'Lock Instance' and 'Unlock Instance' should be hidden.
[Regression Potential]
* Regression potential is low. This bug has been fixed in all releases of
OpenStack starting with Newton. The patch did have to be modified
slightly to apply to mitaka.
[Discussion]
Changed in horizon (Ubuntu): | |
assignee: | nobody → Shane Peters (shaner) |
Changed in horizon (Ubuntu): | |
milestone: | none → xenial-updates |
Changed in cloud-archive: | |
importance: | Undecided → Medium |
tags: | added: sts |
description: | updated |
description: | updated |
tags: | added: sts-sru-needed |
Mitaka should support v2.25 of the Nova API?