yahoo-eng-team team mailing list archive

[Elvira García Ruiz <2073894@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When updating a port, we sometimes need to check dns nameserver ips.
When this happens, if the DNS resolver file (resolv.conf) includes an
address with scope like fe80::5054:ff:fe96:8af7%eth2, oslo_utils
is_valid_ipv6 detects this as valid ipv6 input, but netaddr will raise
an exception since this is not strictly just the IPv6 address, and
therefore the port update fails with a raised exception and the port is
deleted.

On a normal scenario, this means that the metadata port cannot be
spawned and therefore no VMs can be properly configured using metadata.

[resolv.conf example]
# Generated by NetworkManager
nameserver 10.0.0.1
nameserver fe80::5054:ff:fe96:8af7%eth2
nameserver 2620:52:0:13b8::fe

This was found on an environment using Train, but affects every version.

100% Reproducible, just need to try to spawn a VM on an environment with
the resolv.conf similar to the example.

Traceback found on controller logs:
https://paste.opendev.org/show/bzqgpsJRifX0uovHw5nJ/

>From the compute logs we see the metadata port was deleted after the
exception:

2024-07-18 04:38:06.036 49524 DEBUG networking_ovn.agent.metadata.agent
[-] There is no metadata port for network
75b73d16-cb05-42d1-84c5-19eccf3a252d or it has no MAC or IP addresses
configured, tearing the namespace down if needed _get_provision_params
/usr/lib/python3.6/site-
packages/networking_ovn/agent/metadata/agent.py:474

** Affects: neutron
     Importance: Undecided
     Assignee: Elvira García Ruiz (elviragr)
         Status: New

** Affects: oslo.utils
     Importance: Undecided
     Assignee: Elvira García Ruiz (elviragr)
         Status: New

** Also affects: oslo.utils
   Importance: Undecided
       Status: New

** Changed in: oslo.utils
     Assignee: (unassigned) => Elvira García Ruiz (elviragr)

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

Title:
  IPv6 dns nameservers described with their scope on the IP are not
  supported

Status in neutron:
  New
Status in oslo.utils:
  New

Bug description:
  When updating a port, we sometimes need to check dns nameserver ips.
  When this happens, if the DNS resolver file (resolv.conf) includes an
  address with scope like fe80::5054:ff:fe96:8af7%eth2, oslo_utils
  is_valid_ipv6 detects this as valid ipv6 input, but netaddr will raise
  an exception since this is not strictly just the IPv6 address, and
  therefore the port update fails with a raised exception and the port
  is deleted.

  On a normal scenario, this means that the metadata port cannot be
  spawned and therefore no VMs can be properly configured using
  metadata.

  [resolv.conf example]
  # Generated by NetworkManager
  nameserver 10.0.0.1
  nameserver fe80::5054:ff:fe96:8af7%eth2
  nameserver 2620:52:0:13b8::fe

  This was found on an environment using Train, but affects every
  version.

  100% Reproducible, just need to try to spawn a VM on an environment
  with the resolv.conf similar to the example.

  Traceback found on controller logs:
  https://paste.opendev.org/show/bzqgpsJRifX0uovHw5nJ/

  From the compute logs we see the metadata port was deleted after the
  exception:

  2024-07-18 04:38:06.036 49524 DEBUG
  networking_ovn.agent.metadata.agent [-] There is no metadata port for
  network 75b73d16-cb05-42d1-84c5-19eccf3a252d or it has no MAC or IP
  addresses configured, tearing the namespace down if needed
  _get_provision_params /usr/lib/python3.6/site-
  packages/networking_ovn/agent/metadata/agent.py:474

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