Comment 26 for bug 1771662
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name | #26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
c15647f
demo site
(Get the code!)
cd /sys/bus/
xenial:
http://
On Tue, May 22, 2018 at 5:27 PM, Jason Hobbs <email address hidden> wrote:
> Do you really want a tar? How about ls -alR? xenial:
>
> http://
>
> On Tue, May 22, 2018 at 5:14 PM, Jason Hobbs <email address hidden> wrote:
>> ok; looks like that 4.15.0-22-generic just released and wasn't what I
>> used in the first reproduction... I doubt that's it.
>>
>> On Tue, May 22, 2018 at 4:58 PM, Ryan Harper <email address hidden> wrote:
>>> Comparing the kernel logs, on Xenial, the second nic comes up:
>>>
>>> May 22 15:00:27 aurorus kernel: [ 24.840500] IPv6:
>>> ADDRCONF(
>>> May 22 15:00:27 aurorus kernel: [ 25.472391] thunder-nicvf
>>> 0002:01:00.2 enP2p1s0f2: Link is Up 10000 Mbps Full duplex
>>>
>>> But on bionic, we only ever have f3 up. Note this isn't a network
>>> configuration, but rather the state of the Nic and the switch.
>>> It doesn't appear to matter, 0f3 is what get's bridged by juju anyhow.
>>> But it does suggest that something is different.
>>>
>>> There is a slight kernel version variance as well:
>>>
>>> Xenial:
>>> May 22 15:00:27 aurorus kernel: [ 0.000000] Linux version
>>> 4.15.0-22-generic (buildd@
>>> (Ubuntu/Lin
>>>
>>> Bionic:
>>> May 17 18:03:47 aurorus kernel: [ 0.000000] Linux version
>>> 4.15.0-20-generic (buildd@
>>> (Ubuntu/Linaro 7.3.
>>>
>>> Looks like Xenial does not use unified cgroup namespaces, not sure
>>> what affect this may have on what's running in those lxd juju
>>> containers.
>>>
>>> % grep DENIED *.log
>>> bionic.log:May 17 18:19:33 aurorus kernel: [ 983.592228] audit:
>>> type=1400 audit(152658117
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> fstype="cgroup2" srcname="cgroup" flags="rw, nosuid, nodev, noexec"
>>> bionic.log:May 17 18:19:33 aurorus kernel: [ 983.592476] audit:
>>> type=1400 audit(152658117
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> fstype="cgroup2" srcname="cgroup" flags="rw, nosuid, nodev, noexec"
>>> bionic.log:May 17 18:19:41 aurorus kernel: [ 991.818402] audit:
>>> type=1400 audit(152658118
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> comm="(networkd)" flags="ro, nosuid, nodev, remount, bind"
>>> bionic.log:May 17 18:19:46 aurorus kernel: [ 997.271203] audit:
>>> type=1400 audit(152658118
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> fstype="cgroup2" srcname="cgroup" flags="rw, nosuid, nodev, noexec"
>>> bionic.log:May 17 18:19:46 aurorus kernel: [ 997.271425] audit:
>>> type=1400 audit(152658118
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> fstype="cgroup2" srcname="cgroup" flags="rw, nosuid, nodev, noexec"
>>> bionic.log:May 17 18:19:55 aurorus kernel: [ 1006.285863] audit:
>>> type=1400 audit(152658119
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> remount, bind"
>>> bionic.log:May 17 18:20:12 aurorus kernel: [ 1022.760512] audit:
>>> type=1400 audit(152658121
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> fstype="cgroup2" srcname="cgroup" flags="rw, nosuid, nodev, noexec"
>>> bionic.log:May 17 18:20:12 aurorus kernel: [ 1022.760713] audit:
>>> type=1400 audit(152658121
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> fstype="cgroup2" srcname="cgroup" flags="rw, nosuid, nodev, noexec"
>>> bionic.log:May 17 18:20:20 aurorus kernel: [ 1031.256448] audit:
>>> type=1400 audit(152658122
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> name="/
>>> remount, bind"
>>> bionic.log:May 17 18:30:03 aurorus kernel: [ 1613.787782] audit:
>>> type=1400 audit(152658180
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> pid=91926 comm="(arter.sh)" flags="ro, remount, bind"
>>> bionic.log:May 17 18:30:03 aurorus kernel: [ 1613.832621] audit:
>>> type=1400 audit(152658180
>>> operation="mount" info="failed flags match" error=-13
>>> profile=
>>> pid=91949 comm="(y-helper)" flags="ro, remount, bind"
>>>
>>>
>>> xenial.log:May 22 15:15:10 aurorus kernel: [ 918.311740] audit:
>>> type=1400 audit(152700211
>>> operation=
>>> namespace=
>>> profile=
>>> name="/
>>> requested_mask="m" denied_mask="m" fsuid=100000 ouid=100000
>>> xenial.log:May 22 15:15:11 aurorus kernel: [ 919.605481] audit:
>>> type=1400 audit(152700211
>>> operation=
>>> namespace=
>>> profile=
>>> name="/
>>> requested_mask="m" denied_mask="m" fsuid=100000 ouid=100000
>>>
>>> Looking at the nova.pci.utils code, the different errors seem to be
>>> related to sysfs entries:
>>>
>>> https:/
>>>
>>> If the sysfs path exists, then we go "further down" the hole and get
>>> an error like in bionic, but if the sysfs path does not exist, then we
>>> get
>>> the exception we see in Xenial.
>>>
>>> Can we get a tar of /sys for both to see if this confirms the
>>> suspicion that we're taking different paths due to differing kernels?
>>>
>>>
>>> On Tue, May 22, 2018 at 3:27 PM, Jason Hobbs <email address hidden> wrote:
>>>> marked new on nova-compute-charm due to rharper's comment #18, and new
>>>> on libvirt because I've posted all the requested logs now.
>>>>
>>>> --
>>>> You received this bug notification because you are subscribed to the bug
>>>> report.
>>>> https:/
>>>>
>>>> Title:
>>>> libvirtError: Node device not found: no node device with matching name
>>>>
>>>> To manage notifications about this bug go to:
>>>> https:/
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https:/
>>>
>>> Title:
>>> libvirtError: Node device not found: no node device with matching name
>>>
>>> Status in OpenStack nova-compute charm:
>>> New
>>> Status in libvirt package in Ubuntu:
>>> New
>>>
>>> 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.
>>> libvirtError: Node device not found: no node device with matching name
>>> 'net_enP2p1s0f1
>>>
>>> In my /var/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://
>>>
>>> Here is my bundle: http://
>>>
>>> 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:/
>>>
>>> This is with juju 2.4 beta 2.
>>>
>>> Package versions on affected system:
>>> http://
>>>
>>> To manage notifications about this bug go to:
>>> https:/