Re: Can't push images after 1.3.0 upgrade

2017-01-05 Thread Philippe Lafoucrière 
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

2017-01-05 Thread Philippe Lafoucrière 
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:
sha256:fa1f5a94b89552b2c9d370c7ff779d658e09547eae00d931a3b1f2502f1f7260
size: 3339



Cordialement,
Philippe Lafoucrière

-- 
Philippe Lafoucrière - CEO
http://www.tech-angels.com
https://gemnasium.com
France : +33 (0) 3 65 96 02 92
Canada: +1 (418) 478-1175
USA: +1 (954) 607-7443



On Thu, Jan 5, 2017 at 8:49 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:

> 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
>
___
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

2017-01-05 Thread Philippe Lafoucrière 
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
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Skydive in Origin?

2017-01-05 Thread Subhendu Ghosh 
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
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Blue/Green control plane upgrade

2017-01-05 Thread Andrew Butcher 
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 process. I'm doing tests but would appreciate some feedback
> and/or battle stories.
>
> - Add new masters and etcd hosts to inventory - remove any application
> nodes
> - Run ansible-playbook (not scale up)
> - Join new etcd hosts with etcdctl
>
> Config and new image versions should be updated from the playbook.
>
> I'm confused about the dependency on first master, it seems to be
> referenced in ansible for CA provisioning and config generation. If the
> first master goes down does the /etc/origin/generated-config then need to
> be sync'd over to the replacement first master?
>

/etc/origin/generated-configs contains all openshift certificates that were
created as part of install. There should be no need to keep
/etc/origin/generated-configs since the certificate tarballs have already
been distributed to nodes, masters, etc.

Similarly, the first etcd host stores generated certificates
in /etc/etcd/generated_certs but requires /etc/etcd/ca to sign new
certificates. /etc/etcd/ca is currently not synced with other etcd hosts.
This is something we're looking to correct with some upcoming refactors.

Thanks
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users