Bug 2064899 - Failed to provision openshift 4.10 on bare metal
Summary: Failed to provision openshift 4.10 on bare metal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.5
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.5
Assignee: Jian Qiu
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
: 2089568 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-16 20:03 UTC by Thuy Nguyen
Modified: 2023-02-08 02:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2094109 (view as bug list)
Environment:
Last Closed: 2022-06-09 02:09:46 UTC
Target Upstream Version:
Embargoed:
dhuynh: qe_test_coverage+
bot-tracker-sync: rhacm-2.5+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 20792 0 None None None 2022-03-17 17:24:10 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:09:54 UTC

Description Thuy Nguyen 2022-03-16 20:03:42 UTC
Description of the problem: Failed to provision openshift 4.10 on bare metal

Release version:

Operator snapshot version:
- ACM 2.5.0-DOWNSTREAM-2022-03-14-13-03-46 (S4)
- MCE 2.0.0-DOWNANDBACK-2022-03-13-16-38-39

OCP version: 4.9.23

Browser Info:

Steps to reproduce:
1. Provision spoke cluster on bare metal 

Actual results:
Cluster deployment failed

Expected results:

Additional info:

oc get cd -n slot-02
NAME      INFRAID   PLATFORM    REGION   VERSION   CLUSTERTYPE   PROVISIONSTATUS    POWERSTATE   AGE
slot-02             baremetal                                    ProvisionStopped                3m28s

oc get cd -n slot-02 slot-02 -ojsonpath='{.status.conditions[0]}' | jq .
{
  "lastProbeTime": "2022-03-16T19:58:15Z",
  "lastTransitionTime": "2022-03-16T19:58:15Z",
  "message": "Unknown error - installer failed to load install config",
  "reason": "FallbackInvalidInstallConfig",
  "status": "True",
  "type": "ProvisionFailed"
}

provision.log:
time="2022-03-16T19:58:13Z" level=fatal msg="failed to fetch Master Machines: failed to load asset \"Install Config\": failed to unmarshal install-config.yaml: failed to parse first occurence of unknown field: error unmarshaling JSON: while decoding JSON: json: unknown field \"namespace\""
time="2022-03-16T19:58:14Z" level=error msg="error after waiting for command completion" error="exit status 1" installID=t4bgvv8w
time="2022-03-16T19:58:14Z" level=error msg="error generating installer assets" error="exit status 1" installID=t4bgvv8w
time="2022-03-16T19:58:14Z" level=info msg="reading installer log" installID=t4bgvv8w
time="2022-03-16T19:58:14Z" level=info msg="saving installer output" installID=t4bgvv8w
time="2022-03-16T19:58:14Z" level=debug msg="installer console log: level=fatal msg=failed to fetch Master Machines: failed to load asset \"Install Config\": failed to unmarshal install-config.yaml: failed to parse first occurence of unknown field: error unmarshaling JSON: while decoding JSON: json: unknown field \"namespace\"\n" installID=t4bgvv8w
time="2022-03-16T19:58:14Z" level=info msg="updating clusterprovision" installID=t4bgvv8w
time="2022-03-16T19:58:14Z" level=fatal msg="runtime error" error="exit status 1"

Comment 2 bot-tracker-sync 2022-03-24 22:12:53 UTC
G2Bsync 1078175449 comment 
 thuyn-581 Thu, 24 Mar 2022 20:20:12 UTC 
 G2Bsync -
Validated on ACM 2.5.0-DOWNSTREAM-2022-03-23-01-06-05.

Comment 4 Kevin Cormier 2022-05-24 15:42:28 UTC
*** Bug 2089568 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2022-06-09 02:09:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:4956


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