I see the rule is created in the logs:
MainProcess|jsonrpc/5::DEBUG::2021-09-22
10:39:37,504::supervdsm_server::95::SuperVdsm.ServerCallback::(wrapper)
call add_managed_udev_rule with
('ed1a0e9f-4d30-4896-b965-534861cc0c02',
'/dev/mapper/360014054b727813d1bc4d4cefdade7db') {}
MainProcess|jsonrpc/5::DEBUG::2021-09-22
10:39:37,505::udev::124::SuperVdsm.ServerCallback::(add_managed_udev_rule)
Creating rule
/etc/udev/rules.d/99-vdsm-managed_ed1a0e9f-4d30-4896-b965-534861cc0c02.rules:
'SYMLINK=="mapper/360014054b727813d1bc4d4cefdade7db",
RUN+="/usr/bin/chown vdsm:qemu $env{DEVNAME}"\n'
While we no longer test backends other than ceph, this used to work
back when we started and it worked for NetApp. Perhaps this rule is
incorrect, can you check this manually?
regarding 2, can you please submit a bug?
On Wed, Sep 22, 2021 at 1:03 PM Shantur Rathore
<shantur.rathore(a)gmail.com> wrote:
Hi all,
I am trying to set up Managed block storage and have the following issues.
My setup:
Latest oVirt Node NG : 4.4.8
Latest oVirt Engine : 4.4.8
1. Unable to copy to iSCSI based block storage
I created a MBS with Synology UC3200 as a backend ( supported by
Cinderlib ). It was created fine but when I try to copy disks to it,
it fails.
Upon looking at the logs from SPM, I found "qemu-img" failed with an
error that it cannot open "/dev/mapper/xxxxxxxxxx" : Permission Error.
Had a look through the code and digging out more, I saw that
a. Sometimes /dev/mapper/xxxx symlink isn't created ( log attached )
b. The ownership to /dev/mapper/xxxxxx and /dev/dm-xx for the new
device always stays at root:root
I added a udev rule
ACTION=="add|change", ENV{DM_UUID}=="mpath-*",
GROUP="qemu",
OWNER="vdsm", MODE="0660"
and the disk copied correctly when /dev/mapper/xxxxx got created.
2. Copy progress finishes in UI very early than the actual qemu-img process.
The UI shows the Copy process is completed successfully but it's
actually still copying the image.
This happens both for ceph and iscsi based mbs.
Is there any known workaround to get iSCSI MBS working?
Kind regards,
Shantur
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/G6TMTW23SUA...