Canonical Juju

Openstack Provisioning Fails When No Networks Exist

Bug #1785564 reported by Joseph Phillips on 2018-08-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Fix Released	High	Joseph Phillips	Canonical Juju 2.4.2

Bug Description

The patch provided to address https://bugs.launchpad.net/juju/+bug/1780274 assumed that when no network ID existed in model config, and network resolution returned an error, then this would be due to multiple networks being returned.

This is not the case for Canonistack, which lists no networks. The change required is to treat missing config for network ID as *not* an error condition when there are no networks at all. This should restore the prior behaviour for that case.

Joseph Phillips (manadart) on 2018-08-06

Changed in juju:
milestone:	none → 2.4.2
assignee:	nobody → Joseph Phillips (manadart)
importance:	Undecided → High
status:	New → Triaged
status:	Triaged → In Progress