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:
Same scenario is reproducible from API as well in same build.
Upstream bug component is Provisioning
Upstream bug assigned to orabin
Moving to POST since upstream bug http://projects.theforeman.org/issues/13727 has been closed ------------- Ori Rabin Applied in changeset commit:2a08e8c1deac40c26932dc80ca53e89bfe9e493b.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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