yahoo-eng-team team mailing list archive

[LIU Yulong <1911864@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Neutron creates N NetworkDhcpAgentBindings (N is equal to
dhcp_agents_per_network) for network even if the subnets disabled the
dhcp. This means no matter the DHCP state, the dhcp_scheduler will
schedule the network anyway.

Reproduce steps:
$ source demo_rc
$ openstack network create 111
$ openstack subnet create --no-dhcp --subnet-range 1.1.1.0/24 --network 871c588b-2582-4a08-bff7-d92e1590eecd 111-subnet

$ source admin_rc
$ openstack network agent list --network 871c588b-2582-4a08-bff7-d92e1590eecd
+--------------------------------------+------------+----------+-------------------+-------+-------+--------------------+
| ID                                   | Agent Type | Host     | Availability Zone | Alive | State | Binary             |
+--------------------------------------+------------+----------+-------------------+-------+-------+--------------------+
| c9921687-30ee-470e-813f-6e45247b57f1 | DHCP agent | network2 | nova              | :-)   | UP    | neutron-dhcp-agent |
+--------------------------------------+------------+----------+-------------------+-------+-------+--------------------+

Then this behavior has a result is that HA network for HA routers will
also have such bindings.

Because the external network will not have VM created normally, so its
subnets' enable_dhcp are all disabled. Again, the bindings are created.

Good news is that in DHCP agent side dhcp-namespace and dnsmasq are not
created.

So, basically this is inconsitent between neutron server side and DHCP
agent side.

So, I have some thoughts about this is to add config option to disable
some types of network's dhcp agent binding.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  [DHCP] AgentBinding for network will be created no matter the state

Status in neutron:
  New

Bug description:
  Neutron creates N NetworkDhcpAgentBindings (N is equal to
  dhcp_agents_per_network) for network even if the subnets disabled the
  dhcp. This means no matter the DHCP state, the dhcp_scheduler will
  schedule the network anyway.

  Reproduce steps:
  $ source demo_rc
  $ openstack network create 111
  $ openstack subnet create --no-dhcp --subnet-range 1.1.1.0/24 --network 871c588b-2582-4a08-bff7-d92e1590eecd 111-subnet

  $ source admin_rc
  $ openstack network agent list --network 871c588b-2582-4a08-bff7-d92e1590eecd
  +--------------------------------------+------------+----------+-------------------+-------+-------+--------------------+
  | ID                                   | Agent Type | Host     | Availability Zone | Alive | State | Binary             |
  +--------------------------------------+------------+----------+-------------------+-------+-------+--------------------+
  | c9921687-30ee-470e-813f-6e45247b57f1 | DHCP agent | network2 | nova              | :-)   | UP    | neutron-dhcp-agent |
  +--------------------------------------+------------+----------+-------------------+-------+-------+--------------------+

  Then this behavior has a result is that HA network for HA routers will
  also have such bindings.

  Because the external network will not have VM created normally, so its
  subnets' enable_dhcp are all disabled. Again, the bindings are
  created.

  Good news is that in DHCP agent side dhcp-namespace and dnsmasq are
  not created.

  So, basically this is inconsitent between neutron server side and DHCP
  agent side.

  So, I have some thoughts about this is to add config option to disable
  some types of network's dhcp agent binding.

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