@ahasenack I checked internally and the reason why the issue was
observed was because the test was carried out on the migration source
host when it needs to be performed on the destination (which is what we
did to verify it). Admittedly the test plan did not make that clear so I
am updating it to r
> I've upgraded a host to nova (3:25.2.1-0ubuntu2.8) but still got the same
> error: "libvirt.libvirtError:
> Node device not found: no node device with matching name"
Hi Guilherme,
could you please respond to Edward's questions in comment #13? This is
important, as we don't want to risk releas
This has now finally been verified using [Test Plan]:
Created 6 vms each with 5 sru ports and live migrated them. Checked the
logs and confirm do not see any errors:
root@ubuntu:~# grep -c "libvirt.libvirtError: Node device not found: no node
device" /var/log/nova/nova-compute.log
0
i.e. upon
@guimalufb Thanks for the feedback, I'm not sure how you are still
hitting that error since the code is now catching it:
def _safe_list_caps(dev):
try:
return dev.listCaps()
except libvirt.libvirtError:
return []
Would you mind provid
I've upgraded a host to nova (3:25.2.1-0ubuntu2.8) but still got the
same error: "libvirt.libvirtError: Node device not found: no node device
with matching name"
I've migrated 10 VMs with 5 SRIOV ports each back and forth between two hosts.
I saw the same error regardless the nova version.
He
Hello Mohammed, or anyone else affected,
Accepted nova into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nova/3:25.2.1-0ubuntu2.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Changed in: nova (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972028
Title:
[SRU] _get_pci_passthrough_devices prone to race condition
To manage not
@ahasenack i marked UCA zed as fix released to imply that everything
including that release and above already contains the fix and is
released in Ubuntu. If it is easier for you I can add Noble as Fix
Released too but we don't normally need to do that.
re: the test plan, yes it is just an superflu
What's the status in noble, oracular, and plucky? The main devel task is
still "New".
About the test plan:
"* live migrate the vms between the hosts and check for the Traceback in
/var/log/nova/nova-compute.log"
Is the log the only noticeable defect? If yes, what's the real impact to
users, just
SRU uploaded to Jammy and in the queue now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972028
Title:
[SRU] _get_pci_passthrough_devices prone to race condition
To manage notifications about thi
The attachment "lp1972028.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
11 matches
Mail list logo
