[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: problem with installation of Okd 3.11



I've faced the same issue on 3.9 and the issue was nodes was unable to close an SSL connection to master in order to create that `80-openshift-network.conf` file under `/etc/cni/net.d. AFAIK, this is origin-node's job.

Check if there are any error logs regarding unable to connect to master. Raise node logLevel to >=4 in /etc/sysconfig/origin-node
--
Mateus Caruccio / Master of Puppets
GetupCloud.com 
We make the infrastructure invisible
Gartner Cool Vendor 2017


Em qua, 28 de nov de 2018 às 03:13, Dharmit Shah <dshah redhat com> escreveu:
On 27/11, Erekle Magradze wrote:
> Hi,
>
> Can you please drop the link to github issue here?

Sorry for missing that out in my original response. Here's the link to
the issue: https://github.com/openshift/openshift-ansible/issues/10690

Regards,
Dharmit

> On 11/27/18 3:02 PM, Dharmit Shah wrote:
> > On 27/11, Erekle Magradze wrote:
> > >           Nov 26 06:55:55 os-master origin-node: E1126
> > >           06:55:53.495294    5353 kubelet.go:2101] Container runtime
> > >           network not ready: NetworkReady=false
> > >           reason:NetworkPluginNotReady message:docker: network plugin is
> > >           not ready: cni config uninitialized
> > >           Nov 26 06:55:58 os-master origin-node: W1126 06:55:58.496250
> > >           5353 cni.go:172] Unable to update cni config: No networks
> > >           found in /etc/cni/net.d
> > I faced similar error while upgrading from OKD 3.9 to 3.10. While trying
> > to bring up the master node, openshift-ansible always failed and
> > journalctl had similar logs. Looking around, I figured that this was due
> > to missing `80-openshift-network.conf` file under `/etc/cni/net.d` on
> > the master node. Other nodes had this file.
> >
> > So I copy pasted the file from a node to master and then `oc get nodes`
> > showed me "Ready" instead of "NotReady" for the master. I then tried to
> > update again from 3.9 to 3.10 but would fail with same error and same
> > issue. I opened a GitHub issue [1] with all the details I could find but
> > I haven't received any help yet.
> >
> > However, in my case issue was with 3.9 to 3.10 upgrade.
> >
> > Regards,
> > Dharmit
> >

--
Dharmit Shah
Red Hat Developer Tools (https://developers.redhat.com/)
irc, mattermost: dharmit
https://dharmitshah.com

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]