magnum/releasenotes/notes/fix-serveraddressoutputmapping-for-private-clusters-73a874bb4827d568.yaml

---
fixes:
  - |
    Fix an issue with private clusters getting stuck in CREATE_IN_PROGRESS
    status where floating_ip_enabled=True in the cluster template but this is
    disabled when the cluster is created.
Fix ServerAddressOutputMapping for private clusters Following changes were introduced in Train release: - Allow setting network, subnet and FIP when creating cluster (I11579ff6b83d133c71c2cbf49ee4b20996dfb918) - ng-7: Adapt parameter and output mappings (I45cf765977c7f5a92f28ae12c469b98435763163) The first change allowed setting cluster.floating_ip_enabled but the second change introduced ServerAddressOutputMapping conditional on cluster_template.floating_ip_enabled which leads to an edge case where if floating_ip_enabled is overriden to False when a cluster is created when it is True in the cluster_template scope, we see this error in the conductor logs: ValueError: Field `node_addresses[0]' cannot be None and the cluster remains forever stuck in CREATE_IN_PROGRESS status despite Heat reaching CREATE_COMPLETE. This commit addresses this issue by correctly referring to the cluster.floating_ip_enabled. Change-Id: Ic83f625178786d4750a66dd6dd6db35c05bc0272 Story: 2007550 Task: 39401 2020-04-14 15:37:49 +00:00			`---`
			`fixes:`
			`- \|`
			`Fix an issue with private clusters getting stuck in CREATE_IN_PROGRESS`
			`status where floating_ip_enabled=True in the cluster template but this is`
			`disabled when the cluster is created.`