yahoo-eng-team team mailing list archive

[OpenStack Infra <1942794@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/807692
Committed: https://opendev.org/openstack/neutron/commit/bd0ded15ca21161c0f20679477445f4e31128267
Submitter: "Zuul (22348)"
Branch:    master

commit bd0ded15ca21161c0f20679477445f4e31128267
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Tue Sep 7 08:52:21 2021 +0000

    [OVN] Update the DHCP options when the metadata port is modified
    
    Always update the DHCP options when the metadata port is created,
    updated or deleted. If the metadata port IP addresses are updated,
    the DHCP options register should be too, modifying the static routes
    defined in "DHCP_Options.options.classless_static_route".
    
    These static routes will be injected in the VM in the DHCP request.
    The IP address of the metadata port should match with the static
    route redirecting the traffic to the metadata IP address
    "169.254.169.254/32":
    
      $ ip r
      default via 10.0.0.1 dev eth0
      10.0.0.0/28 dev eth0 scope link  src 10.0.0.7
      169.254.169.254 via 10.0.0.2 dev eth0  # 10.0.0.2 is the metadata
                                             # port IP address
    
    Closes-Bug: #1942794
    Change-Id: Id5d4909caa521a899b97d83bdc1963b010e97dac


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  [OVN] "DHCP_Options" is not updated when the metadata port IPs are

Status in neutron:
  Fix Released

Bug description:
  In OVN, the DHCP server will inject into the VM the routes defined in
  "DHCP_Options" register. There is "DHCP_Option" per subnet with DHCP
  enabled.

  The "DHCP_Options.options.classless_static_route" is a set of static
  routes defined in the root namespace of the VM. If the OVN metadata is
  enabled, a static route will be created to send traffic to the
  metadata IP "169.254.169.254/32", using the metadata port IP.

  Currently, if the user manually changes this IP address (the metadata
  port should have only one IP address per subnet), this is not updated
  in the corresponding "DHCP_Option" register.

  Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1994591

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