Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMaxim Burgerhout
2014-07-10 14:22:57 UTC
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:
<version>
<base_template href="/api/templates/857cd7ce-3461-4eb5-9acb-7a49404ec2f7" id="857cd7ce-3461-4eb5-9acb-7a49404ec2f7"/>
<version_number>2</version_number>
<version_name>enabled cloudinit</version_name>
</version>
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
How reproducible:
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.
Actual results:
The 'image' selector field will show 'foo' and 'foo' for the two versions. Indistinguishable.
Expected results:
The 'image' selector field shows 'foo' and 'foo v.2 (enabled cloudinit)' or something similar.
Additional info:
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://access.redhat.com/errata/RHBA-2016:1500
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: <version> <base_template href="/api/templates/857cd7ce-3461-4eb5-9acb-7a49404ec2f7" id="857cd7ce-3461-4eb5-9acb-7a49404ec2f7"/> <version_number>2</version_number> <version_name>enabled cloudinit</version_name> </version> 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 How reproducible: 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. Actual results: The 'image' selector field will show 'foo' and 'foo' for the two versions. Indistinguishable. Expected results: The 'image' selector field shows 'foo' and 'foo v.2 (enabled cloudinit)' or something similar. Additional info: