subnet-id should be discoverable, shouldn't have to be configured
Bug #1835960 reported by
Jason Hobbs
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Openstack Integrator Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
here is my bundle that was used to deploy k8s on openstack
http://
Here is the output of me adding the k8s to juju and trying to bootstrap it:
http://
We never get endpoints for the controller-service and juju bootstrap eventually gives up.
http://
I don't know why it's not getting endpoints, or what to look for.
no longer affects: | juju |
summary: |
- juju k8s bootstrap of k8s on openstack fails with polling k8s controller - svc DNS, in xx attempt, controller service address not provisioned + subnet-id should be discoverable, shouldn't have to be configured |
Changed in charm-openstack-integrator: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
To post a comment you must log in.
I was able to get past this by setting the subnet-id config on the openstack- integrator charm to the subnet my openstack units are allocated on. It seems like the openstack- integrator charm should be able to figure that out on its own, given it was deployed on that subnet...