[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
pod deletion should invoke unpublish the PVC which detaches it from
the node which is seen in the engine log:
2021-08-20 17:40:35,664+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
(default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START,
HotUnPlugDiskVDSCommand(HostName = host,
HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
diskId='63a64445-1659-4d5f-8847-e7266e64b09e'}), log id: 506ff4a4
2021-08-20 17:40:35,678+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
(default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Disk
hot-unplug:
2021-08-20 17:40:35,749+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
(default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] FINISH,
HotUnPlugDiskVDSCommand, return: , log id: 506ff4a4
2021-08-20 17:40:35,842+09 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] EVENT_ID:
USER_DETACH_DISK_FROM_VM(2,018), Disk
pvc-9845a0ff-e94c-497c-8c65-fc6a1e26db20 was successfully detached
from VM centos by admin@internal-authz.
I suspect something keeps the volume busy, can run:
$ rbd status /volume-63a64445-1659-4d5f-8847-e7266e64b09e
On Mon, Aug 23, 2021 at 3:56 AM wrote:
>
> Hi all,
>
> I deployed ovirt-csi in the k8s by applying yaml manually. I used the latest
> version of the container image.
> (https://github.com/openshift/ovirt-csi-driver-operator/tree/master/assets)
>
> After successfully creating pvc and pod, I tried to delete it.
> And the pod is deleted, but the pvc is not deleted. This is because deleting
> a pod does not unmap /dev/rbd0 attached to the ovirt vm.
>
> How can I delete the pvc successfully?
>
> oVirt engine version is 4.4.7.6-1.el8.
> Here is the engine log when deleting the pod:
>
> 2021-08-20 17:40:35,385+09 INFO
> [org.ovirt.engine.core.sso.service.AuthenticationService] (default task-149)
> [] User admin@internal-authz with profile [internal] successfully logged in
> with scopes: ovirt-app-api ovirt-ext=token-info:authz-search
> ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate
> ovirt-ext=token:password-access
> 2021-08-20 17:40:35,403+09 INFO
> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149)
> [68ee3182] Running command: CreateUserSessionCommand internal: false.
> 2021-08-20 17:40:35,517+09 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-149) [68ee3182] EVENT_ID: USER_VDC_LOGIN(30), User
> admin@internal-authz connecting from '192.168.7.169' using session
> 'XfDgNkmAGnPiZahK5itLhHQTCNHZ3JwXMMzOiZrYL3C32+1TTys3xcjrAmCIKPu02hgN1sdVpfZXWd0FznaPCQ=='
> logged in.
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will
> return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will
> return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will
> return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will
> return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will
> return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource", will
> return null
> 2021-08-20 17:40:35,663+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.DetachDiskFromVmCommand] (default
> task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Running command:
> DetachDiskFromVmCommand internal: false. Entities affected : ID:
> 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group
> CONFIGURE_VM_STORAGE with role type USER
> 2021-08-20 17:40:35,664+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand] (default
> task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START,
> HotUnPlugDiskVDSCommand(HostName = host,
> HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
> diskId='63a6444
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
When I check the status of the rbd volume, watcher still exists. Wathcer is /dev/rbd0 in the ovirt vm. $ rbd status mypool/volume-3643db6c-38a6-4a21-abb3-ce8cc15e8c86 Watchers: watcher=192.168.7.18:0/1903159992 client.44942 cookie=18446462598732840963 And the attachment information was also left in the volume_attachment of ovirt_cinderlib DB. After manually unmap /dev/rbd0 in the ovirt vm and delete the db row, the pvc was deleted normally. Shouldn't those tasks be done when deleting the pod? ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PSL4JPAMEQ5NHICWI34YI3HO62J2T3MB/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
It should do this and it's not semantically different from what happens with non-MBS disks. The log I pasted is what unmaps the volume, I am not sure why it returned successfully if the volume wasn't unmapped, if possible please attach vdsm and supervdsm logs from the relevant, perhaps there's some clue there. But we essentially use cinderlib's `disconnect`, so perhaps it hasn't errored On Mon, Aug 23, 2021 at 10:05 AM wrote: > > When I check the status of the rbd volume, watcher still exists. Wathcer is > /dev/rbd0 in the ovirt vm. > $ rbd status mypool/volume-3643db6c-38a6-4a21-abb3-ce8cc15e8c86 > Watchers: > watcher=192.168.7.18:0/1903159992 client.44942 > cookie=18446462598732840963 > > And the attachment information was also left in the volume_attachment of > ovirt_cinderlib DB. > > After manually unmap /dev/rbd0 in the ovirt vm and delete the db row, the pvc > was deleted normally. > Shouldn't those tasks be done when deleting the pod? > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/PSL4JPAMEQ5NHICWI34YI3HO62J2T3MB/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/646F25UD5ARFWPUOYMQABSIMGD63Y7SJ/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
There were no error logs in vdsm and supervdsm.
And I found that the
[org.ovirt.engine.core.bll.storage.disk.managedblock.DisconnectManagedBlockStorageDeviceCommand]
and
[org.ovirt.engine.core.vdsbroker.vdsbroker.DetachManagedBlockStorageVolumeVDSCommand]
functions are being called when the disk is detached from ovirt vm.
However, in the log I gave first, there is no part where the correspoding
functions are called, isn't it a bug?
Here is the engine log where detaching the disk:
2021-08-23 10:29:43,972+09 INFO
[org.ovirt.engine.core.bll.storage.disk.HotUnPlugDiskFromVmCommand] (default
task-176) [2538ba78-6916-431c-b3bc-b98b26515842] Lock Acquired to object
'EngineLock:{exclusiveLocks='[f17702e4-ba97-4f95-a6d4-b89de003bd26=DISK]',
sharedLocks='[59a7461c-72fe-4e01-86a7-c70243f31596=VM]'}'
2021-08-23 10:29:44,054+09 INFO
[org.ovirt.engine.core.bll.storage.disk.HotUnPlugDiskFromVmCommand]
(EE-ManagedThreadFactory-engine-Thread-149928)
[2538ba78-6916-431c-b3bc-b98b26515842] Running command:
HotUnPlugDiskFromVmCommand internal: false. Entities affected : ID:
59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group CONFIGURE_VM_STORAGE
with role type USER
2021-08-23 10:29:44,076+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-149928)
[2538ba78-6916-431c-b3bc-b98b26515842] START, HotUnPlugDiskVDSCommand(HostName
= host,
HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
diskId='f17702e4-ba97-4f95-a6d4-b89de003bd26'}), log id: 1c39f09a
2021-08-23 10:29:44,078+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-149928)
[2538ba78-6916-431c-b3bc-b98b26515842] Disk hot-unplug:
2021-08-23 10:29:44,218+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-149928)
[2538ba78-6916-431c-b3bc-b98b26515842] FINISH, HotUnPlugDiskVDSCommand, return:
, log id: 1c39f09a
2021-08-23 10:29:44,471+09 INFO
[org.ovirt.engine.core.bll.storage.disk.managedblock.DisconnectManagedBlockStorageDeviceCommand]
(EE-ManagedThreadFactory-engine-Thread-149928) [2a452b04] Running command:
DisconnectManagedBlockStorageDeviceCommand internal: true.
2021-08-23 10:29:44,514+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DetachManagedBlockStorageVolumeVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-149928) [2a452b04] START,
DetachManagedBlockStorageVolumeVDSCommand(HostName = host,
AttachManagedBlockStorageVolumeVDSCommandParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
vds='Host[host,29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094]'}), log id: 2d6874a5
2021-08-23 10:29:46,683+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DetachManagedBlockStorageVolumeVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-149928) [2a452b04] FINISH,
DetachManagedBlockStorageVolumeVDSCommand, return: StatusOnlyReturn
[status=Status [code=0, message=Done]], log id: 2d6874a5
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LL4WSFNCV6EW6DVDQ3DENEDUVA5MAL6L/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
yes, it should indeed defer to
DetachManagedBlockStorageVolumeVDSCommand which is what does the
unmapping, do you have an earlier log that shows the XML (for example,
when it was attached)?
On Mon, Aug 23, 2021 at 10:59 AM wrote:
>
> There were no error logs in vdsm and supervdsm.
>
> And I found that the
> [org.ovirt.engine.core.bll.storage.disk.managedblock.DisconnectManagedBlockStorageDeviceCommand]
> and
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DetachManagedBlockStorageVolumeVDSCommand]
> functions are being called when the disk is detached from ovirt vm.
>
> However, in the log I gave first, there is no part where the correspoding
> functions are called, isn't it a bug?
>
> Here is the engine log where detaching the disk:
>
> 2021-08-23 10:29:43,972+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.HotUnPlugDiskFromVmCommand] (default
> task-176) [2538ba78-6916-431c-b3bc-b98b26515842] Lock Acquired to object
> 'EngineLock:{exclusiveLocks='[f17702e4-ba97-4f95-a6d4-b89de003bd26=DISK]',
> sharedLocks='[59a7461c-72fe-4e01-86a7-c70243f31596=VM]'}'
> 2021-08-23 10:29:44,054+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.HotUnPlugDiskFromVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928)
> [2538ba78-6916-431c-b3bc-b98b26515842] Running command:
> HotUnPlugDiskFromVmCommand internal: false. Entities affected : ID:
> 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group
> CONFIGURE_VM_STORAGE with role type USER
> 2021-08-23 10:29:44,076+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928)
> [2538ba78-6916-431c-b3bc-b98b26515842] START,
> HotUnPlugDiskVDSCommand(HostName = host,
> HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
> diskId='f17702e4-ba97-4f95-a6d4-b89de003bd26'}), log id: 1c39f09a
> 2021-08-23 10:29:44,078+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928)
> [2538ba78-6916-431c-b3bc-b98b26515842] Disk hot-unplug: encoding="UTF-8"?>
>
>
>
>
>
>
>
> 2021-08-23 10:29:44,218+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928)
> [2538ba78-6916-431c-b3bc-b98b26515842] FINISH, HotUnPlugDiskVDSCommand,
> return: , log id: 1c39f09a
> 2021-08-23 10:29:44,471+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.managedblock.DisconnectManagedBlockStorageDeviceCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928) [2a452b04] Running command:
> DisconnectManagedBlockStorageDeviceCommand internal: true.
> 2021-08-23 10:29:44,514+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DetachManagedBlockStorageVolumeVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928) [2a452b04] START,
> DetachManagedBlockStorageVolumeVDSCommand(HostName = host,
> AttachManagedBlockStorageVolumeVDSCommandParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vds='Host[host,29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094]'}), log id: 2d6874a5
> 2021-08-23 10:29:46,683+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.DetachManagedBlockStorageVolumeVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-149928) [2a452b04] FINISH,
> DetachManagedBlockStorageVolumeVDSCommand, return: StatusOnlyReturn
> [status=Status [code=0, message=Done]], log id: 2d6874a5
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LL4WSFNCV6EW6DVDQ3DENEDUVA5MAL6L/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BWJW6DBXXZC6I2XMV4XPGS4MAX54U2DA/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
I attached a mbs disk to the running vm through the dashboard.
Here is the engine log:
2021-08-23 19:00:54,912+09 INFO
[org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (default
task-209) [28eaa439-0bce-456d-8931-f1edc74ca71b] Lock Acquired to object
'EngineLock:{exclusiveLocks='[f17702e4-ba97-4f95-a6d4-b89de003bd26=DISK]',
sharedLocks='[59a7461c-72fe-4e01-86a7-c70243f31596=VM]'}'
2021-08-23 19:00:54,917+09 INFO
[org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
(EE-ManagedThreadFactory-engine-Thread-154035)
[28eaa439-0bce-456d-8931-f1edc74ca71b] Running command: HotPlugDiskToVmCommand
internal: false. Entities affected : ID: 59a7461c-72fe-4e01-86a7-c70243f31596
Type: VMAction group CONFIGURE_VM_STORAGE with role type USER
2021-08-23 19:00:54,922+09 INFO
[org.ovirt.engine.core.bll.storage.disk.managedblock.ConnectManagedBlockStorageDeviceCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] Running command:
ConnectManagedBlockStorageDeviceCommand internal: true.
2021-08-23 19:00:59,441+09 INFO
[org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor]
(EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] cinderlib output:
{"driver_volume_type": "rbd", "data": {"name":
"mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26", "hosts": ["172.22.5.6"],
"ports": ["6789"], "cluster_name": "ceph", "auth_enabled": true,
"auth_username": "admin", "secret_type": "ceph", "secret_uuid": null,
"volume_id": "f17702e4-ba97-4f95-a6d4-b89de003bd26", "discard": true,
"keyring": "[client.admin]\n\tkey =
AQCjBFhgjRWFOBAAMxEaJ3yffC50GDFWnR43DQ==\n", "access_mode": "rw"}}
2021-08-23 19:00:59,442+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.AttachManagedBlockStorageVolumeVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] START,
AttachManagedBlockStorageVolumeVDSCommand(HostName = host,
AttachManagedBlockStorageVolumeVDSCommandParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
vds='Host[host,29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094]'}), log id: 5657b4a1
2021-08-23 19:01:02,715+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.AttachManagedBlockStorageVolumeVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] FINISH,
AttachManagedBlockStorageVolumeVDSCommand, return: {attachment={path=/dev/rbd1,
conf=/tmp/brickrbd_it_6m0e4, type=block},
path=/dev/rbd/mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26,
vol_id=f17702e4-ba97-4f95-a6d4-b89de003bd26}, log id: 5657b4a1
2021-08-23 19:01:02,817+09 INFO
[org.ovirt.engine.core.bll.storage.disk.managedblock.SaveManagedBlockStorageDiskDeviceCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] Running command:
SaveManagedBlockStorageDiskDeviceCommand internal: true.
2021-08-23 19:01:09,072+09 INFO
[org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] cinderlib output:
2021-08-23 19:01:09,077+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] START,
HotPlugDiskVDSCommand(HostName = host,
HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
diskId='f17702e4-ba97-4f95-a6d4-b89de003bd26'}), log id: 5acbdc16
2021-08-23 19:01:09,111+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] Disk hot-plug:
f17702e4-ba97-4f95-a6d4-b89de003bd26
http://ovirt.org/vm/1.0";>
/dev/rbd/mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26
2021-08-23 19:01:09,221+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] FINISH,
HotPlugDiskVDSCommand, return: , log id: 5acbdc16
2021-08-23 19:01:09,358+09 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] EVENT_ID:
USER_HOTPLUG_DISK(2,000), VM centos disk mbs was plugged by
admin@internal-authz.
2021-08-23 19:01:09,358+09 INFO
[org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
(EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] Lock freed to object
'EngineLock:{exclusiveLocks='[f17702e4-ba97-4f95-a6d4-b89de003bd26=DISK]',
sharedLocks='[59a7461c-72fe-4e01-86a7-c70243f31596=VM]'}'
2021-08-23 19:01:10,916+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) []
START, DumpXmlsVDSCommand(HostName = host,
Params:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
vmIds='[59a7461c-72fe-4e01-86a7-c70243f31596]'}), log id: 22d45ea6
2021-08-23 19:01:10,919+09 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand]
(EE-Mana
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
this is a correct run, right? the original flow works with this one?
On Mon, Aug 23, 2021 at 1:05 PM wrote:
>
> I attached a mbs disk to the running vm through the dashboard.
>
> Here is the engine log:
>
>
> 2021-08-23 19:00:54,912+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (default
> task-209) [28eaa439-0bce-456d-8931-f1edc74ca71b] Lock Acquired to object
> 'EngineLock:{exclusiveLocks='[f17702e4-ba97-4f95-a6d4-b89de003bd26=DISK]',
> sharedLocks='[59a7461c-72fe-4e01-86a7-c70243f31596=VM]'}'
> 2021-08-23 19:00:54,917+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035)
> [28eaa439-0bce-456d-8931-f1edc74ca71b] Running command:
> HotPlugDiskToVmCommand internal: false. Entities affected : ID:
> 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group
> CONFIGURE_VM_STORAGE with role type USER
> 2021-08-23 19:00:54,922+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.managedblock.ConnectManagedBlockStorageDeviceCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] Running command:
> ConnectManagedBlockStorageDeviceCommand internal: true.
> 2021-08-23 19:00:59,441+09 INFO
> [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor]
> (EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] cinderlib output:
> {"driver_volume_type": "rbd", "data": {"name":
> "mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26", "hosts":
> ["172.22.5.6"], "ports": ["6789"], "cluster_name": "ceph", "auth_enabled":
> true, "auth_username": "admin", "secret_type": "ceph", "secret_uuid": null,
> "volume_id": "f17702e4-ba97-4f95-a6d4-b89de003bd26", "discard": true,
> "keyring": "[client.admin]\n\tkey =
> AQCjBFhgjRWFOBAAMxEaJ3yffC50GDFWnR43DQ==\n", "access_mode": "rw"}}
> 2021-08-23 19:00:59,442+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.AttachManagedBlockStorageVolumeVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] START,
> AttachManagedBlockStorageVolumeVDSCommand(HostName = host,
> AttachManagedBlockStorageVolumeVDSCommandParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vds='Host[host,29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094]'}), log id: 5657b4a1
> 2021-08-23 19:01:02,715+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.AttachManagedBlockStorageVolumeVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [373c4bed] FINISH,
> AttachManagedBlockStorageVolumeVDSCommand, return:
> {attachment={path=/dev/rbd1, conf=/tmp/brickrbd_it_6m0e4, type=block},
> path=/dev/rbd/mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26,
> vol_id=f17702e4-ba97-4f95-a6d4-b89de003bd26}, log id: 5657b4a1
> 2021-08-23 19:01:02,817+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.managedblock.SaveManagedBlockStorageDiskDeviceCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] Running command:
> SaveManagedBlockStorageDiskDeviceCommand internal: true.
> 2021-08-23 19:01:09,072+09 INFO
> [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] cinderlib output:
> 2021-08-23 19:01:09,077+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] START,
> HotPlugDiskVDSCommand(HostName = host,
> HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
> diskId='f17702e4-ba97-4f95-a6d4-b89de003bd26'}), log id: 5acbdc16
> 2021-08-23 19:01:09,111+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] Disk hot-plug:
>
>
>
>
>dev="/dev/rbd/mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26">
>
>
>
>
>
> f17702e4-ba97-4f95-a6d4-b89de003bd26
>
>
> http://ovirt.org/vm/1.0";>
>
>
>
> /dev/rbd/mypool/volume-f17702e4-ba97-4f95-a6d4-b89de003bd26
>
>
>
>
>
> 2021-08-23 19:01:09,221+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] FINISH,
> HotPlugDiskVDSCommand, return: , log id: 5acbdc16
> 2021-08-23 19:01:09,358+09 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] EVENT_ID:
> USER_HOTPLUG_DISK(2,000), VM centos disk mbs was plugged by
> admin@internal-authz.
> 2021-08-23 19:01:09,358+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> (EE-ManagedThreadFactory-engine-Thread-154035) [50d635e3] Lock freed to
> object
> 'EngineLock:{exclusiveLocks='[f17702e4-ba97-4f95-a6d4-b89de003bd26=DISK]',
> sharedLocks='[59a7461c-72fe-4e01-86a7-c70243f31596=VM]'}'
> 2021-08-23 19:01:10,916+09 INFO
> [org.ovirt.engine.core.vdsbroker.vd
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
Yes, that's right. I can attach and detach mbs disk to ovirt vm normally through dashboard. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/C6Z2TPVX7Z2OBGUAGA4UYCMSWK3RBZK4/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
And the full flow, with CSI? I'm trying to determine whether the CSI driver does something wrong, or something went wrong during that specific run On Mon, Aug 23, 2021 at 2:34 PM wrote: > > Yes, that's right. > I can attach and detach mbs disk to ovirt vm normally through dashboard. > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/C6Z2TPVX7Z2OBGUAGA4UYCMSWK3RBZK4/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/A2AI23GC6TJEQ5WJYPB3W4OYLB4V7GF5/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
Hey there,
The CSI driver in this repository is built with OpenShift in mind, and does
not have an upstream that is intended to work with vanilla Kubernetes. Even
if you get it to work now, it may break in the future.
We have had some discussions around reviving the upstream for the CSI
driver, which is located here: https://github.com/oVirt/csi-driver
We are also doing a fair bit of work which will make the process easier
here: https://github.com/oVirt/go-ovirt-client
However, at this time we haven't made any progress that would be useful to
you. With that in mind, I would recommend reporting possible bugs either on
GitHub or on Bugzilla, that way they will reach us quicker, even if we
officially don't support vanilla Kubernetes.
Cheers,
Janos
On Mon, Aug 23, 2021 at 12:57 AM wrote:
> Hi all,
>
> I deployed ovirt-csi in the k8s by applying yaml manually. I used the
> latest version of the container image.
> (https://github.com/openshift/ovirt-csi-driver-operator/tree/master/assets
> )
>
> After successfully creating pvc and pod, I tried to delete it.
> And the pod is deleted, but the pvc is not deleted. This is because
> deleting a pod does not unmap /dev/rbd0 attached to the ovirt vm.
>
> How can I delete the pvc successfully?
>
> oVirt engine version is 4.4.7.6-1.el8.
> Here is the engine log when deleting the pod:
>
> 2021-08-20 17:40:35,385+09 INFO
> [org.ovirt.engine.core.sso.service.AuthenticationService] (default
> task-149) [] User admin@internal-authz with profile [internal]
> successfully logged in with scopes: ovirt-app-api
> ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search
> ovirt-ext=token-info:validate ovirt-ext=token:password-access
> 2021-08-20 17:40:35,403+09 INFO
> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149)
> [68ee3182] Running command: CreateUserSessionCommand internal: false.
> 2021-08-20 17:40:35,517+09 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-149) [68ee3182] EVENT_ID: USER_VDC_LOGIN(30), User
> admin@internal-authz connecting from '192.168.7.169' using session
> 'XfDgNkmAGnPiZahK5itLhHQTCNHZ3JwXMMzOiZrYL3C32+1TTys3xcjrAmCIKPu02hgN1sdVpfZXWd0FznaPCQ=='
> logged in.
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,663+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.DetachDiskFromVmCommand] (default
> task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Running command:
> DetachDiskFromVmCommand internal: false. Entities affected : ID:
> 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group
> CONFIGURE_VM_STORAGE with role type USER
> 2021-08-20 17:40:35,664+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START,
> HotUnPlugDiskVDSCommand(HostName = host,
> HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
> diskId='63a64445-1659-4d5f-8847-e7266e64b09e'}), log id: 506ff4a4
> 2021-08-20 17:40:35,678+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Disk hot-unplug:
>
>
>
>
>
>
>
>
> 2021-08-20 17:40:35,749+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] FINISH,
> HotUnPlugDiskVDSCommand, return: , log id: 506ff4a4
> 2021-08-20 17:40:35,842+09 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-149) [198e2dc9-b908
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
Hey there,
The CSI driver in this repository is built with OpenShift in mind, and does
not have an upstream that is intended to work with vanilla Kubernetes. Even
if you get it to work now, it may break in the future.
We have had some discussions around reviving the upstream for the CSI
driver, which is located here: https://github.com/oVirt/csi-driver
We are also doing a fair bit of work which will make the process easier
here: https://github.com/oVirt/go-ovirt-client
However, at this time we haven't made any progress that would be useful to
you. With that in mind, I would recommend reporting possible bugs either on
GitHub or on Bugzilla, that way they will reach us quicker, even if we
officially don't support vanilla Kubernetes.
Cheers,
Janos
On Mon, Aug 23, 2021 at 12:57 AM wrote:
> Hi all,
>
> I deployed ovirt-csi in the k8s by applying yaml manually. I used the
> latest version of the container image.
> (https://github.com/openshift/ovirt-csi-driver-operator/tree/master/assets
> )
>
> After successfully creating pvc and pod, I tried to delete it.
> And the pod is deleted, but the pvc is not deleted. This is because
> deleting a pod does not unmap /dev/rbd0 attached to the ovirt vm.
>
> How can I delete the pvc successfully?
>
> oVirt engine version is 4.4.7.6-1.el8.
> Here is the engine log when deleting the pod:
>
> 2021-08-20 17:40:35,385+09 INFO
> [org.ovirt.engine.core.sso.service.AuthenticationService] (default
> task-149) [] User admin@internal-authz with profile [internal]
> successfully logged in with scopes: ovirt-app-api
> ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search
> ovirt-ext=token-info:validate ovirt-ext=token:password-access
> 2021-08-20 17:40:35,403+09 INFO
> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-149)
> [68ee3182] Running command: CreateUserSessionCommand internal: false.
> 2021-08-20 17:40:35,517+09 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-149) [68ee3182] EVENT_ID: USER_VDC_LOGIN(30), User
> admin@internal-authz connecting from '192.168.7.169' using session
> 'XfDgNkmAGnPiZahK5itLhHQTCNHZ3JwXMMzOiZrYL3C32+1TTys3xcjrAmCIKPu02hgN1sdVpfZXWd0FznaPCQ=='
> logged in.
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,520+09 WARN
> [org.ovirt.engine.api.restapi.util.LinkHelper] (default task-149) [] Can't
> find relative path for class
> "org.ovirt.engine.api.resource.StorageDomainVmDiskAttachmentsResource",
> will return null
> 2021-08-20 17:40:35,663+09 INFO
> [org.ovirt.engine.core.bll.storage.disk.DetachDiskFromVmCommand] (default
> task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Running command:
> DetachDiskFromVmCommand internal: false. Entities affected : ID:
> 59a7461c-72fe-4e01-86a7-c70243f31596 Type: VMAction group
> CONFIGURE_VM_STORAGE with role type USER
> 2021-08-20 17:40:35,664+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] START,
> HotUnPlugDiskVDSCommand(HostName = host,
> HotPlugDiskVDSParameters:{hostId='29dc5d53-7ec5-4a38-aaf1-c6eaf32b0094',
> vmId='59a7461c-72fe-4e01-86a7-c70243f31596',
> diskId='63a64445-1659-4d5f-8847-e7266e64b09e'}), log id: 506ff4a4
> 2021-08-20 17:40:35,678+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] Disk hot-unplug:
>
>
>
>
>
>
>
>
> 2021-08-20 17:40:35,749+09 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnPlugDiskVDSCommand]
> (default task-149) [198e2dc9-b908-474e-a395-0fe682c29af0] FINISH,
> HotUnPlugDiskVDSCommand, return: , log id: 506ff4a4
> 2021-08-20 17:40:35,842+09 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-149) [198e2dc9-b908-
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
With csi, a pvc is created and a pod is also created by attaching the pvc. And if I delete the pod, /dev/rbd0 connected to the ovirt vm is not released and connection information remains in the DB. So I cannot delete the pvc and cannot attach the pvc again. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q6KDWOOMNYDM4LLQJNT6BGVK5VHIWDD2/
[ovirt-users] Re: Cannot delete pvc attached to pod using ovirt-csi in kubernetes
And also you can't migrate your pvc between pools. I was create ticket for that [1] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1997241 k > On 24 Aug 2021, at 04:13, ssarang...@gmail.com wrote: > > With csi, a pvc is created and a pod is also created by attaching the pvc. > > And if I delete the pod, /dev/rbd0 connected to the ovirt vm is not released > and connection information remains in the DB. > So I cannot delete the pvc and cannot attach the pvc again. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AY5SBCN5C2H6I67DVGZ4JO6TO46QR3IO/
