Red Hat Bugzilla – Bug 1308860
CLI Error not raised while setting default value when 'Override' set to False for parameter.
Last modified: 2016-07-27 07:43:47 EDT
Created attachment 1127547 [details]
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):
Steps to Reproduce:
1. Attempt to set default value for parameter which override flag is set to False.
Default Value successfully updated and no error raised.
1. Error/Info should be raised to set the 'override' flag to True first.
2. Default Value should not be updated.
Same scenario is reproducible from API as well in same build.
Upstream bug component is Provisioning
Upstream bug assigned to email@example.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/13727 has been closed
Applied in changeset commit:2a08e8c1deac40c26932dc80ca53e89bfe9e493b.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
@Sat 6.2 Snap 11
root@qeblade36 ~]# hammer sc-param update --id 322 --default-value 
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.