On Fri, Oct 25, 2019 at 3:01 AM Joel Pearson wrote:
> One strange thing that happened was that it was trying to download images
> from "quay.io/openshift-release-dev/ocp-v4.0-art-dev" instead of the
> documented "quay.io/openshift-release-dev/ocp-release".
The operator and so on images referenced by the release image are
there. For example:
$ oc adm release info --pullspecs
quay.io/openshift-release-dev/ocp-release:4.2.2 | grep -A3 Images:
Images:
NAME PULL SPEC
aws-machine-controllers
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3366f4120ebf7465f147a5e43d6e1c43a76cefbd461cdbe25349f8b3c735bc1d
azure-machine-controllers
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8f724056624dc3b5130c9b80a88891e21579ddb6fa49c1ed21bd6173879609d2
> - mirrors: - <bastion_host_name>:5000/<repo_name>/release
> source: registry.svc.ci.openshift.org/ocp/release
This entry should only be needed if your are installing a release from
the CI registry. 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?
> Where can I look for errors?
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.
Cheers,
Trevor
[1]:
https://docs.openshift.com/container-platform/4.2/installing/installing_restricted_networks/installing-restricted-networks-preparations.html#installation-mirror-repository_installing-restricted-networks-preparations
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
