Yes, that is a known 4.2 bug. > On Oct 28, 2019, at 2:24 PM, W. Trevor King <wk...@redhat.com> wrote: > >> On Mon, Oct 28, 2019 at 4:05 AM Joel Pearson wrote: >> Maybe must-gather could be included in the release manifest so that it's >> available in disconnected environments by default? > > It is: > > $ oc adm release info --image-for=must-gather > quay.io/openshift-release-dev/ocp-release:4.2.0 > > quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:34ff29512304f77b0ab70ea6850e7f8295a4d19e497ab690ea5102a7044ea993 > > If your 'oc adm must-gather' is reaching out to Quay, instead of > hitting your mirror, it may be because your samples operator has yet > to get the mirrored must-gather ImageStream set up. > >>> Failed to resync 4.2.0 because: timed out waiting for the condition during >>> waitForFaemonsetRollout: Daemonset machine-config-daemon is not ready. >>> status (desired:7, updated 7, ready: 6, unavailable: 6) > > That (un)available typo should be fixed in master by [1], but looks > like that hasn't been backported to 4.2.z. But look for the > machine-config daemon that is unready (possibly by listing Pods), and > see why it's not going ready. > > Cheers, > Trevor > > [1]: > https://github.com/openshift/machine-config-operator/commit/efb6a96a5bcb13cb3c0c0a0ac0c2e7b022b72665 > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
