yahoo-eng-team team mailing list archive

[Lucas Alvares Gomes <1888649@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The patch [0] added validations to the DHCP options passed to OVN via
the Neutron API because, not all existing DHCP options are supported by
the OVN DHCP.

Some projects such as Ironic uses a dnsmasq syntax when passing those
options, for example [1]: "tag:ipxe,<option name>". Which is not
understood by the OVN driver for Neutron causing the validation to fail
the API request.

But by failing the API request we also break the combination of using
Ironic + OVN + Neutron DHCP agent, where the agent is able to understand
that syntax and boot the baremetal instances via the network.

Due to that problem, I believe the OVN driver should stop failing the
API request for the options it doesn't understand and instead log an
error message so that it's visible to the cloud operator.

[0] https://review.opendev.org/#/c/722025/
[1] https://github.com/openstack/ironic/blob/19866e3ddbff1953a5ed6fb3abd11d7f649238fa/ironic/common/pxe_utils.py#L472-L487

** Affects: neutron
     Importance: High
     Assignee: Lucas Alvares Gomes (lucasagomes)
         Status: New


** Tags: ovn

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
     Assignee: (unassigned) => Lucas Alvares Gomes (lucasagomes)

** Changed in: neutron
   Importance: Medium => High

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

Title:
  OVN: Extra DHCP options validation broke the Ironic+OVN+DHCP agent
  combination

Status in neutron:
  New

Bug description:
  The patch [0] added validations to the DHCP options passed to OVN via
  the Neutron API because, not all existing DHCP options are supported
  by the OVN DHCP.

  Some projects such as Ironic uses a dnsmasq syntax when passing those
  options, for example [1]: "tag:ipxe,<option name>". Which is not
  understood by the OVN driver for Neutron causing the validation to
  fail the API request.

  But by failing the API request we also break the combination of using
  Ironic + OVN + Neutron DHCP agent, where the agent is able to
  understand that syntax and boot the baremetal instances via the
  network.

  Due to that problem, I believe the OVN driver should stop failing the
  API request for the options it doesn't understand and instead log an
  error message so that it's visible to the cloud operator.

  [0] https://review.opendev.org/#/c/722025/
  [1] https://github.com/openstack/ironic/blob/19866e3ddbff1953a5ed6fb3abd11d7f649238fa/ironic/common/pxe_utils.py#L472-L487

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