Bug 1815613

+++ This bug was initially created as a clone of Bug #1815612 +++

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".