On Jul 18, 2019, at 6:24 PM, Daniel Comnea <comnea dani gmail com> wrote:On Thu, Jul 18, 2019 at 10:08 PM Clayton Coleman <ccoleman redhat com> wrote:We generally bump "latest" symlink once it's in the stable channel, which 4.1.6 is not in. 4.1.6 is still considered pre-release.[DC]: i looked  and so i assumed is stable since is part of 4-stable section.That page has nothing to do with officially going into stable channels. If the cluster doesn’t show the update or “latest” doesn’t point to it it’s not stable yet.
For your first error message, which installer binary were you using? Can you link to it directly?[DC]: sure thing, i've downloaded from try.openshift.com which took me to https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.1.4/openshift-install-mac-4.1.4.tar.gzAre you positive you were installing from that binary? I just double checked locally and that listed a quay.io release image.
On Thu, Jul 18, 2019 at 3:55 PM Daniel Comnea <comnea dani gmail com> wrote:_______________________________________________Hi,Trying a new fresh deployment by downloading a new secret together with the installer from try.openshift.com i end up in a failure state with bootstrap node caused byerror pulling image "registry.svc.ci.openshift.org/ocp/release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163a": unable to pull registry.svc.ci.openshift.org/ocp/release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163a: unable to pull image: Error determining manifest MIME type for docker://registry.svc.ci.openshift.org/ocp/release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163a: Error reading manifest sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163a in registry.svc.ci.openshift.org/ocp/release: unauthorized: authentication requiredManually trying from withing bootstrap node to check if it works .. i get same negative resultskopeo inspect --authfile /root/.docker/config.json docker://registry.svc.ci.openshift.org/ocp/release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163aSwitching to installer 4.1.0/ 4.1.3/ 4.1.6 with the same pull secret am able to get bootstrap node up with is MCO and the other pods up.One interesting bit is that 4.1.4 points to a release image hosted internally./openshift-install version
built from commit bf47826c077d16798c556b1bd143a5bbfac14271
release image registry.svc.ci.openshift.org/ocp/release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163abut 4.1.6 for example points to quay.io (as expected).Is this a bug?On a slightly different note, would be nice to update try.openshift.com to latest stable 4.1 release which is .6 and not .4.Cheers,Dani
dev mailing list
dev lists openshift redhat com