Neutron DHCP agent should have upstart script disabled

Bug #1495133 reported by Andrey Grebennikov on 2015-09-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Low
Matthew Mosesohn
7.0.x
Low
Fuel Library (Deprecated)

Bug Description

Fuel 6.1 Ubuntu.

Neutron DHCP and Neutron L3 services should be only able to be started by Pacemaker.
Per @xarses the upstart scripts should not allow to start them. In fact, if I execute "start neutron-dhcp-agent" on the controller in can be successfully started and I get 2 instances of the dhcp agent.

Vladimir Kuklin (vkuklin) wrote :

Andrey, you can even run commands 'su neutron "neutron-l3-agent" &' for example and you will still start l3-agent. So far, there are not so many ways to not let user to shoot himself in the foot. The same stands true for mysql and other services. The only thing we can do this is to provide our users with good documentation.

tags: added: docs release-notes
Changed in fuel:
importance: Undecided → Low
Dmitry Pyzhov (dpyzhov) on 2015-10-12
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov) on 2015-10-22
tags: added: area-library
tags: added: team-bugfix
Dmitry Pyzhov (dpyzhov) on 2015-12-29
Changed in fuel:
milestone: 8.0 → 9.0
Matthew Mosesohn (raytrac3r) wrote :

root@node-2:/etc/init# cat neutron*agent.override

manual
manual
manual

This was done a long time ago it seems.

Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Matthew Mosesohn (raytrac3r)
status: Confirmed → Invalid
Matthew Mosesohn (raytrac3r) wrote :

For release notes:

All corosync managed services (RabbitMQ, neutron agents, MySQL, etc) are installed with an override file in /etc/init/SERVICENAME.overide. This blocks upstart from starting this service automatically, but it does not prohibit a user from manually running /etc/init.d/SERVICENAME start. Blocking this could be possible with some workarounds, but an administrator could start a duplicate copy of the service through many methods. There should be no scenario where services run duplicate instances, so this solution in place is adequate.

tags: added: release-notes-done
removed: release-notes
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers