group.of.nepali.translators team mailing list archive

[Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx>]

for ref: sru cancelled

** Changed in: cloud-archive/mitaka
       Status: Fix Committed => Invalid

** Changed in: horizon (Ubuntu Xenial)
       Status: Fix Committed => Invalid

** Tags removed: sts-sru-needed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1725421

Title:
  [mitaka] Hide nova lock/unlock if nova api <2.9 and when >= 2.9,
  "Lock/Unlock Instance" should not be shown at same time.

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Invalid
Status in horizon package in Ubuntu:
  Invalid
Status in horizon source package in Xenial:
  Invalid

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]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1725421/+subscriptions