← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1623838] [NEW] Nova requires netaddr >= 0.7.12 which is not enough

 

Public bug reported:

In this commit:
https://github.com/openstack/nova/commit/4647f418afb9ced223c089f9d49cd686eccae9e2

nova starts using the modified_eui64() function which isn't available in
netaddr 0.7.12. It is available in version 0.7.18, which is what the
upper-constraints.txt has. I haven't investigate (yet) when the new
method was introduce in netaddr, though in all reasonableness, I'd
strongly suggest pushing for an upgrade of global-requirements.txt to
0.7.18 (which is what we've been gating on for a long time).

At the packaging level, it doesn't seem to be a big problem, as 0.7.18
is what Xenial has.

The other solution would be to remove the call of modified_eui64() in
Nova, but this looks a more risky option to me, so close from the
release.

** Affects: nova
     Importance: High
         Status: Confirmed


** Tags: newton-backport-potential testing

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1623838

Title:
  Nova requires netaddr >= 0.7.12 which is not enough

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  In this commit:
  https://github.com/openstack/nova/commit/4647f418afb9ced223c089f9d49cd686eccae9e2

  nova starts using the modified_eui64() function which isn't available
  in netaddr 0.7.12. It is available in version 0.7.18, which is what
  the upper-constraints.txt has. I haven't investigate (yet) when the
  new method was introduce in netaddr, though in all reasonableness, I'd
  strongly suggest pushing for an upgrade of global-requirements.txt to
  0.7.18 (which is what we've been gating on for a long time).

  At the packaging level, it doesn't seem to be a big problem, as 0.7.18
  is what Xenial has.

  The other solution would be to remove the call of modified_eui64() in
  Nova, but this looks a more risky option to me, so close from the
  release.

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


Follow ups