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 <[email protected]> wrote: > Yes, that'll probably have to be a point change. > > On Mon, Jul 31, 2017 at 11:02 PM, Andrew Lau <[email protected]> > wrote: > >> I think the node images are still missing the sdn-ovs package. >> >> On Tue, 1 Aug 2017 at 07:45 Clayton Coleman <[email protected]> wrote: >> >>> This has been fixed and images were repushed. >>> >>> On Mon, Jul 31, 2017 at 12:13 PM, Clayton Coleman <[email protected]> >>> wrote: >>> >>>> Hrm, so they do. Looking. >>>> >>>> On Mon, Jul 31, 2017 at 11:57 AM, Andrew Lau <[email protected]> >>>> 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 just got merged for a missing package in the >>>>> node image https://github.com/openshift/origin/pull/15542 >>>>> >>>>> On Tue, 1 Aug 2017 at 01:34 Clayton Coleman <[email protected]> >>>>> wrote: >>>>> >>>>>> 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 mailing list >>>>>> [email protected] >>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>>>>> >>>>> >>>> >>> >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
