no ability for vault:lb-provider to create an octavia LB for Vault VIP
Bug #1940328 reported by
Jeff Hillman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Openstack Integrator Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
charms stable/latest
Currently the *-integrator charms only work with Azure to provide a VIP for loadbalancer aware applicatoins, such as vault. The openstack-
the current work around is to manually create an openstack port, assign a FIP (when necessary), allow all vault units to access that port, then set the VIP in the vault charm option.
| Changed in charm-openstack-integrator: | |
| milestone: | none → 1.25 |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.25 → 1.26 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.26 → 1.26+ck1 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.26+ck1 → 1.26+ck2 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.26+ck2 → 1.27 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.27 → 1.27+ck1 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.27+ck1 → 1.28 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.28 → 1.28+ck1 |
| Changed in charm-openstack-integrator: | |
| milestone: | 1.28+ck1 → 1.29 |
To post a comment you must log in.
