Amphora has incorrect cached_zone after migrating amphora instance to another availability zone
Issue
- When we live-migrate an amphora instance to another availability zone, the amphora still shows old cached_zone in octavia, which is different from its actual availabiliy_zone
+-----------------+--------------------------------------+
| Field | Value |
+-----------------+--------------------------------------+
| id | 96af613a-2529-4dae-a65f-f65f50a8957a |
| loadbalancer_id | 1443af85-1bf8-4a01-ad97-3a54e483eaed |
| compute_id | 8839cfbf-2fb6-4de5-add5-0e313998598d |
| lb_network_ip | 172.24.0.1 |
| vrrp_ip | 192.168.0.100 |
| ha_ip | 192.168.0.101 |
| vrrp_port_id | 3a14c027-dd41-4094-8e07-ec0574020a48 |
| ha_port_id | 18914663-4376-47c2-af95-6521a5846744 |
| cert_expiration | 2022-01-23T01:23:45 |
| cert_busy | False |
| role | STANDALONE |
| status | ALLOCATED |
| vrrp_interface | None |
| vrrp_id | 1 |
| vrrp_priority | None |
| cached_zone | nova1 | <==== THIS IS NOT UPDATED
+-----------------+--------------------------------------+
Environment
- Red Hat OpenStack Platform 13
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.