Bug #3889
No validation errors for nested class parameters on Puppet class edit page
Description
When a validation errors occurs on the puppet class edit page, no validation messages are returned to the UI for nested smart class parameters and matchers.
Related issues
Associated revisions
History
#1
Updated by Dominic Cleal about 7 years ago
- Related to Bug #2726: Smart Class Parameter - over-ride match value unable to set yaml added
#2
Updated by Dominic Cleal about 7 years ago
- Status changed from Assigned to Ready For Testing
#3
Updated by Dominic Cleal about 7 years ago
- Related to Bug #3871: Foreman 1.3.1: Adding a new smart class parameter override fails if there is an existing match on an hostgroup that don't exist. added
#4
Updated by Dominic Cleal about 7 years ago
- Legacy Backlogs Release (now unused) changed from 3 to 2
#5
Updated by Dominic Cleal about 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset a387cbcbbae22a6283d229eebbf77f0b3932d27f.
fixes #3889 - don't reload nested lookup keys during render, so validation errors aren't lost