juju2 openstack provider setting default network

Bug #1570219 reported by Brad Marshall
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned

Bug Description

I'm trying to deploy a multiuser juju2 controller and models to an Openstack Mitaka cloud, and am having problems with spinning up VMs.

$ juju2 bootstrap cs canonistack
Creating Juju controller "local.cs" on canonistack/bootstack-canonistack-bos01
Bootstrapping model "admin"
Starting new instance for initial controller
Launching instance

ERROR failed to bootstrap model: cannot start bootstrap instance: cannot run instance: failed to run a server with nova.RunServerOpts{Name:"juju-uuid-machine-0", FlavorId:"2", ImageId:"image-id", UserData:[]uint8{*snip*}, SecurityGroupNames:[]nova.SecurityGroupName{nova.SecurityGroupName{Name:"juju-uuid"}, nova.SecurityGroupName{Name:"juju-uuid"}}, Networks:[]nova.ServerNetworks{}, AvailabilityZone:"nova", Metadata:map[string]string{"juju-model-uuid":"uuid", "juju-is-controller":"true"}, ConfigDrive:false}

caused by: request (http://x.y.z.12:8774/v2/uuid/servers) returned unexpected status: 409; error info: {"conflictingRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 409}}

If I then bootstrap with juju2 bootstrap cs canonistack --config network=<netid> it works fine, but then I can't deploy any instances, or enable HA or anything else, as the VMs then error out with the same error:

  Multiple possible networks found, use a Network ID to be more specific

I've been unable to find a way to set the default network, or how to tell a juju2 deploy what network it should be on. Even if that was possible, it would seem easier to be able to set a default network, as people might not have openstack access or know how to find that information.

I also checked out spaces, but they don't seem to be usable on OpenStack yet.

$ juju2 --version
2.0-beta3-trusty-amd64

Please let me know if you need any further information.

Curtis Hovey (sinzui)
tags: added: network openstack-provider
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-rc1
Revision history for this message
Brad Marshall (brad-marshall) wrote :

With 2.0 beta 4, once I juju-2.0 bootstrap with the --config network=<netid>, I can then boot VMs, enable HA or anything else without any issues.

Revision history for this message
Cheryl Jennings (cherylj) wrote :

Based on the previous comment, it looks like this was addressed in beta4.

Changed in juju-core:
status: Triaged → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta5 → none
milestone: none → 2.0-beta5
Revision history for this message
Bruno Carvalho (brunowcs) wrote :

plz send your config openstack cloud for juju2

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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