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

Bug 1222571

Summary: [RFE] Let the user change the name of an imported file Storage Domain
Product: [oVirt] ovirt-engine Reporter: Fred Rolland <frolland>
Component: Frontend.WebAdminAssignee: Maor <mlipchuk>
Status: CLOSED DUPLICATE QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, amureini, bugs, ecohen, frolland, gklein, iheim, kgoldbla, lsurette, mlipchuk, rbalakri, Rhev-m-bugs, tnisan, yeylon, ylavi
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Let the user have the ability to import an existing Storage Domain of ISO Data or Export and override the name description or type of the Storage Domain as he desire. Result: Add the ability to override the Storage Domain fields (name,description,type). Those changed fields will be reflected in the engine DB and in the GUI but will not get updated in the Storage Domain metadata until the user will update the Storage Domain ince it is active. Once a Storage Domain will be imported, if one of the fields will be blank (name, description) then the value from the Storage Domain metadata will be initialized, otherwise the fields which were provided in the user request will be used.
Story Points: ---
Clone Of: 1195784 Environment:
Last Closed: 2016-01-07 08:10:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1295852    
Bug Blocks:    

Comment 1 Allon Mureinik 2015-05-19 11:30:59 UTC
Yaniv/Scott - the block part was handled in bug 1195784 and will be included in 3.6.0.

This one requires a substantional extra effort. Please advise on priority.

Comment 2 Yaniv Lavi 2015-06-17 23:27:37 UTC
(In reply to Allon Mureinik from comment #1)
> Yaniv/Scott - the block part was handled in bug 1195784 and will be included
> in 3.6.0.
> 
> This one requires a substantional extra effort. Please advise on priority.

Since this is weekathon item, we will have to address the second part in 4.0.

Comment 3 Maor 2016-01-07 08:07:31 UTC
Since this RFE is also part of this bug fix:
https://bugzilla.redhat.com/1295852

and since the fix seems to be quite trivial (REST is already supported)
I assume this RFE can be available for 3.6

Comment 4 Red Hat Bugzilla Rules Engine 2016-01-07 08:07:36 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Red Hat Bugzilla Rules Engine 2016-01-07 08:09:29 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 Red Hat Bugzilla Rules Engine 2016-01-07 08:09:29 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 7 Yaniv Lavi 2016-01-07 08:10:15 UTC
(In reply to Maor from comment #3)
> Since this RFE is also part of this bug fix:
> https://bugzilla.redhat.com/1295852
> 
> and since the fix seems to be quite trivial (REST is already supported)
> I assume this RFE can be available for 3.6

Closing as dup

*** This bug has been marked as a duplicate of bug 1295852 ***