setup-neutron hardcodes "datacentre" as the physical network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-cloud-config |
Fix Released
|
High
|
Steve Kowalik | ||
tripleo |
Fix Released
|
High
|
Steve Kowalik |
Bug Description
++ os-apply-config -m /home/shared/
+ BM_NETWORK_
+ '[' -n 1598 ']'
+ BM_NETWORK_GATEWAY=
++ os-apply-config -m /home/shared/
+ BM_NETWORK_
++ os-apply-config -m /home/shared/
+ BM_NETWORK_
++ os-apply-config -m /home/shared/
+ UNDERCLOUD_
++ mktemp
+ NETWORK_
+ jq .
+ setup-neutron -n /tmp/tmp.XiPMDf9AIZ
+ rm /tmp/tmp.XiPMDf9AIZ
+ '[' -n 1598 ']'
++ jq -r '.["baremetal-
+ BM_VLAN_
++ jq -r '.["baremetal-
+ BM_VLAN_
++ mktemp
+ PUBLIC_
+ jq .
+ setup-neutron -n /tmp/tmp.cUvUPuAj2B
2014-12-02 16:23:09 - root - ERROR - Unexpected error during command execution
Traceback (most recent call last):
File "/home/
keystone_
File "/home/
net = _create_
File "/home/
return neutron.
File "/home/
ret = self.function(
File "/home/
return self.post(
File "/home/
headers=
File "/home/
self.
File "/home/
exception_
File "/home/
status_
BadRequest: Invalid input for operation: physical_network 'datacentre' unknown for VLAN provider network.
stack@bastion:
{
"physical": {
"enable_dhcp": false,
"gateway": "15.126.48.1",
"metadata_
"cidr": "15.126.48.0/24",
"allocation
"allocation
"name": "public",
"nameserver": "",
"segmentati
}
}
It looks to me as though the value "datacentre" is coming from around http://
If 'datacentre' doesn't work, the cod shouldn't set it as a default value. If 'datacentre' will work if the correct setup has been done beforehand, that setup should be documented.
Changed in os-cloud-config: | |
status: | Incomplete → Confirmed |
assignee: | nobody → Steve Kowalik (stevenk) |
Changed in tripleo: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Steve Kowalik (stevenk) |
summary: |
- setup-neutron has default values that don't work + setup-neutron hardcodes "datacenter" as the physical network |
Changed in os-cloud-config: | |
status: | Confirmed → In Progress |
summary: |
- setup-neutron hardcodes "datacenter" as the physical network + setup-neutron hardcodes "datacentre" as the physical network |
Changed in os-cloud-config: | |
status: | Fix Committed → Fix Released |
As far as I can tell, tripleo used to use the old shell version of setup-neutron; this was removed in https:/ /review. openstack. org/#/c/ 117401
In this version, the provider: physical_ network parameter used $PHYSICAL_NETWORK, which was read from $6, which in https:/ /review. openstack. org/#/c/ 117401/ 2/scripts/ devtest_ undercloud. sh was ctlplane
I don't know why the new setup-neutron has this hardcoded to "datacentre" when the old setup-neutron had it configureable (and tripleo defaulted to call it "ctlplane"; but imo this seems to be a backwards- compatibility break.
I think that the new setup-neutron should take a parameter for configuring this, just like the old setup-neutron did.