Re: Pull secret for CI builds?
On Sun, Oct 27, 2019 at 6:41 PM Jon Stanley wrote: > Is there a pull secret available for the CI builds (i.e. > registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-10-27-140004) > for those of us that want to live on the bleeding edge? CI-registry images are internal, although we push nightlies to [1] which don't require CI-registry access (just the usual cloud.openshift.com pull secret, although that seems to redirect to cloud.redhat.com/openshift now). Looks like there haven't been recent 4.2.z nightlies up there, but 4.2.2 is based on a nightly from the 23rd [2] and 4.2.3 should be moving out to Quay on Thursday, so it's not that long of a wait to see new 4.2.z stuff. Cheers, Trevor [1]: https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/ [2]: https://openshift-release.svc.ci.openshift.org/releasestream/4-stable/release/4.2.2 ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: Failing to bootstrap disconnected 4.2 cluster on metal
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 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 ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: Failing to bootstrap disconnected 4.2 cluster on metal
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
Re: Failing to bootstrap disconnected 4.2 cluster on metal
> > quay.io/openshift-release-dev/ocp-release:4.2.0$ oc adm release info > --pullspecs > quay.io/openshift-release-dev/ocp-release:4.2.2 | grep -A3 Images: 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? ... And it's not in [1], although you should just be > recycling whatever 'oc adm release mirror' suggests instead of blindly > copy/pasting from docs. Which release did you mirror? Thanks for this information. Looks like I must have skipped reading the output of the mirror command. Thanks for that heads up! I mirrored quay.io/openshift-release-dev/ocp-release:4.2.0 I dunno what happened with your API-server lock-up, but > 'openshift-install gather bootstrap ...' will SSH into your bootstrap > machine and from there onto the control-plane machines and gather the > things we expected would be useful for debugging this sort of thing, > so probably start with that. I'll try out "openshift-install gather bootstrap" tomorrow. It sounds very useful, thanks for that information. Thanks, Joel ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
