Project

General

Profile

Actions
Copy link

Bug #3871

closed

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 by Peter Gustafsson about 11 years ago. Updated almost 11 years ago.

Status:
Duplicate
Priority:
High
Assignee:
-
Category:
Parameters
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hi,

Adding a new smart class parameter override from the Smart Class Parameter page fails if there is an existing match on an hostgroup that don't exist.
It fails silent so if there is many matches defined, it is a tedious task to find the failing match.
This situation can occur if you rename a host group that there is matches on.

Br, Peter

Related issues 3 (0 open — 3 closed)

Related to Foreman - Bug #3206: Prevent any user including admin from creating lookup_value with fdqn= to host that doesn't existClosedJoseph Magen10/06/2013Actions
Related to Foreman - Bug #3889: No validation errors for nested class parameters on Puppet class edit pageClosedDominic Cleal12/16/2013Actions
Is duplicate of Foreman - Bug #2866: Changing a hostgroup name doesn't update associated Smart Variable matchersClosedJoseph Magen07/31/2013Actions
Actions
Copy link

Also available in: Atom PDF