Description of problem:
After upgrade of environment from previous versions customers are not allowed to change template versioning policy for the existing pools.
The constraint is rather in UI than on other levels as the change is rather trivial and manually takes only single DB query (update of template_version_number entry in vm_static table).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create template with Base template version
2. Try to edit it to the latest version
It cannot be edited
It should be editable
Verified with rhevm-3.6.2-0.1.el6.noarch.
After creating a vm pool from template with 5 version (choose version 1 at first), changing the version is possible via ui to each of the 5 version + to the latest pointer.
Each change between version will invoke vms deletion and re creation from the new chosen version as expected.
Please notice that there is a regression on the latest pointer as can be seen in this bz: https://bugzilla.redhat.com/show_bug.cgi?id=1294511.
Might be caused by this patch?
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:
The documentation team will review, edit, and approve the text.
If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
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.