[network][chef client 12] The error return value of `service openvswitch status` makes chef cannot start openvswitch if openvswitch stopped

Bug #1310962 reported by Feng Ju on 2014-04-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack + Chef
Medium
Unassigned

Bug Description

The `service openvswitch status` will return 0 even if openvswitch stopped.
This will make openvswitch stopped forever if openvswitch stopped for some reason.
It's openvswtich bug but we can fix it in the our cookbook.

I searched and found that puppet has fixed this in it's code.
https://bugs.launchpad.net/puppet-vswitch/+bug/1288659
we can refer to it.

Mark Vanderwiel (vanderwl) wrote :

I believe this is handled by the Chef service provider class: chef\lib\chef\provider\service\upstart.rb Therefore you need to write a defect against Chef itself is there's an issue with that. Might need to update your Chef version to pick up that support.

Please verify what levels of cookbooks and Chef your are using.

Changed in openstack-chef:
status: New → Incomplete
Changed in openstack-chef:
milestone: none → juno-rc1
JJ Asghar (d-jj) wrote :

chef-client 12 should resolve this issue.

Changed in openstack-chef:
status: Incomplete → Fix Committed
summary: - The error return value of `service openvswitch status` makes chef
- cannot start openvswitch if openvswitch stopped
+ [network][chef client 12] The error return value of `service openvswitch
+ status` makes chef cannot start openvswitch if openvswitch stopped
JJ Asghar (d-jj) on 2014-11-25
Changed in openstack-chef:
importance: Undecided → Medium
JJ Asghar (d-jj) on 2015-01-14
Changed in openstack-chef:
milestone: juno-rc1 → kilo-rc1
Changed in openstack-chef:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers