[Bug 1725421] Re: [mitaka] Nova lock/unlock should be hidden if nova api <2.9

[Corey Bryant]

I've updated the bug description and title as it was discussing 2
different scenarios.

** Description changed:

  [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]
  
-   1. Log into Horizon dashboard.
-   2. Create new instance.
-   3. Wait for instance to switch to 'running' state.
-   4. On the newly created instance, under Actions, you'll
-      see both 'Lock Instance' and 'Unlock Instance' are
-      available, even after locking the instance.
+ 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]

** Summary changed:

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

** Also affects: cloud-archive/mitaka
   Importance: Undecided
       Status: New

** Also affects: horizon (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: horizon (Ubuntu)
       Status: In Progress => Invalid

** Changed in: cloud-archive
       Status: New => Invalid

** Changed in: cloud-archive/mitaka
       Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

** Changed in: horizon (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: horizon (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: horizon (Ubuntu)
   Importance: Medium => Undecided

** Changed in: cloud-archive
   Importance: Medium => Undecided

** Changed in: horizon (Ubuntu Xenial)
     Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: horizon (Ubuntu)
     Assignee: Shane Peters (shaner) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to horizon in Ubuntu.
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:
  Triaged
Status in horizon package in Ubuntu:
  Invalid
Status in horizon source package in Xenial:
  Triaged

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