Created attachment 1566764 [details]
undercloud.conf

New OSP 14 deployment with routed control plane (provisioning) network.  I would like to have the local subnet (local_subnet in undercloud.conf) named simply "ctlplane" (rather than the default "ctlplane-subnet"), so that the subnet name with match the segment/provider:physical_network name.

To that end, I've got the following in my undercloud.conf:

local_subnet = ctlplane
subnets = ctlplane,ctlplane-remote

#[ctlplane-subnet]

[ctlplane]
cidr = 192.168.19.0/24
dhcp_start = 192.168.19.101
dhcp_end = 192.168.19.200
inspection_iprange = 192.168.19.51,192.168.19.100
gateway = 192.168.19.254
masquerade_network = False

[ctlplane-remote]
cidr = 192.168.119.0/24
dhcp_start = 192.168.119.101
dhcp_end = 192.168.119.200
inspection_iprange = 192.168.119.51,192.168.119.100
gateway = 192.168.119.254
masquerade_network = False

(Note that the [ctlplane-subnet] section is commented out.)

Despite this, the ctlplane-subnet subnet and network segment are being created, with the derault 192.168.24.0/24 network address:

$ openstack network segment list -c Name -c Network
+-----------------+--------------------------------------+
| Name            | Network                              |
+-----------------+--------------------------------------+
| ctlplane-remote | 8bbf86d6-893d-4212-b74b-d4396b641e7e |
| ctlplane-subnet | 8bbf86d6-893d-4212-b74b-d4396b641e7e |
| ctlplane        | 8bbf86d6-893d-4212-b74b-d4396b641e7e |
+-----------------+--------------------------------------+

$ openstack subnet list -c Name -c Network -c Subnet
+-----------------+--------------------------------------+------------------+
| Name            | Network                              | Subnet           |
+-----------------+--------------------------------------+------------------+
| ctlplane        | 8bbf86d6-893d-4212-b74b-d4396b641e7e | 192.168.19.0/24  |
| ctlplane-subnet | 8bbf86d6-893d-4212-b74b-d4396b641e7e | 192.168.24.0/24  |
| ctlplane-remote | 8bbf86d6-893d-4212-b74b-d4396b641e7e | 192.168.119.0/24 |
+-----------------+--------------------------------------+------------------+

$ openstack network show ctlplane -f json -c segments 
{
  "segments": [
    {
      "provider:network_type": "flat", 
      "provider:physical_network": "ctlplane-remote", 
      "provider:segmentation_id": null
    }, 
    {
      "provider:network_type": "flat", 
      "provider:physical_network": "ctlplane", 
      "provider:segmentation_id": null
    }, 
    {
      "provider:network_type": "flat", 
      "provider:physical_network": "ctlplane-subnet", 
      "provider:segmentation_id": null
    }
  ]
}

It looks like the existence of "ctlplane-subnet" is effectively hardcoded in ${THT}/environments/undercloud.yaml:

  UndercloudCtlplaneSubnets:
    ctlplane-subnet:
      NetworkCidr: '192.168.24.0/24'
      NetworkGateway: '192.168.24.1'
      DhcpRangeStart: '192.168.24.5'
      DhcpRangeEnd: '192.168.24.24'

I.e. there's no way to get rid of the ctlplane-subnet via undercloud.conf.