Hide Forgot
Created attachment 1010630 [details] Disks-tab Description of problem: See att image - there is not clear which disk belongs to which template version (1st and last on image). Version-Release number of selected component (if applicable): saw on 3.5.0, but probably on newer as well. How reproducible: 100% Steps to Reproduce: 1. Have template & create new version of it 2. see the Disk tab for both templates and their disks 3. Actual results: Currently I've 2 images where each lies on different storage. Expected results: Clearly distinguished disks in Disks tab Additional info:
you give the name during the create process... just like when crating regular templates.. if you like to have a unique name, just write it there in the dialog. did i misunderstand the issue? or can we close this?
Unfortunately there is problem. If you'll do same for VM based on template - see steps: Create Template name BBB, create VM, name it CCC based on BBB (only choose VM name, nothing else changed - no disk renaming) then switched to Disks tab you'll see: two disks with name BBB_Disk1, each will have different ID and one will have 'Attached To' column BBB and second CCC. Here we have different behaviour with versioned templates - there is NO distinguish among TempalteOriginal & TemplateVersionX - as the column 'AttachedTo' is same for both - see original image. Adding another pic with templates - the name is same, only Version differs (but in disks there is no such identifier). (sory I wasn't more specific before).
Created attachment 1011102 [details] templates-tab
would probably enough to show disks like "Attached To: template(subversion)". Just need a note in docs what that thing in parenthesis mean
ok, rhevm-4.0.0-0.7.master.el7ev.noarch template disks in Disks maintab contain following info in 'Attached To' column: $vm (base version) $vm (template sub-name)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html