Re: Can't push images after 1.3.0 upgrade

Hmm, I got it working by removing the :443 in our repo url (while this port was needed before to be able to push...) ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Can't push images after 1.3.0 upgrade

It's really the images layers patching which is blocking. I can pull an image from the registry, and push it again with no error: The push refers to a repository [our-registry:443/projectname/theimagestream] 38731c91ef63: Layer already exists 7d7e09f222b3: Layer already exists latest: digest:

Re: Can't push images after 1.3.0 upgrade

I'm digging this up. We just upgraded our production cluster to OS 1.3, and having this issue again. Builds are working as expected, but we can't push using our CI any more, with the same exact symptoms as above :( Any idea? I have tried to reconcile roles, with no success. Thanks

Skydive in Origin?

Any plans to include skydive integration with 2 network plugins ? Anyone tried to use skydive with origin or OpenShift? http://github.com/skydive-project/skydive Subhendu ___ users mailing list users@lists.openshift.redhat.com

Re: Blue/Green control plane upgrade

On Tue, Jan 3, 2017 at 8:32 PM, Andrew Lau wrote: > Hi, > > Has anyone had any experience in upgrading control plane with the > blue/green method (containerisation install)? > > Preps for upgrading to 1.4 I want to redeploy parts of the control plane > as part of the