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.
DescriptionJitendra Yejare
2016-02-16 09:58:59 UTC
Created attachment 1127547[details]
Screenshot Attached
Description of problem:
User is able to set the default value for parameter even if the 'override' flag is not set for the parameter, which is not expected.
Note: This issue is only observed in CLI and not in UI.
Version-Release number of selected component (if applicable):
foreman-1.11.0-0.develop.201601251557git59dc77b.el6.noarch
How reproducible:
Always
Steps to Reproduce:
1. Attempt to set default value for parameter which override flag is set to False.
Actual results:
Default Value successfully updated and no error raised.
Expected results:
1. Error/Info should be raised to set the 'override' flag to True first.
2. Default Value should not be updated.
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/13727 has been closed
-------------
Ori Rabin
Applied in changeset commit:2a08e8c1deac40c26932dc80ca53e89bfe9e493b.
Verified !
@Sat 6.2 Snap 11
Proof:
root@qeblade36 ~]# hammer sc-param update --id 322 --default-value [78]
Could not update the parameter:
Validation failed: Override must be true to edit the parameter
So moving this to verified.
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 1127547 [details] Screenshot Attached Description of problem: User is able to set the default value for parameter even if the 'override' flag is not set for the parameter, which is not expected. Note: This issue is only observed in CLI and not in UI. Version-Release number of selected component (if applicable): foreman-1.11.0-0.develop.201601251557git59dc77b.el6.noarch How reproducible: Always Steps to Reproduce: 1. Attempt to set default value for parameter which override flag is set to False. Actual results: Default Value successfully updated and no error raised. Expected results: 1. Error/Info should be raised to set the 'override' flag to True first. 2. Default Value should not be updated. Additional info: