yahoo-eng-team team mailing list archive

[Krzysztof Klimonda <1940541@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Since e4fb06b24299a7ecf10b05ef6ddc2d883c40e5a1 ([ovn] Add neutron
network to metadata namespace names) ovn metadata agent saves neutron
uuid in external-ids for chassis to indicate that it's ready to serve
metadata for network.

When this patch was merged, a metadata readiness check wasn't updated
and so it looks for ovn datapath uuid in external-ids instead of neutron
network uuid, delaying processing of UP port state by 15 seconds.

This check has been dropped in master, and I'll prepare backports to
ussuri, victoria and wallaby to also drop that check. Alternatively, I
have a patch that handles both datapath and neutron uuids in external-
ids if it's preferred.

** 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/1940541

Title:
  [ovn] metadata readiness check is looking for wrong uuid in chassis

Status in neutron:
  New

Bug description:
  Since e4fb06b24299a7ecf10b05ef6ddc2d883c40e5a1 ([ovn] Add neutron
  network to metadata namespace names) ovn metadata agent saves neutron
  uuid in external-ids for chassis to indicate that it's ready to serve
  metadata for network.

  When this patch was merged, a metadata readiness check wasn't updated
  and so it looks for ovn datapath uuid in external-ids instead of
  neutron network uuid, delaying processing of UP port state by 15
  seconds.

  This check has been dropped in master, and I'll prepare backports to
  ussuri, victoria and wallaby to also drop that check. Alternatively, I
  have a patch that handles both datapath and neutron uuids in external-
  ids if it's preferred.

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