Also such situation affects us if plugin modify network_metadata and end-user rename node after deploy (LCM). Such scenario leads a to duplicate node record into the hiera_hash('network_metadata') call:
network_metadata: nodes: node-1: swift_zone: '1' uid: '1' fqdn: node-1.test.domain.local user_node_name: Untitled (38:fb) node_roles: - primary-controller - plugin-modified-node_role_record name: node-1 renamed_node-1: swift_zone: '1' uid: '1' fqdn: renamed_node-1.test.domain.local user_node_name: renamed_node-1 (38:fb) node_roles: - primary-controller name: renamed_node-1
Also such situation affects us if plugin modify network_metadata and end-user rename node after deploy (LCM). 'network_ metadata' ) call:
Such scenario leads a to duplicate node record into the hiera_hash(
network_ metadata:
swift_ zone: '1' test.domain. local
user_ node_name: Untitled (38:fb)
node_ roles: modified- node_role_ record
renamed_ node-1:
swift_ zone: '1' node-1. test.domain. local
user_ node_name: renamed_node-1 (38:fb)
node_ roles:
nodes:
node-1:
uid: '1'
fqdn: node-1.
- primary-controller
- plugin-
name: node-1
uid: '1'
fqdn: renamed_
- primary-controller
name: renamed_node-1