This bug was initially created as a copy of Bug #1722578 This is for OSP14 Description of problem: Sometimes after a reboot of a compute node, the compute node/server stays unreachable. In order to remediate the issue network.service needs to be restarted. From `messages.log` we suspect the network isn't brought up correctly and the bond (OVS) is brought up before the network interface: ~~~ 2019-05-31 10:00:20 +02:00 d100siul0555 kern.info kernel: device em1 entered promiscuous mode 2019-05-31 10:00:20 +02:00 d100siul0555 kern.info kernel: device p1p1 entered promiscuous mode 2019-05-31 10:00:23 +02:00 d100siul0555 kern.info kernel: IPv6: ADDRCONF(NETDEV_UP): em1: link is not ready 2019-05-31 10:00:23 +02:00 d100siul0555 kern.info kernel: IPv6: ADDRCONF(NETDEV_UP): p1p1: link is not ready 2019-05-31 10:00:24 +02:00 d100siul0555 daemon.notice ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -t 10 -- --if-exists del-port br-ex bond0 -- add-bond br-ex bond0 p1p1 em1 bond_mode=active-backup 2019-05-31 10:00:24 +02:00 d100siul0555 daemon.info network: Bringing up interface bond0: [ OK ] <<== Bond is brought up 2019-05-31 10:00:26 +02:00 d100siul0555 kern.info kernel: igb 0000:20:00.0 p1p1: igb: p1p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX <<<===NIC is brought up 2019-05-31 10:00:26 +02:00 d100siul0555 kern.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): p1p1: link becomes ready 2019-05-31 10:00:27 +02:00 d100siul0555 kern.info kernel: ixgbe 0000:08:00.0 em1: NIC Link is Up 1 Gbps, Flow Control: None 2019-05-31 10:00:27 +02:00 d100siul0555 kern.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): em1: link becomes ready 2019-05-31 10:00:36 +02:00 d100siul0555 daemon.info network: Bringing up interface em1: [ OK ] <<<===NIC is brought up 2019-05-31 10:00:38 +02:00 d100siul0555 daemon.info network: Bringing up interface p1p1: [ OK ] <<<===NIC is brought up ~~~ Version-Release number of selected component (if applicable): RHOSP 13.0 RHEL 7.6 How reproducible: The issue is occasional. The customer says it happens on 1 out of 10 reboots. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3750