Project

General

Profile

Actions

Bug #14292

closed

Child hostgroup cloning issue with array parameters

Added by Jeff Sault over 8 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Host groups
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

This is a bit of an odd one but during the cloning of a hostgroup it seems that array/json class parameter overrides can become invalid.

Pre-req:
2 x environments with the same classes in both.
2 x identical hostgroups in different environments. Not sure if having classes in them is mandatory or not
1 x child hostgroup containing a class with an array-type override set.

Step to reproduce:
Clone the child hostgroup from one environment to the other, changing both the parent HG and environment fields during the clone process.

Expected:
HG should be cloned with override parameter kept.

Actual:
Parameter override values are cloned with additional escape sequences, causing them to fail validation. See attached.


Files

foreman_error.png View foreman_error.png 7.51 KB Jeff Sault, 03/21/2016 08:04 AM

Related issues 1 (1 open0 closed)

Related to Foreman - Bug #12284: host group parameter overrides reformatting YAML values to stringsNew10/23/2015Actions
Actions #1

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #12284: host group parameter overrides reformatting YAML values to strings added
Actions #2

Updated by Dominic Cleal over 8 years ago

  • Category set to Host groups

It might be worth trying this on 1.11, it could have been fixed when the parameter tab was changed.

Actions #3

Updated by MARCIN BOJKO over 7 years ago

  • Priority changed from Normal to High

This bug is still active in 1.14.2 - it prevents from cloning groups, hosts and even changing host's domains.
With every touch all YAML arrays are being converted to strings with \n signs, so the config is just gone.

Actions #4

Updated by J. A. over 6 years ago

Oftentimes I get this when editing a host too. This just happened to me on 1.16.1 but it happened to me on 1.{13,14,15} as well.

Actions #5

Updated by yifat makias over 3 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF