Comment 10 for bug 1638704

All right, so I tested this with the 2.0.2 build from juju-proposed and now I'm confused:

09:21:39 DEBUG juju.provider.openstack provider.go:945 allocating public IP address for openstack node
09:21:40 INFO juju.provider.common destroy.go:20 destroying model "controller"
09:21:40 INFO juju.provider.common destroy.go:31 destroying instances
09:21:41 DEBUG juju.provider.openstack provider.go:1075 terminating instances []
09:21:42 INFO juju.provider.common destroy.go:51 destroying storage
09:21:42 DEBUG juju.provider.openstack cinder.go:80 volume URL: https://<hostname>:8776/v2/22f3992b3e2b4a07a7253199c93cd4f9
09:21:44 ERROR cmd supercommand.go:458 failed to bootstrap model: cannot start bootstrap instance: cannot allocate a public IP as needed: failed to allocate a floating ip
caused by: Resource at https://<hostname>:8774/v2/22f3992b3e2b4a07a7253199c93cd4f9/os-floating-ips not found
caused by: request (https://<hostname>:8774/v2/22f3992b3e2b4a07a7253199c93cd4f9/os-floating-ips) returned unexpected status: 404; error info: {"itemNotFound": {"message": "Floating ip pool not found.", "code": 404}}
09:21:44 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:556: failed to bootstrap model} {github.com/juju/juju/provider/common/bootstrap.go:47: } {github.com/juju/juju/provider/common/bootstrap.go:178: cannot start bootstrap instance} {github.com/juju/juju/provider/openstack/provider.go:947: cannot allocate a public IP as needed} {failed to allocate a floating ip
caused by: Resource at https://<hostname>:8774/v2/22f3992b3e2b4a07a7253199c93cd4f9/os-floating-ips not found
caused by: request (https://<hostname>:8774/v2/22f3992b3e2b4a07a7253199c93cd4f9/os-floating-ips) returned unexpected status: 404; error info: {"itemNotFound": {"message": "Floating ip pool not found.", "code": 404}}}])

Compare this from "nova --debug floating-ip-list":

DEBUG (session:248) REQ: curl -g -i -X GET https://<hostname>:8774/v2/22f3992b3e2b4a07a7253199c93cd4f9/os-floating-ips -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: <token>"
DEBUG (connectionpool:388) "GET /v2/22f3992b3e2b4a07a7253199c93cd4f9/os-floating-ips HTTP/1.1" 200 20
DEBUG (session:277) RESP: [200] Date: Mon, 14 Nov 2016 09:22:54 GMT Content-Length: 20 Content-Type: application/json X-Compute-Request-Id: req-15cd6d3a-286a-4282-b2de-1143415870b9
RESP BODY: {"floating_ips": []}

+----+----+-----------+----------+------+
| Id | IP | Server Id | Fixed IP | Pool |
+----+----+-----------+----------+------+
+----+----+-----------+----------+------+

So now it's using exactly the URI that it should, but still produces a 404. What exactly is going on there?