Bug 2109616
Summary: | Nova fails to parse new libvirt mediated device name format | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Sylvain Bauza <sbauza> |
Component: | openstack-nova | Assignee: | Sylvain Bauza <sbauza> |
Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 17.0 (Wallaby) | CC: | alifshit, chhu, dasmith, eglynn, igallagh, jamsmith, jhakimra, jjongsma, joflynn, jparker, juzhou, kchamart, sbauza, sgordon, smooney, spower, vromanso |
Target Milestone: | ga | Keywords: | Patch, Regression, Triaged, UpgradeBlocker |
Target Release: | 17.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-nova-23.2.3-1.20221209191244.bbf626c.el9ost | Doc Type: | Bug Fix |
Doc Text: |
Before this update, the Compute service was unable to determine the VGPU resource use because the mediated device name format changed in libvirt 7.7. With this update, the Compute service can now parse the new mediated device name format.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-08-16 01:11:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2109450 | ||
Bug Blocks: | 1761861 |
Description
Sylvain Bauza
2022-07-21 15:46:07 UTC
Moving to 17.1, see https://bugzilla.redhat.com/show_bug.cgi?id=2116979 and https://bugzilla.redhat.com/show_bug.cgi?id=2116980. This will need a bug fix doctext because of the following known issue relese note: https://bugzilla.redhat.com/show_bug.cgi?id=2120726 *** Bug 2142768 has been marked as a duplicate of this bug. *** Hi Sylvain, If I'm reading things correctly, it looks like the proposed fix here is still attempting to parse the data from the nodedev name. From libvirt's point of view, the nodedev name is just a unique opaque string that identifies a device. There is no guarantee that it is stable or can be parsed for information (thus, the change in name). Admittedly, that was previously the only way to get the UUID for the mdev, but versions of libvirt after 7.3.0 provide the uuid in the nodedev xml, so you can use that instead of parsing the UUID from the name. (You may need to fall back to name parsing the name for older versions of libvirt though). Here's a similar virt-manager/virt-install issue for reference: https://github.com/virt-manager/virt-manager/pull/319 We are not in a blockers stage for 17.1 yet so no need to propose a blocker for OSP 17.1. I will remove the flag. (In reply to Jonathon Jongsma from comment #5) > Admittedly, that was > previously the only way to get the UUID for the mdev, but versions of > libvirt after 7.3.0 provide the uuid in the nodedev xml, so you can use that > instead of parsing the UUID from the name. (You may need to fall back to > name parsing the name for older versions of libvirt though). > > Here's a similar virt-manager/virt-install issue for reference: > https://github.com/virt-manager/virt-manager/pull/319 Hi Jonathan, thanks a lot for helping us to resolve this issue. Indeed we found that using the mdev name was a fragile API so the change is now using the uuid from the XML : https://code.engineering.redhat.com/gerrit/c/nova/+/436530/1/nova/virt/libvirt/driver.py#7768 Anyway, thanks ;-) Btw, I just backported the master changes to the 17.1 branch : https://code.engineering.redhat.com/gerrit/c/nova/+/436529 https://code.engineering.redhat.com/gerrit/c/nova/+/436530 Putting then the BZ to POST. We had some issues we needed to resolve so now the two patches are https://code.engineering.redhat.com/gerrit/c/nova/+/437157 and https://code.engineering.redhat.com/gerrit/c/nova/+/436530/ Putting to POST again. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577 |