oVirt requires read/write permissions and ownership of ISO domains. It is common to have a readonly NFS ISO share in companies and currently sysadmins have to create a new ISO repository with read/write permissions and copy there the ISO images instead of just mounting the current company's readonly one. Expected results: Make oVirt able to use NFS ISO domain shared as readonly as the real requisite is to read ISO images. Additional info: ovirt-iso-uploader may test for permissions and warn user when it's not able to upload ISO images.
any reason iso domain access by vdsm isn't read only to begin with? (i remember in the past we used to specify pools it was part of, but i hope/think we stopped doing so)?
(In reply to Itamar Heim from comment #1) > any reason iso domain access by vdsm isn't read only to begin with? not that I can think of. > (i remember in the past we used to specify pools it was part of, but i > hope/think we stopped doing so)? I'm not sure I understand what you mean by 'we used to specify pools'. In general we want to get rid of the iso domain entirely (just list content of path and allow attaching read-only to guests).
Similar to bug 1040297.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.