Bug 1834353 - Libdevmapper fails with "Device %s not found" when calling dm_task_set_name()
Summary: Libdevmapper fails with "Device %s not found" when calling dm_task_set_name()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: libvirt
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.3
Assignee: Michal Privoznik
QA Contact: Han Han
URL:
Whiteboard:
Depends On: 1823976
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-11 14:52 UTC by Michal Privoznik
Modified: 2020-07-28 07:13 UTC (History)
14 users (show)

Fixed In Version: libvirt-6.0.0-20.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1823976
Environment:
Last Closed: 2020-07-28 07:12:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3172 0 None None None 2020-07-28 07:13:08 UTC

Comment 1 Michal Privoznik 2020-05-11 14:59:54 UTC 
To POST:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2020-May/msg00320.html
Comment 4 Han Han 2020-06-09 03:36:55 UTC 
Verified on qemu-kvm-4.2.0-23.module+el8.2.1+6917+927fbb44.x86_64
libvirt-6.0.0-23.module+el8.2.1+6955+1e1fca42.x86_64

Steps:
➜  ~ dmsetup create --table '0 10240 zero' loop0
➜  ~ virsh destroy pc
Domain pc destroyed

➜  ~ qemu-img create /tmp/raw 100M
Formatting '/tmp/raw', fmt=raw size=104857600
➜  ~ losetup /dev/loop0 /tmp/raw
➜  ~ virsh attach-disk pc /tmp/raw sdb --config
Disk attached successfully

➜  ~ virsh start pc
Domain pc started

➜  ~ virsh destroy pc
Domain pc destroyed

VM started with loop device loop0 while dm loops exists.
Comment 6 errata-xmlrpc 2020-07-28 07:12:15 UTC 
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, 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/RHBA-2020:3172
Note You need to log in before you can comment on or make changes to this bug.