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

2019-07-18 Thread Daniel Comnea
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 *error pulling image >

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

2019-07-18 Thread Clayton Coleman
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. For your first error message, which installer binary were you using? Can you link to it directly? On Thu, Jul 18, 2019 at 3:55 PM Daniel Comnea wrote: > Hi, > >

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

2019-07-18 Thread Daniel Comnea
On Thu, Jul 18, 2019 at 10:08 PM Clayton Coleman 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. [1]

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

2019-07-18 Thread Clayton Coleman
On Jul 18, 2019, at 6:24 PM, Daniel Comnea wrote: On Thu, Jul 18, 2019 at 10:08 PM Clayton Coleman 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

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

2019-07-18 Thread Daniel Comnea
On Thu, Jul 18, 2019 at 11:35 PM Clayton Coleman wrote: > > > On Jul 18, 2019, at 6:24 PM, Daniel Comnea wrote: > > > > On Thu, Jul 18, 2019 at 10:08 PM Clayton Coleman > 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