Bug 2089568 - New OCP deployment on BM fails for v4.10 (but works for older ocpversions)
Summary: New OCP deployment on BM fails for v4.10 (but works for older ocpversions)
Keywords:
Status: CLOSED DUPLICATE of bug 2064899
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.4.z
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: rhacm-2.4.5
Assignee: Kevin Cormier
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 03:41 UTC by Mihir Lele
Modified: 2025-08-08 13:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-24 15:42:28 UTC
Target Upstream Version:
Embargoed:
dhuynh: qe_test_coverage+
bot-tracker-sync: rhacm-2.4.z+
kcormier: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 22690 0 None None None 2022-05-24 08:13:43 UTC

Description Mihir Lele 2022-05-24 03:41:32 UTC
Description of the problem:

Customer is deploying new clusters using ACM on BM. The installations work fine for ocp 4.9 or older version, but is failing for ocp 4.10

Additional info:

Hive-controller logs:

time="2022-05-19T09:47:51Z" level=debug msg="Built from commit 26fec8834ed5b3fef59f4f08f16c66fce52c001e"
time="2022-05-19T09:47:51Z" level=debug msg="Fetching Master Machines..."
time="2022-05-19T09:47:51Z" level=debug msg="Loading Master Machines..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Cluster ID..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Install Config..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading SSH Key..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Base Domain..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Platform..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Cluster Name..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Base Domain..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Platform..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Networking..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Platform..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Pull Secret..."
time="2022-05-19T09:47:51Z" level=debug msg=" Loading Platform..."
time="2022-05-19T09:47:51Z" 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-05-19T09:47:52Z" level=error msg="error after waiting for command completion" error="exit status 1" installID=hmzhtmp7
time="2022-05-19T09:47:52Z" level=error msg="error generating installer assets" error="exit status 1" installID=hmzhtmp7
time="2022-05-19T09:47:52Z" level=info msg="reading installer log" installID=hmzhtmp7
time="2022-05-19T09:47:52Z" level=info msg="saving installer output" installID=hmzhtmp7
time="2022-05-19T09:47:52Z" 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=hmzhtmp7
time="2022-05-19T09:47:52Z" level=info msg="updating clusterprovision" installID=hmzhtmp7
time="2022-05-19T09:47:52Z" level=fatal msg="runtime error" error="exit status 1"

Comment 2 daliu 2022-05-24 07:02:02 UTC
We already fixed a issue about this in ACM2.5: 
https://github.com/stolostron/backlog/issues/20792
https://bugzilla.redhat.com/show_bug.cgi?id=2064899

@kcormier I guess CU's ACM version is 2.4, so please confirm if this issue also fixed in 2.4

Comment 3 Mihir Lele 2022-05-24 07:18:35 UTC
Thanks for the update! I will inform the customer.

Also, I am good to mark this bz as duplicate of 2064899

Comment 4 bot-tracker-sync 2022-05-24 13:57:07 UTC
G2Bsync 1135907266 comment 
 KevinFCormier Tue, 24 May 2022 13:12:24 UTC 
 G2Bsync The issue was not fixed for RHACM 2.4. The fix can be backported for 2.4.5 under this issue.

Comment 6 Kevin Cormier 2022-05-24 15:42:28 UTC

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


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