Project

General

Profile

Actions

Bug #13727

closed

Error not raised while setting default value when 'Override' set to False for parameter.

Added by Jitendra Yejare almost 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Parameters
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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:


Related issues 2 (0 open2 closed)

Related to Hammer CLI - Bug #13832: Both Matcher Value and puppet-default value can be set at a time in sc-paramClosedAdam Ruzicka02/22/2016Actions
Related to Foreman - Bug #15308: editing puppet class parameter with arrays and hashes fails when not overridingClosedOri Rabin06/06/2016Actions
Actions

Also available in: Atom PDF