Sometimes the controller may exist more than one L3-agent/DHCP-agent/Metadata-agent.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Committed
|
Wishlist
|
Andrii Kroshchenko |
Bug Description
We have a large scale of openstack clusters, sometimes the controller node may exist more than one L3-agent/
Our environment is mainly based on Mirantis Fuel 7.0, many services are monitored and managed by pacemaker that is a very powerful and automantic tool. Also there are four services controlled by pacemaker, for example, L3-agent, DHCP-agent, ovs-agent and neutron meta-data agent. So administrator and any other users have no need to manage and operate them, but ...... what happened? And here is the key reason that administrator and other users unexpectedly don't find them because of unknown reasons, for instance, using linux bash shell "ps -ef | grep L3-agent", they may use types of tools to restart these services, e.g. "service *** start", "systemctl *** start" ......
As a result, it looks ok, and the crash service works again, however it is just managed by linux bash, and pacemaker don't know what happened and regularly start this crash service by himself, so TWO the same services have been started and they work dependently.
Or any other non man-made factors, so it should be checked when system wants to start a new *-agent.
* Pre-condition:
You have a large scale environment or a small test one when it works several days.
* Step-by-step:
In controller, when you type the list of commands, like "neutron agent-list, check *-agents"
* Expect result:
Only one L3-agent/
* Actual result:
Two L3-agent/
* Version:
Openstack Newton, deployed with Fuel 10.0
Ubuntu Ubuntu 16.04.1 LTS, running kernel 4.4.0-57-generic
Neutron version 5.1.0
Changed in neutron: | |
assignee: | nobody → siyingchun (wintersi) |
Changed in mos: | |
assignee: | MOS Packaging Team (mos-packaging) → Andrii Kroshchenko (akroshchenko) |
Changed in mos: | |
assignee: | Andrii Kroshchenko (akroshchenko) → nobody |
assignee: | nobody → MOS Packaging Team (mos-packaging) |
Changed in mos: | |
assignee: | MOS Packaging Team (mos-packaging) → Andrii Kroshchenko (akroshchenko) |
This issue as reported seem to be related to the specific (downstream) distribution used to deploy and operate OpenStack.