Canonical Juju

improve openstack provider error reporting when no networks specified at bootstrap

Bug #1687724 reported by Heather Lanigan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Since bootstrap without a networking is a common openstack provider failure, let's have a
message indicating what to do. We can also skip calling RunServer() since we know it will fail.

One thing to investigate is, can we determine if there is only 1 network available with
router:external set to false, if so, use that for DefaultNetwork().

There is also a newer "feature" in openstack where you can specify network as "auto". Should we
make use of it?

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

See also: https://bugs.launchpad.net/juju/+bug/1188126

Tim Penhey (thumper)
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

There have been clouds where no network is seen by the user/juju, but is handled behind the scenes, thus juju will still bootstrap.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.