CNO is responsible for deploying the multus-admission-controller, but unlike everything else it deploys, that is not necessary for "cluster networking" to be functional, and it can't start up until fairly late in the install. This means that if *anything* fails mid-install, the network operator will almost always be reporting not Available and (since https://github.com/openshift/cluster-network-operator/pull/358) eventually Degraded, causing people to mistakenly believe that the network was the cause of their install failure. We need to fix our status reporting to not imply that.
Tested and verified on 4.4.0-0.nightly-2020-01-06-072200 CNO does not Degraded anymore just because multus-admission-controller is not available.
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:0581