Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1876605

Summary: VM with scsi hostdev (scsi_generic custom property) fails on start:'node-name too long for qemu'
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Milan Zamazal <mzamazal>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.3.1CC: ahadas, bugs, mzamazal
Target Milestone: ovirt-4.4.3Keywords: Automation, Regression
Target Release: 4.4.3.3Flags: pm-rhel: ovirt-4.4+
pm-rhel: blocker?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.40.31, ovirt-engine-4.4.3.3 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 06:42:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1876467, 1876984, 1877675    
Bug Blocks:    
Attachments:
Description Flags
logs
none
logs second reproduce none

Description Polina 2020-09-07 17:20:42 UTC
Created attachment 1713990 [details]
logs

Description of problem:VM with scsi hostdev (scsi_generic custom property) fails on start:Exit message: internal error: node-name 'libvirt-ua-a03481b3-d43c-4fa1-9566-640e092f384e-backend' too long for qemu


Version-Release number of selected component (if applicable):
ovirt-engine-4.4.3.1-0.7.el8ev.noarch

How reproducible:100%

Steps to Reproduce:
1. create VM on the base of last infra template latest-rhel-guest-image-8.2-infra
2. Attach scsi hostdev and configure scsi_generic custom property.
(chosed device for the LUN that is not used by any SDs)

3. Run VM

Actual results:
VM vails on start .
VM golden_env_mixed_virtio_1_0 is down with error. Exit message: internal error: node-name 'libvirt-ua-a03481b3-d43c-4fa1-9566-640e092f384e-backend' too long for qemu

In the attached engine.log 

2020-09-07 19:59:49,437+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-25) [] EVENT_ID: VM_DOWN_ERROR(119), VM golden_env_mixed_virtio_1_0 is down with error. Exit message: internal error: node-name 'libvirt-ua-a03481b3-d43c-4fa1-9566-640e092f384e-backend' too long for qemu.

Expected results:vm starts


Additional info: the same VM with the same attached scsi hostdev starts if custom property = scsi_hd or scsi_block

Comment 1 Arik 2020-09-08 07:55:51 UTC
It seems that 'libvirt-ua-a03481b3-d43c-4fa1-9566-640e092f384e-backend' value is generated by libvirt and the fact that 'ua-a03481b3-d43c-4fa1-9566-640e092f384e' is a valid user-alias that later leads to an invalid value of node-name sounds like a problem on the libvirt side

While we can change the user-alias assigned to hostdev on our side, I'd like to check it first with libvirt.
Milan, can you please check where that comes from and whether it's possible to fix it at the libvirt-level?

Comment 2 RHEL Program Management 2020-09-08 07:55:57 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Polina 2020-09-08 13:54:47 UTC
Created attachment 1714126 [details]
logs second reproduce

Comment 4 Milan Zamazal 2020-09-08 16:19:52 UTC
I think it should be fixed in libvirt, so I filed a libvirt bug: Bug 1876984.

Comment 5 Arik 2020-09-21 12:50:36 UTC
bz 1877675 is verified, do we need to upgrade the libvirt version we depend on?

Comment 6 Arik 2020-09-21 12:51:03 UTC
(In reply to Arik from comment #5)
> bz 1877675 is verified, do we need to upgrade the libvirt version we depend
> on?

I meant bz 1876467

Comment 7 Milan Zamazal 2020-09-21 13:29:52 UTC
Yes, if/once the given version is available in Advanced Virt. I'll post a patch.

Comment 8 Polina 2020-09-29 13:13:15 UTC
verified on ovirt-engine-4.4.3.3-0.19.el8ev.noarch, qemu-kvm-core-5.1.0-9.module+el8.3.0+8182+ac9ced32.x86_64, vdsm-4.40.31-1.el8ev.x86_64, libvirt-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64

Comment 9 Sandro Bonazzola 2020-11-11 06:42:09 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.