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

Nodes 'NotReady' after reboot,'origin-node' service fails to start- "no port named vxlan0"



Another issue i am facing is with nodes which are in NotReady status after reboot.

Out of 3 nodes 2 are in NotReady and one is in ready state.

oc get no
NAME           LABELS                                STATUS                        AGE
10.99.10.191   kubernetes.io/hostname=10.99.10.191   NotReady                                         1d
10.99.10.192   kubernetes.io/hostname=10.99.10.192   Ready                                               1d
10.99.10.193   kubernetes.io/hostname=10.99.10.193   NotReady,SchedulingDisabled    1d

when i checked the status of "origin-node" service it shows issue with vxlan port in ovs,but this port is actually present in ovs.

systemctl status origin-node
origin-node.service - Origin Node
   Loaded: loaded (/usr/lib/systemd/system/origin-node.service; enabled)
  Drop-In: /usr/lib/systemd/system/origin-node.service.d
           ââopenshift-sdn-ovs.conf
   Active: failed (Result: exit-code) since Sun 2015-10-11 12:40:57 EDT; 37min ago
     Docs: https://github.com/openshift/origin
 Main PID: 2221 (code=exited, status=255)

Oct 11 12:40:56 node1 ovs-vsctl[2268]: ovs|00002|vsctl|ERR|no port named vxlan0
Oct 11 12:40:56 node1 ovs-vsctl[2269]: ovs|00001|vsctl|INFO|Called as ovs-vsctl add-port br0 vxlan0 -- set Interface vxlan0 type=vxlan options:remote_ip=flow options:key=flow ofport_request=1
Oct 11 12:40:56 node1 ovs-vsctl[2270]: ovs|00001|vsctl|INFO|Called as ovs-vsctl add-port br0 tun0 -- set Interface tun0 type=internal ofport_request=2
Oct 11 12:40:56 node1 ovs-vsctl[2292]: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port br0 vovsbr
Oct 11 12:40:56 node1 ovs-vsctl[2293]: ovs|00001|vsctl|INFO|Called as ovs-vsctl add-port br0 vovsbr -- set Interface vovsbr ofport_request=9
Oct 11 12:40:57 node1 origin-node[2221]: F1011 12:40:57.022525    2221 node.go:85] ERROR: Unable to check for Docker server version.
Oct 11 12:40:57 node1 origin-node[2221]: unexpected EOF
Oct 11 12:40:57 node1 systemd[1]: origin-node.service: main process exited, code=exited, status=255/n/a
Oct 11 12:40:57 node1 systemd[1]: Failed to start Origin Node.
Oct 11 12:40:57 node1 systemd[1]:


Manually starting the service using "systemctl start origin-node" will change the status to Ready,but causes other issues like failing to reach registry container etc.

 ovs-vsctl show
1c0b52c8-f3c8-42e1-89c2-2ba60c1b91ff
    Bridge "br0"
        fail_mode: secure
        Port vovsbr
            Interface vovsbr
        Port "vxlan0"
            Interface "vxlan0"
                type: vxlan
                options: {key=flow, remote_ip=flow}
        Port "tun0"
            Interface "tun0"
                type: internal
        Port "br0"
            Interface "br0"
                type: internal
    ovs_version: "2.3.1"


Any idea about this behaviour.Tried couple of reboots but doesn't make any difference.

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