[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Failing to bootstrap disconnected 4.2 cluster on metal

So I got past bootstrap this time, and it made it almost all the way, it got stuck on the machine-operator.  All the other cluster operators have passed.

I'm not really sure how to diagnose what is wrong with the machine-config operator.  I tried 'oc adm must-gather', but it didn't work because the must-gather container isn't part of the release manifest, so it tried to reach out to quay.io to download that container, which obviously fails in a disconnected environment.  Maybe must-gather could be included in the release manifest so that it's available in disconnected environments by default?

I instead ran "oc describe clusteroperator machine-config", this error message was there, how do I diagnose this?

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)  

On Mon, 28 Oct 2019 at 05:59, Clayton Coleman <ccoleman redhat com> wrote:
We probably need to remove the example from the docs and highlight
that you must copy the value reported by image mirror

> On Oct 27, 2019, at 11:33 AM, W. Trevor King <wking redhat com> wrote:
>> On Sun, Oct 27, 2019 at 2:17 AM Joel Pearson wrote:
>> Ooh, does this mean 4.2.2 is out or the release is imminent? Should I be trying to install 4.2.2 instead of 4.2.0?
> 4.2.2 exists and is in candidate-4.2.  That means it's currently
> unsupported.  The point of candidate-* testing is to test the releases
> to turn up anything that should block them going stable, so we're
> certainly launching a bunch of throw-away 4.2.2 clusters at this
> point, and other folks are welcome to do that too.  But if you want
> stability and support, you should wait until it is promoted into
> fast-4.2 or stable-4.2 (which may never happen if testing turns up a
> serious-enough issue).  So "maybe" to both your question ;).
>> I mirrored quay.io/openshift-release-dev/ocp-release:4.2.0
> Yeah, should be no CI-registry images under that.
> Cheers,
> Trevor
> _______________________________________________
> users mailing list
> users lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]