Bug #6568
closedRHEV 3.4 versioned templates are indistinguishable
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1118369
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:
Updated by Dominic Cleal about 10 years ago
- Category set to Compute resources - oVirt
Updated by Tom Caspy over 9 years ago
requires these pull requests to be merged and released in order for this to work:
https://github.com/abenari/rbovirt/pull/59
https://github.com/fog/fog/pull/3394
Updated by Tom Caspy over 9 years ago
- Status changed from New to Pending
- Pull request https://github.com/theforeman/foreman/pull/2076 added
- Pull request deleted (
)
Updated by The Foreman Bot over 9 years ago
- Status changed from Pending to Ready For Testing
Updated by Tom Caspy over 9 years ago
- Status changed from Ready For Testing to Pending
Updated by The Foreman Bot over 9 years ago
- Status changed from Pending to Ready For Testing
Updated by Tom Caspy over 9 years ago
- Status changed from Ready For Testing to Pending
how can we stop the bot from changing the status, this is annoying :)
Updated by The Foreman Bot over 9 years ago
- Status changed from Pending to Ready For Testing
Updated by Dominic Cleal over 9 years ago
- Blocked by Refactor #9107: Update fog to 1.28.x added
Updated by Tom Caspy over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset a647442376aceae2e539791790eb8f308b56cd3a.
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 28