Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1533412

Summary:	[RFE][DR] - Support registration of floating disks with permissions
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Maor <mlipchuk>
Component:	disaster-recovery	Assignee:	Nobody <nobody>
Status:	CLOSED DEFERRED	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	bugs, eshenitz, lsvaty, tnisan
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	DR
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-29 11:33:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maor 2018-01-11 09:55:16 UTC

Description of problem:
We should support floating disks registration including direct LUN disks. 
Add register of floating disks + permissions.
The permissions should probably be saved in the new metadata file in the OVF_STORE disk

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Maor 2018-05-29 22:44:19 UTC

Permissions should be added to the OVF_STORE disk probably in a new file.
This is an enhancement not related to DR, wihch needs to be designed properly.
Posponing it to 4.3

Comment 3 Sandro Bonazzola 2019-01-28 09:37:01 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 4 Eyal Shenitzky 2021-08-29 09:30:03 UTC

This bug/RFE didn't get enough attention so far and is now flagged as pending close. 
Please review if it is still relevant and provide additional details/justification/patches
if you believe it should get more attention for the next oVirt release.

Comment 5 Michal Skrivanek 2021-09-29 11:33:06 UTC

This bug didn't get any attention in a long time, and it's not planned in foreseeable future. oVirt development team has no plans to work on it.
Please feel free to reopen if you have a plan how to contribute this feature/bug fix.