OpenvSwitch service doesn't restart after a failure automatically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Alexander Rubtsov |
Bug Description
--- Environment ---
MOS 9.2 (build 606)
--- Description ---
OpenvSwitch service doesn't start after a failure automatically
--- Steps to reproduce ---
1) Deploy an OpenStack environment
2) Log into a Controller node
3) Determine PID of OpenvSwitch process:
[root@node-1 ~]$ ps aux | grep "ovs-vswitchd.
root 7046 0.1 0.3 246308 7224 ? S<Ll May21 4:05 ovs-vswitchd unix:/var/
4) Kill this process
kill -9 7046
5) Wait for a while
6) Check the OpenvSwitch process again
ps aux | grep "ovs-vswitchd.
--- Actual result ---
There is no OpenvSwitch process running
--- Expected result ---
OpenvSwitch process is running again:
root 13679 0.3 0.1 246308 3304 ? S<Ll 10:03 0:00 ovs-vswitchd unix:/var/
--- Notes ---
- 1 -
The corresponding Upstart service is not configured to auto-restart:
[root@node-1 ~]$ grep -i "respawn" /etc/init/
[root@node-1 ~]$
However, many other services on Controller nodes are configured to auto-restart:
[root@node-1 ~]$ grep -rl "respawn" /etc/init/ | wc -l
66
- 2 -
The service doesn't notice killing of the corresponding process
[root@node-1 ~]$ service openvswitch-switch status
openvswitch-switch start/running
[root@node-1 ~]$ kill -9 13679
[root@node-1 ~]$ ps aux | grep "ovs-vswitchd.
[root@node-1 ~]$ service openvswitch-switch status
openvswitch-switch start/running
Changed in fuel: | |
milestone: | 9.x-updates → 9.2-mu-7 |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | MOS Maintenance (mos-maintenance) → Alexander Rubtsov (arubtsov) |
status: | Confirmed → Invalid |
milestone: | 9.2-mu-7 → 9.x-updates |
sla2 for 9.0-updates