yahoo-eng-team team mailing list archive

[Armando Migliaccio <1652748@xxxxxxxxxxxxxxxxxx>]

This issue as reported seem to be related to the specific (downstream)
distribution used to deploy and operate OpenStack.

** Also affects: mos
   Importance: Undecided
       Status: New

** Changed in: neutron
       Status: New => Invalid

** Changed in: neutron
     Assignee: siyingchun (wintersi) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1652748

Title:
  Sometimes the controller may exist more than one L3-agent/DHCP-agent
  /Metadata-agent.

Status in Mirantis OpenStack:
  New
Status in neutron:
  Invalid

Bug description:
  We have a large scale of openstack clusters, sometimes the controller
  node may exist more than one L3-agent/DHCP-agent/Metadata-agent, after
  the whole environment works correctly several days.

  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/DHCP-agent/Metadata-agent exists 

  * Actual result:
  Two L3-agent/DHCP-agent/Metadata-agent exist 

  * 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mos/+bug/1652748/+subscriptions