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

Re: [v4]: v4.1.4 is using internal registry, is this a bug?





On Thu, Jul 18, 2019 at 11:35 PM Clayton Coleman <ccoleman redhat com> wrote:


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 [1] 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.
[DC]: thank you for the info, learnt something new. (one day i'll learn how this promotion works and how is triggered)



For your first error message, which installer binary were you using?  Can you link to it directly?

Are you positive you were installing from that binary?  I just double checked locally and that listed a quay.io release image.

[DC]: i'm no longer positive, sorry for the noise and for wasting your time. :facepalm

[dani-dev in ~/Downloads]# wget https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.1.4/openshift-install-mac-4.1.4.tar.gz
--2019-07-18 23:41:46--  https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.1.4/openshift-install-mac-4.1.4.tar.gz
Resolving mirror.openshift.com (mirror.openshift.com)... 54.172.163.83
Connecting to mirror.openshift.com (mirror.openshift.com)|54.172.163.83|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 56179054 (54M) [application/x-gzip]
Saving to: ‘openshift-install-mac-4.1.4.tar.gz’

openshift-install-mac-4.1.4.tar.gz                 100%[==============================================================================================================>]  53.58M  7.67MB/s    in 10s

2019-07-18 23:41:57 (5.21 MB/s) - ‘openshift-install-mac-4.1.4.tar.gz’ saved [56179054/56179054]

[dani-dev in ~/Downloads]# md5sum openshift-install-mac-4.1.4.tar.gz
71fd99d94dc1062a52d43b2ca83900fa  openshift-install-mac-4.1.4.tar.gz
[dcomnea DCOMNEA-M-M29F in ~/Downloads]# tar xzvf openshift-install-mac-4.1.4.tar.gz
x README.md
x openshift-install
[dani-dev in ~/Downloads]# md5sum openshift-install
dedb9c8d0c66861ebb3e620e32cef438  openshift-install
[dani-dev in ~/Downloads]# ./openshift-install version
./openshift-install v4.1.4-201906271212-dirty
built from commit ca5d270bc8d554496f0aa1073bdaa67adf01a25a
release image quay.io/openshift-release-dev/ocp-release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163a
[dani-dev in ~/Downloads]#


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 by 


Manually trying from withing bootstrap node to check if it works .. i get same negative result


Switching 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
./openshift-install v4.1.4-201906271212-dirty
built from commit bf47826c077d16798c556b1bd143a5bbfac14271
release image registry.svc.ci.openshift.org/ocp/release sha256:a6c177eb007d20bb00bfd8f829e99bd40137167480112bd5ae1c25e40a4a163a

but 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
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

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