Train -> Wallaby - FFU - Network-v2 idempotency not working
Bug #1970936 reported by
Harald Jensås
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
Critical
|
Harald Jensås |
Bug Description
In https:/
The dns_domain is not set in Train, so after undercloud FFU running pre-provision commands to create the environment file describing the baremetal deployment end up creating new ports instead of updateing/re-using the existing ports that where created when deploying the Train overcloud.
We need to backport - https:/
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/839911 /opendev. org/openstack/ tripleo- heat-templates/ commit/ b72fa565994c599 dce10f61df46e19 39d705e06f
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/train
commit b72fa565994c599 dce10f61df46e19 39d705e06f
Author: Harald Jensås <email address hidden>
Date: Sat Mar 28 03:47:06 2020 +0100
Set dns_name propery on ports and networks
Neutron's dns_assignments field includes a nice pice of
structured data. This is a prerequirement for Designate
usage. (No plan's to use that, but being a bit ready
does'nt hurt.)
{"hostname": "my-vm",
"ip_address" : "192.0.2.16", example. org."}
"fqdn": "my-vm.
Enable for the undercloud:
- dns_domain_ports ml2 extension driver
Need to backport this to train because network-v2 idempotency 533f4269cdfec40 d3634684e22
rely on the dns_doman. In Ie326f30fcc3d93
idempotency was change to use dns_domain instead of a neutron tag
with the hostname because of neutron's limit on 60 chars per tag.
Without this change the provisioning workflow will create duplicate
ports when FFU upgrade is performed.
Conflicts: .j2.yaml
overcloud
Closes-Bug: #1970936 1b27524fe4d1fda b617b6fa948 96a1fcddb7aeb78 fc6735809f)
Change-Id: I46eb9a24dd6682
(cherry picked from commit 679ecaada05768e