yahoo-eng-team team mailing list archive

[dann frazier <dann.frazier@xxxxxxxxxxxxx>]

Fixes have now landed upstream:

04983c3c6a util: Fixing invalid error checking from virPCIGetNetname()
8fac64db5e util: Fix for NULL dereference
10bca495e0 util: Code simplification
6452e2f5e1 util: fixing wrong assumption that PF has to have netdev assigned


** Also affects: libvirt (Ubuntu Disco)
   Importance: Undecided
       Status: In Progress

** Also affects: libvirt (Ubuntu Cosmic)
   Importance: Undecided
       Status: New

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: libvirt (Ubuntu Disco)
       Status: In Progress => Triaged

** Changed in: nova
       Status: New => Invalid

** Changed in: libvirt (Ubuntu Cosmic)
       Status: New => Triaged

** Changed in: libvirt (Ubuntu Bionic)
       Status: New => Triaged

-- 
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/1771662

Title:
  [bionic] libvirtError: Node device not found: no node device with
  matching name

Status in OpenStack nova-compute charm:
  Invalid
Status in OpenStack Compute (nova):
  Invalid
Status in libvirt package in Ubuntu:
  Triaged
Status in libvirt source package in Bionic:
  Triaged
Status in libvirt source package in Cosmic:
  Triaged
Status in libvirt source package in Disco:
  Triaged

Bug description:
  After deploying openstack on arm64 using bionic and queens, no
  hypervisors show upon. On my compute nodes, I have an error like:

  2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager
  libvirtError: Node device not found: no node device with matching name
  'net_enP2p1s0f1_40_8d_5c_ba_b8_d2'

  In my /var/log/nova/nova-compute.log

  I'm not sure why this is happening - I don't use enP2p1s0f1 for
  anything.

  There are a lot of interesting messages about that interface in syslog:
  http://paste.ubuntu.com/p/8WT8NqCbCf/

  Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/

  The same bundle works fine for xenial-queens, with the source changed
  to the cloud-archive, and using stable charms rather than -next. I hit
  this same issue on bionic queens using either stable or next charms.

  This thread has some related info, I think:
  https://www.spinics.net/linux/fedora/libvir/msg160975.html

  This is with juju 2.4 beta 2.

  Package versions on affected system:
  http://paste.ubuntu.com/p/yfQH3KJzng/

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions