Comment 2 for bug 2009156

I don't see any related errors/problems in libvirt logs: it looks like libvirt was able to remove volume attachment without any issues:

2023-02-28 21:59:15.232+0000: 59397: debug : qemuDomainObjBeginJobInternal:9470 : Started job: modify (async=none vm=0x7f9474014b30 name=instance-0000000d)
2023-02-28 21:59:15.233+0000: 59397: debug : qemuDomainObjEnterMonitorInternal:9869 : Entering monitor (mon=0x7f9474054dd0 vm=0x7f9474014b30 name=instance-0000000d)
2023-02-28 21:59:15.233+0000: 59397: debug : qemuMonitorDelDevice:2848 : devalias=virtio-disk1
2023-02-28 21:59:15.233+0000: 59397: debug : qemuMonitorDelDevice:2850 : mon:0x7f9474054dd0 vm:0x7f9474014b30 fd:34
2023-02-28 21:59:15.233+0000: 59397: info : qemuMonitorSend:993 : QEMU_MONITOR_SEND_MSG: mon=0x7f9474054dd0 msg={"execute":"device_del","arguments":{"id":"virtio-disk1"},"id":"libvirt-398"}
 fd=-1
2023-02-28 21:59:15.233+0000: 59392: info : qemuMonitorIOWrite:450 : QEMU_MONITOR_IO_WRITE: mon=0x7f9474054dd0 buf={"execute":"device_del","arguments":{"id":"virtio-disk1"},"id":"libvirt-398"}
 len=79 ret=79 errno=0
2023-02-28 21:59:15.234+0000: 59392: debug : qemuMonitorJSONIOProcessLine:220 : Line [{"return": {}, "id": "libvirt-398"}]
2023-02-28 21:59:15.234+0000: 59392: info : qemuMonitorJSONIOProcessLine:239 : QEMU_MONITOR_RECV_REPLY: mon=0x7f9474054dd0 reply={"return": {}, "id": "libvirt-398"}
2023-02-28 21:59:15.234+0000: 59397: debug : qemuDomainObjExitMonitorInternal:9892 : Exited monitor (mon=0x7f9474054dd0 vm=0x7f9474014b30 name=instance-0000000d)
2023-02-28 21:59:20.234+0000: 59397: debug : qemuDomainObjEnterMonitorInternal:9869 : Entering monitor (mon=0x7f9474054dd0 vm=0x7f9474014b30 name=instance-0000000d)