undercloud.conf subnets option - help cause confusion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Harald Jensås |
Bug Description
The example of subnet section is explained in line 54.
~~~
42 # List of routed network subnets for provisioning and introspection.
43 # Comma separated list of names/tags. For each network a section/group
44 # needs to be added to the configuration file with these parameters
45 # set: cidr, dhcp_start, dhcp_end, inspection_iprange, gateway and
46 # masquerade_network.
47 #
48 # Example:
49 #
50 # subnets = subnet1,subnet2
51 #
52 # An example section/group in config file:
53 #
54 # [subnet1]
55 # cidr = 192.168.10.0/24
56 # dhcp_start = 192.168.10.100
57 # dhcp_end = 192.168.10.200
58 # inspection_iprange = 192.168.
59 # gateway = 192.168.10.254
60 # masquerade_network = True
61 # [subnet2]
62 # . . .
63 # (list value)
64 #subnets = ctlplane-subnet
~~~
The 'ctlplane-subnet' section defined at the end of the file at line no. 358
~~~
358 [ctlplane-subnet]
359
360 #
361 # From instack-undercloud
362 #
363
364 # Network CIDR for the Neutron-managed subnet for Overcloud instances.
365 # (string value)
366 # Deprecated group/name - [DEFAULT]
367 #cidr = 192.168.24.0/24
~~~
The deployment fails if we modify the value in example section.
I.e users place the section defining provisioning subnets right in the middle of the DEFAULT section.
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
status: | Triaged → Fix Released |
Related fix proposed to branch: master /review. openstack. org/578172
Review: https:/