It calls:
virProcessRunInFork for virSecurityDACMoveImageMetadataHelper
And I was able to confirm that this is the "remaining" source of a
negative return code that was formerly hidden behind the missing
function.
Thread 18 "libvirtd" hit Breakpoint 4, virSecurityDACMoveImageMetadata
(mgr=0x7f8c1805cf10, pid=-1, src=0x7f8c4803fbf0, dst=0x0) at
../../../src/security/security_dac.c:1122
1122 {
(gdb) fin
Run till exit from #0 virSecurityDACMoveImageMetadata (mgr=0x7f8c1805cf10,
pid=-1, src=0x7f8c4803fbf0, dst=0x0) at
../../../src/security/security_dac.c:1122
[Detaching after fork from child process 14055]
0x00007f8c638a8ecf in virSecurityManagerMoveImageMetadata (mgr=0x7f8c1805cf10,
pid=pid@entry=-1, src=src@entry=0x7f8c4803fbf0, dst=dst@entry=0x0)
at ../../../src/security/security_manager.c:471
471 ret = mgr->drv->domainMoveImageMetadata(mgr, pid, src, dst);
Value returned is $11 = -1
Checking for behavior in virProcessRunInFork and
virSecurityDACMoveImageMetadataHelper next ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879325
Title:
Unable to remove disk metadata on vm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
