005cd1e6a6
When we create amphora for specific loadbalancer it would be good to get info about mapping pair loadbalancer-amphora as soon as possible. For example, if admin needs to debug connectivity issues with amphora VMs - loadbalancer_id won't be set until AmphoraComputeConnectivityWait task succeeds (which is never for such case) so they have to go to worker logs to understand which amphora is related to a currently creating loadbalancer. Co-Authored-By: Ann Taraday <akamyshnikova@mirantis.com> Change-Id: I865445af34bc63b90d965ef5e2c8f9f49aa9c2f3
10 lines
481 B
YAML
10 lines
481 B
YAML
---
|
|
other:
|
|
- |
|
|
Amphorae that are booting for a specific loadbalancer will now be linked to
|
|
that loadbalancer immediately upon creation. Previously this would not
|
|
happen until near the end of the process, leaving a gap during booting
|
|
during which is was difficult to understand which booting amphora belonged
|
|
to which loadbalancer. This was especially problematic when attempting to
|
|
troubleshoot loadbalancers that entered ERROR status due to boot issues.
|