Description of problem:
RHEV 3.4 allows for the creation of versioned templates, i.e. multiple templates with the same name, but a different version number. For version > 1 of a template, the API returns XML describing the template, including a stanza like:
<base_template href="/api/templates/857cd7ce-3461-4eb5-9acb-7a49404ec2f7" id="857cd7ce-3461-4eb5-9acb-7a49404ec2f7"/>
In my RHEV 3.4 setup, I have multiple versions of a template called 'vm_template'. When creating a new image under my RHEV compute resource, all these templates show up as just 'vm_template' in the 'image' selector field (which sounds pretty confusing, but I have no better way of describing this).
Version-Release number of selected component (if applicable):
Public beta, 6.0.3
Steps to Reproduce:
1. Connect Satellite 6 to RHEV 3.4 as compute resource.
2. Create versioned template 'foo' in RHEV 3.4, with at least two versions.
3. Try to use it in Satellite 6 by creating a new 'image' under the RHEV compute resource.
The 'image' selector field will show 'foo' and 'foo' for the two versions. Indistinguishable.
The 'image' selector field shows 'foo' and 'foo v.2 (enabled cloudinit)' or something similar.
Created redmine issue http://projects.theforeman.org/issues/6568 from this bug
Upstream bug assigned to email@example.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/6568 has been closed
requires these pull requests to be merged and released in order for this to work:
Applied in changeset commit:a647442376aceae2e539791790eb8f308b56cd3a.
Oh! ok, thanks for the info, will test it with rhev 3.5 then.
TESTED With sat62-snap8.1
We still face this issue with the above build.
Attaching a screenshot shortly.
Created attachment 1149124 [details]
versioned templates are indistinguishable
Upstream bug component is Compute Resources
It's been a while will verify this again with latest snap and update it here.
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.