Bug #13727
closed
Error not raised while setting default value when 'Override' set to False for parameter.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1308860
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:
Updated by Dominic Cleal almost 9 years ago
- Subject changed from CLI Error not raised while setting default value when 'Override' set to False for parameter. to Error not raised while setting default value when 'Override' set to False for parameter.
- Category set to Parameters
Applies to the API.
Updated by Ori Rabin almost 9 years ago
- Status changed from New to Assigned
- Assignee set to Ori Rabin
Updated by The Foreman Bot almost 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3204 added
Updated by Dominic Cleal almost 9 years ago
- Related to Bug #13832: Both Matcher Value and puppet-default value can be set at a time in sc-param added
Updated by Ori Rabin over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 2a08e8c1deac40c26932dc80ca53e89bfe9e493b.
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 136
Updated by Dominic Cleal over 8 years ago
- Related to Bug #15308: editing puppet class parameter with arrays and hashes fails when not overriding added