Project

General

Profile

Actions

Bug #11663

closed

Empty lookup value validated even when use_puppet_default is checked

Added by Ori Rabin about 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

Since https://github.com/theforeman/foreman/blob/develop/app/models/lookup_value.rb#L10 was added
adding a matcher with an empty value isn't possible even when checking use_puppet_default.
Workaround for now: put any value, save the smart class parameter, edit it again and check use puppet default.


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #9187: Overrideable empty puppet class parameters are still validate their default valueClosedOri Rabin02/02/2015Actions
Related to Foreman - Bug #9812: 'match' and 'value' parameters in override value's create should be required in apidocClosedShlomi Zadok03/18/2015Actions
Actions #1

Updated by Dominic Cleal about 9 years ago

  • Related to Bug #9187: Overrideable empty puppet class parameters are still validate their default value added
Actions #2

Updated by Dominic Cleal about 9 years ago

  • Related to Bug #9812: 'match' and 'value' parameters in override value's create should be required in apidoc added
Actions #3

Updated by Dominic Cleal about 9 years ago

  • Translation missing: en.field_release set to 72

Appears to be a 1.9 regression.

Actions #4

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2674 added
  • Pull request deleted ()
Actions #5

Updated by Ori Rabin about 9 years ago

  • Assignee set to Ori Rabin
Actions #6

Updated by Ori Rabin about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF