OpenShift Origin v3.6.0 is released

2017-07-31 Thread Clayton Coleman
https://github.com/openshift/origin/releases/tag/v3.6.0 Images are pushed to the hub. Thanks to everyone for their hard work this release. Expect official RPMs in a few days. Remember to use the Ansible release-3.6 branch for your installs. ___ dev

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Andrew Lau
The images still seem to be using rc0 packages. rpm -qa | grep origin origin-clients-3.6.0-0.rc.0.359.de23676.x86_64 origin-3.6.0-0.rc.0.359.de23676.x86_64 I also had a PR which just got merged for a missing package in the node image https://github.com/openshift/origin/pull/15542 On Tue, 1 Aug

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Clayton Coleman
Hrm, so they do. Looking. On Mon, Jul 31, 2017 at 11:57 AM, Andrew Lau wrote: > The images still seem to be using rc0 packages. > > rpm -qa | grep origin > origin-clients-3.6.0-0.rc.0.359.de23676.x86_64 > origin-3.6.0-0.rc.0.359.de23676.x86_64 > > I also had a PR which

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Clayton Coleman
This has been fixed and images were repushed. On Mon, Jul 31, 2017 at 12:13 PM, Clayton Coleman wrote: > Hrm, so they do. Looking. > > On Mon, Jul 31, 2017 at 11:57 AM, Andrew Lau > wrote: > >> The images still seem to be using rc0 packages. >> >>

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Andrew Lau
I think the node images are still missing the sdn-ovs package. On Tue, 1 Aug 2017 at 07:45 Clayton Coleman wrote: > This has been fixed and images were repushed. > > On Mon, Jul 31, 2017 at 12:13 PM, Clayton Coleman > wrote: > >> Hrm, so they do.

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Clayton Coleman
Yes, that'll probably have to be a point change. On Mon, Jul 31, 2017 at 11:02 PM, Andrew Lau wrote: > I think the node images are still missing the sdn-ovs package. > > On Tue, 1 Aug 2017 at 07:45 Clayton Coleman wrote: > >> This has been fixed and

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Andrew Lau
Does that not prevent pods from booting? At least in my case when I was building some test RPMs, pods were unable to start up with an error "cni config unintialized". On Tue, 1 Aug 2017 at 13:21 Clayton Coleman wrote: > Yes, that'll probably have to be a point change. > >