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

Bug 2002354

Summary: Missing DU configuration "Done" status reporting during ZTP flow
Product: OpenShift Container Platform Reporter: Marius Cornea <mcornea>
Component: Telco EdgeAssignee: Angie Wang <angwang>
Telco Edge sub component: ZTP QA Contact: yliu1
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: aos-bugs, eparis, nstielau
Version: 4.8   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
There wasn't an easy way for customers to know when ZTP of a cluster is completed and the cluster is ready to host their workloads. Customers must manually check some resources on each deployed spoke cluster. So a validator ACM policy is introduced in this story that indicates when du configuration is completed and ZTP is done.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:08:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marius Cornea 2021-09-08 15:38:25 UTC
Description of problem:

Currently there isn't a single way to check the DU configuration status.  In order to determine when the DU configuration is complete the user needs to check multiple resources like:

- agentclusterinstall/clusterdeployment status to determine that OCP is installed
- ACM policies status to check that policies were applied
- MachineConfigs have been created
- the MCP was fully reconciled
- the operators installed by policies are Available
- the api-server is responding

Since these checks need to be done by the user for each DU nodes individually it won't scale when a large number of DU nodes are deployed.

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

How reproducible:
100%

Comment 1 Nick Stielau 2021-10-07 17:19:17 UTC
Assuming not a blocker for 4.9.  Please look for blocker? BZs and make a blocker determination.

Comment 4 yliu1 2022-02-01 17:54:00 UTC
Verified with "DU validator" on 4.10.

Comment 7 errata-xmlrpc 2022-03-10 16:08:32 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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:0056