Bug #9981
closedSmart variable doesn't show error on new variable
Description
Steps to reproduce:
1. create a new smart variable with parameter type integer and a matcher with the value 'abc'
2. try to save the puppetclass
Expected result: tab becomes red, next to value an error message "is invalid integer"
Actual result: the variable disappears and the puppetclass can't be saved
Workaround for now: save the puppetclass when the variable is empty (only parameter, type and default value) and then edit.
When the variable is updated the validations are shown correctly.
Updated by Ori Rabin over 9 years ago
- Related to Tracker #4470: Usability of parameters and overrides added
Updated by Walden Raines almost 9 years ago
- Status changed from New to Assigned
- Assignee set to Walden Raines
Updated by Walden Raines almost 9 years ago
There are, in fact, two issues here.
1. If you don't enter a key then it saves the puppet class but does not attempt to save the new smart variable at all and spits you out on the puppetclasses list page
2. If you enter a key and also enter an invalid default value (a string for an int, for example) then the form marks itself as invalid but does not specify what the actual issue is
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/2693 added
- Pull request deleted (
)
Updated by Ori Rabin almost 9 years ago
- Assignee changed from Walden Raines to Tom Caspy
Updated by Dominic Cleal almost 9 years ago
- Related to Bug #8416: Puppetclasses edit n+1 query added
Updated by Dominic Cleal almost 9 years ago
- Translation missing: en.field_release set to 71
Updated by Tom Caspy almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset de65857c3ebc9717d1796e9c99c7e1fceeffa8d2.