Bug #23463
closed
YAML rendering of external nodes generates incorrect data if hashes are used
Added by Anonymous over 6 years ago.
Updated over 6 years ago.
Description
Rendering the external YAML data of a host causes Foreman to generate incorrect data if it includes hashes that are set in parameterised classes.
Generated YAML:
classes:
easystack:
ceph_monitors:
- !ruby/hash:ActiveSupport::HashWithIndifferentAccess
fqdn: [RETRACTED]
ip: [RETRACTED]
master: true
- !ruby/hash:ActiveSupport::HashWithIndifferentAccess
fqdn: [RETRACTED]
ip: [RETRACTED]
master: true
- !ruby/hash:ActiveSupport::HashWithIndifferentAccess
fqdn: [RETRACTED]
ip: [RETRACTED]
master: true
This seems to be a duplicate of #9240 and was introduced again somewhere between 1.16.1 and 1.17.0.
- Related to Bug #23382: Editing Smart Class Parameter of type YAML creates malformed value in release 1.17.0 added
- Translation missing: en.field_release set to 360
- Category changed from API to Parameters
Does anyone have a good reproducer for this one? I'm able to get the following hashes right:
classes:
dhcp:
bootfiles:
'00:06': grub2/bootia32.efi
'00:07': grub2/bootx64.efi
'00:09': grub2/bootx64.efi
- Status changed from New to Duplicate
This is most certainly a duplicate of #23382
- Related to deleted (Bug #23382: Editing Smart Class Parameter of type YAML creates malformed value in release 1.17.0)
- Is duplicate of Bug #23382: Editing Smart Class Parameter of type YAML creates malformed value in release 1.17.0 added
Also available in: Atom
PDF