Bug 1815612
| Summary: | further multus-admission-controller clusteroperator status improvements | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan Winship <danw> | |
| Component: | Networking | Assignee: | Dan Winship <danw> | |
| Networking sub component: | multus | QA Contact: | Weibin Liang <weliang> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | unspecified | |||
| Priority: | unspecified | |||
| Version: | 4.5 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1815613 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:23:29 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1815613 | |||
Got correct muluts logs described in comment1 in 4.5.0-0.nightly-2020-03-24-094447, testing passed and verified. 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, 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/RHBA-2020:2409 |
In the past there has often been confusion about the network clusteroperator status including messages like: DaemonSet "openshift-multus/multus-admission-controller" is not available which led people to believe that the network operator was reporting on its own failure to do something, when it fact it's merely commenting on *someone else's* failure to allow the admission controller to start. This is now fixed in master to instead show: DaemonSet "openshift-multus/multus-admission-controller" is waiting for other operators to become ready For QE: if you look in the cluster-network-operator logs, as it posts updates to the clusteroperator status, you should see first: Waiting for DaemonSet "openshift-multus/multus-admission-controller" to be created and shortly after: DaemonSet "openshift-multus/multus-admission-controller" is waiting for other operators to become ready and then that will stay in the status through most of the install process. If the install fails before the worker nodes are allocated, then the status will never make it beyond that. But once the worker nodes come up, it should show that the DaemonSet is deploying, with some series of messages like: DaemonSet "openshift-multus/multus-admission-controller" update is rolling out (0 out of 1 updated) or DaemonSet "openshift-multus/multus-admission-controller" is not available (awaiting 1 nodes) and then eventually CNO will switch to "False" for "Progressing".