We're starting to have this kind of issues lately too (500, 503, etc.).
Only solution is to delete the registry pod and sometimes even the router +
ipfailover.
​Especially when pods start failing to be deployed, with events:
Container image "
172.30.68.98:5000/myproject/myimage@sha256:033b2937b3bf
How did you create the registry? Do you have a set of ENV vars
defined on the registry deployment config?
On Wed, Mar 16, 2016 at 2:44 PM, Robert Wehner
wrote:
> It looks like it is "oadm v1.1.2-1-gbe558b1".
>
>
> --
> Robert Wehner
> Return Path
>
> On Wed, Mar 16, 2016 at 12:43 PM, Clayton Col
I'm having trouble getting my builds to push to an internal registry. I'm
running Origin v1.1.2. When I run through the nodejs example (
https://docs.openshift.org/latest/getting_started/developers/developers_console.html),
the build always fails pushing to the internal registry with this error:
I
It looks like it is "oadm v1.1.2-1-gbe558b1".
--
Robert Wehner
Return Path
On Wed, Mar 16, 2016 at 12:43 PM, Clayton Coleman
wrote:
> What version of oadm are you running?
>
> On Wed, Mar 16, 2016 at 2:32 PM, Robert Wehner
> wrote:
> > I'm having trouble getting my builds to push to an intern
I've gotten this working again, but I'm not sure how/why it stopped working
in the first place but I think ti was somehow related to the secrets
created with the registry. Perhaps one of them got changed or corrupted
(maybe when I took the nodes down to patch last week). Anyway, I was
deleting the
