Description of problem: Add template versions to the entity OVF, so on registration the engine will be able to register the template with its versions Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Would not doing for 4.2 this mean that any VM would break if the templates has versions?
template version seems to be part of the OVF after all. Verified it trough the GUI with success. Once the storage domain is attached to the setup, we can see two Templates with the same name which exists under the unregistered entities sub tab. The user should only pick the base volume to be registered and that will cause the Template to be registered with its other version. Closing this bug as current release.