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
2016-05-09 21:02:03 UTC
Created attachment 1155467[details]
Full trace
Description of problem:
A new version of a module, with a new default for a parameter seems to trigger Foreman's validation of parameters: the new default is seen as a changed parameter and Foreman errors out with:
ActiveRecord::RecordInvalid: Validation failed: Override must be true to edit the parameter
Version-Release number of selected component (if applicable):
6.2.0 beta SNAP 10
How reproducible:
using hammer proxy import-classes --environment xxx --id xx
Steps to Reproduce:
1. create two environments, with the same simple module with one parameter in each
2. import the first environment
3. change the parameter in the second env and then import it
Actual results:
First import of second environment might(?) be ok, but second import will trigger validation errors like above.
Expected results:
environment with changed module is imported
Additional info:
I tried changing the version of the module to see if that would help to not trigger the validation, but it doesn't
For my simple test case, actually setting override to true for the parameter allowed me to import the environment.
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:1501
Created attachment 1155467 [details] Full trace Description of problem: A new version of a module, with a new default for a parameter seems to trigger Foreman's validation of parameters: the new default is seen as a changed parameter and Foreman errors out with: ActiveRecord::RecordInvalid: Validation failed: Override must be true to edit the parameter Version-Release number of selected component (if applicable): 6.2.0 beta SNAP 10 How reproducible: using hammer proxy import-classes --environment xxx --id xx Steps to Reproduce: 1. create two environments, with the same simple module with one parameter in each 2. import the first environment 3. change the parameter in the second env and then import it Actual results: First import of second environment might(?) be ok, but second import will trigger validation errors like above. Expected results: environment with changed module is imported Additional info: I tried changing the version of the module to see if that would help to not trigger the validation, but it doesn't For my simple test case, actually setting override to true for the parameter allowed me to import the environment.