Bug 1853605 - Deploying an Bare Metal Host cluster does not properly set BMC secrets.
Summary: Deploying an Bare Metal Host cluster does not properly set BMC secrets.
Keywords:
Status: CLOSED DUPLICATE of bug 1853516
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Hao Liu
QA Contact: magchen@redthat.com
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-03 10:18 UTC by Constantin Vultur
Modified: 2020-07-03 13:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-03 13:18:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Constantin Vultur 2020-07-03 10:18:10 UTC
Description of problem:
Deploying an Spoke with Bare Metal Hosts does not properly set BMC secrets.

Version-Release number of selected component (if applicable):
ACM: 2.0.0-SNAPSHOT-2020-07-02-00-34-59
OCP: 4.5.0-0.nightly-2020-07-01-152847

Spoke OCP: 4.4.8

How reproducible:


Steps to Reproduce:
1. Deploy a Spoke OCP Bare Metal cluster with version 4.4.8
2. 
3.

Actual results:
Install hangs and eventually times out

While inspecting the cluster, the Masters are deployed but not the workers.
Furthermore, looking at the NS : openshift-machine-api , I checked the BMH 

$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version             False       True          82m     Unable to apply 4.4.8: some cluster operators have not yet rolled out
$ oc get bmh
NAME                   STATUS   PROVISIONING STATUS   CONSUMER                                BMC                                                                                    HARDWARE PROFILE   ONLINE   ERROR
openshift-master-1-0   error                          ocp-edge-cluster-cdv-1-master-0         redfish://192.168.123.1:8000/redfish/v1/Systems/ba9f944c-cf62-4b3d-93fd-253f5da0242f                      true     Validation error with BMC credentials: Missing BMC connection detail 'username' in credentials
openshift-master-1-1   error                          ocp-edge-cluster-cdv-1-master-1         redfish://192.168.123.1:8000/redfish/v1/Systems/8da13d70-b381-42a9-8adb-f029fa859e7c                      true     Validation error with BMC credentials: Missing BMC connection detail 'username' in credentials
openshift-master-1-2   error                          ocp-edge-cluster-cdv-1-master-2         redfish://192.168.123.1:8000/redfish/v1/Systems/3019610b-517d-4920-8dd2-fbdcb7d92896                      true     Validation error with BMC credentials: Missing BMC connection detail 'username' in credentials
openshift-worker-1-0   error                          ocp-edge-cluster-cdv-1-worker-0-vrg66   redfish://192.168.123.1:8000/redfish/v1/Systems/ed79938b-2b03-44d7-a3be-b7cfc4f8dbd2                      true     Validation error with BMC credentials: Missing BMC connection detail 'username' in credentials
openshift-worker-1-1   error                          ocp-edge-cluster-cdv-1-worker-0-78rkh   redfish://192.168.123.1:8000/redfish/v1/Systems/93a83023-6f34-40dc-840b-e784419d3e87                      true     Validation error with BMC credentials: Missing BMC connection detail 'username' in credentials

The secrets for BMC access are empty:

$ oc get secret openshift-master-1-0-bmc-secret -o json
{
    "apiVersion": "v1",
    "data": {
        "password": "",
        "username": ""
    },
    "kind": "Secret",

As a workaround, I've added by hand the username and secret, which set back to Status:OK the BMH 

$ oc edit secret openshift-master-1-0-bmc-secret
secret/openshift-master-1-0-bmc-secret edited
$ oc edit secret openshift-master-1-1-bmc-secret
secret/openshift-master-1-1-bmc-secret edited
$ oc edit secret openshift-master-1-2-bmc-secret
secret/openshift-master-1-2-bmc-secret edited
$ oc edit secret openshift-worker-1-0-bmc-secret
secret/openshift-worker-1-0-bmc-secret edited
$ oc edit secret openshift-worker-1-1-bmc-secret
secret/openshift-worker-1-1-bmc-secret edited
$ oc get bmh
NAME                   STATUS   PROVISIONING STATUS      CONSUMER                                BMC                                                                                    HARDWARE PROFILE   ONLINE   ERROR
openshift-master-1-0   OK       externally provisioned   ocp-edge-cluster-cdv-1-master-0         redfish://192.168.123.1:8000/redfish/v1/Systems/ba9f944c-cf62-4b3d-93fd-253f5da0242f                      true     
openshift-master-1-1   OK       externally provisioned   ocp-edge-cluster-cdv-1-master-1         redfish://192.168.123.1:8000/redfish/v1/Systems/8da13d70-b381-42a9-8adb-f029fa859e7c                      true     
openshift-master-1-2   OK       externally provisioned   ocp-edge-cluster-cdv-1-master-2         redfish://192.168.123.1:8000/redfish/v1/Systems/3019610b-517d-4920-8dd2-fbdcb7d92896                      true     
openshift-worker-1-0   OK       inspecting               ocp-edge-cluster-cdv-1-worker-0-vrg66   redfish://192.168.123.1:8000/redfish/v1/Systems/ed79938b-2b03-44d7-a3be-b7cfc4f8dbd2                      true     
openshift-worker-1-1   OK       inspecting               ocp-edge-cluster-cdv-1-worker-0-78rkh   redfish://192.168.123.1:8000/redfish/v1/Systems/93a83023-6f34-40dc-840b-e784419d3e87                      true    

Also, with that change the deployment went successfully

msg=\"Access the OpenShift web-console here: https://console-openshift-console.apps.ocp-edge-cluster-cdv-1.qe.lab.redhat.com\"\nREDACTED LINE OF OUTPUT\n" 
level=info msg="install completed successfully"

Expected results:


Additional info:

Comment 1 Alexander Chuzhoy 2020-07-03 13:18:44 UTC

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


Note You need to log in before you can comment on or make changes to this bug.