Bug 2002354 - Missing DU configuration "Done" status reporting during ZTP flow
Summary: Missing DU configuration "Done" status reporting during ZTP flow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Telco Edge
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: Angie Wang
QA Contact: yliu1
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-08 15:38 UTC by Marius Cornea
Modified: 2022-03-10 16:08 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2022-03-10 16:08:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift-kni cnf-features-deploy pull 805 0 None Merged ztp: Update PolicyGen to create static inform policy 2022-01-25 14:09:03 UTC
Red Hat Issue Tracker CNF-2880 0 None None None 2021-09-08 15:39:30 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:08:52 UTC

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
Note You need to log in before you can comment on or make changes to this bug.