Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1872896

Summary: [OCP 4.6] UI Graceful popup not detected when power off node under Actions button in Compute->BMH-><name of node>->Actions->Power Off but works correctly when you use Compute->BMH-><name of node>-><Kebab button: Power Off
Product: OpenShift Container Platform Reporter: mlammon
Component: Console Metal3 PluginAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED DUPLICATE QA Contact: Yanping Zhang <yanpzhan>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: abeekhof, aos-bugs, gharden, jtomasek, yanpzhan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1872893 Environment:
Last Closed: 2020-09-14 07:20:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1872893    
Bug Blocks:    

Description mlammon 2020-08-26 20:45:25 UTC
+++ This bug was initially created as a clone of Bug #1872893 +++

This is also an issue in 4.6 (not released)

Description of problem:
UI Graceful popup not detected when power off node under Actions button in Compute->BMH-><name of node>->Actions->Power Off
but works correctly when you use Compute->BMH-><name of node>-><Kebab button: Power Off>

See attachments

Version-Release number of selected component (if applicable):
version   4.5.6

How reproducible:
100%

Steps to Reproduce:
1. Install OCP 
2. Installed  Openshift Virtualization in OperatorHub (kubevirt-hyperconverged - Red Hat Operators) for use with
Node Maintenance Operator (NM)
3. Compute->BMH->Start Maintenance or Compute->Nodes->Start Maintenance
(After node goes into "Under Maintenance"
4. Compute->BMH->Start Maintenance->(...)Kebab button "Power Off"
(This will cause a pop up message) "Host is ready to be gracefully powered off.  The host is currently under maintenance and all workloads have already been moved." 
****  This is what we want to see

Or in this case (the bug)

4. Compute->BMH->Start Maintenance->openshift-master-0-0->Actions->Power Off
It gives you a different pop up basically "thinking its not ready to be gracefully turned off" with checking the Power off immediately



Actual results:
Not getting correct pop up for graceful power off

Expected results:
pop up for graceful power off (confirmation)

Additional info:


oc describe nodemaintenances.nodemaintenance.kubevirt.io nm-45zcv 

Name:         nm-45zcv
Namespace:
Labels:       <none>
Annotations:  <none>
API Version:  nodemaintenance.kubevirt.io/v1beta1
Kind:         NodeMaintenance
Metadata:
  Creation Timestamp:  2020-08-26T19:55:49Z
  Finalizers:
    foregroundDeleteNodeMaintenance
  Generate Name:  nm-
  Generation:     1
  Managed Fields:
    API Version:  nodemaintenance.kubevirt.io/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:generateName:
      f:spec:
        .:
        f:nodeName:
        f:reason:
    Manager:      Mozilla
    Operation:    Update
    Time:         2020-08-26T19:55:49Z
    API Version:  nodemaintenance.kubevirt.io/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .:
          v:"foregroundDeleteNodeMaintenance":
      f:status:
        .:
        f:evictionPods:
        f:phase:
        f:totalpods:
    Manager:         node-maintenance-operator
    Operation:       Update
    Time:            2020-08-26T19:56:30Z
  Resource Version:  71970
  Self Link:         /apis/nodemaintenance.kubevirt.io/v1beta1/nodemaintenances/nm-45zcv
  UID:               4f45006b-4687-45ba-b289-e298d7f229d2
Spec:
  Node Name:  master-0-0
  Reason:     replace server
Status:
  Eviction Pods:  31
  Phase:          Succeeded
  Totalpods:      51
Events:           <none>

--- Additional comment from  on 2020-08-26 20:41:40 UTC ---



--- Additional comment from  on 2020-08-26 20:42:23 UTC ---

Comment 1 Jiri Tomasek 2020-09-14 07:20:18 UTC

*** This bug has been marked as a duplicate of bug 1872893 ***