Activity log for bug #1899964

Date Who What changed Old value New value Message
2020-10-15 11:44:54 Hemanth Nakkina bug added bug
2020-10-15 11:57:50 Edward Hope-Morley bug task added cloud-archive
2020-10-15 11:58:15 Edward Hope-Morley nominated for series cloud-archive/ussuri
2020-10-15 11:58:15 Edward Hope-Morley bug task added cloud-archive/ussuri
2020-10-15 11:58:15 Edward Hope-Morley nominated for series cloud-archive/train
2020-10-15 11:58:15 Edward Hope-Morley bug task added cloud-archive/train
2020-10-15 11:58:15 Edward Hope-Morley nominated for series cloud-archive/victoria
2020-10-15 11:58:15 Edward Hope-Morley bug task added cloud-archive/victoria
2020-10-15 11:58:32 Edward Hope-Morley cloud-archive/victoria: status New Fix Committed
2020-10-15 11:58:36 Edward Hope-Morley octavia (Ubuntu): status New Fix Released
2020-10-15 12:03:29 Pedro Victor Lourenço Fragola bug added subscriber Pedro Victor Lourenço Fragola
2020-10-15 13:22:45 Edward Hope-Morley nominated for series Ubuntu Groovy
2020-10-15 13:22:45 Edward Hope-Morley bug task added octavia (Ubuntu Groovy)
2020-10-15 13:22:45 Edward Hope-Morley nominated for series Ubuntu Focal
2020-10-15 13:22:45 Edward Hope-Morley bug task added octavia (Ubuntu Focal)
2020-10-15 13:23:52 Edward Hope-Morley cloud-archive/victoria: status Fix Committed Fix Released
2020-10-15 14:22:34 Edward Hope-Morley description Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked. [Impact] (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state. Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder) [Test Case] [Regression Potential] ------------------------------------------------------------------------ Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked.
2020-10-15 20:36:12 Edward Hope-Morley attachment added lp1899964-ussuri.debdiff https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1899964/+attachment/5422695/+files/lp1899964-ussuri.debdiff
2020-10-15 20:36:32 Edward Hope-Morley attachment added lp1899964-train.debdiff https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1899964/+attachment/5422697/+files/lp1899964-train.debdiff
2020-10-16 16:42:29 Edward Hope-Morley description [Impact] (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state. Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder) [Test Case] [Regression Potential] ------------------------------------------------------------------------ Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked. [Impact] (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state. Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder) [Test Case] * deploy Openstack with Octavia and 2 compute hosts e.g. ./generate-bundle.sh --use-stable-charms --release train --octavia --num-compute 3 * juju config octavia loadbalancer-topology=ACTIVE_STANDBY * create ubuntu vm and install apache2 (i.e. listen port 80) * create loadbalancer with vm as member and floating ip for LB vip * test connection with: nc -vz LB_FIP 80 * openstack loadbalancer amphora list * get amphora master vm uuid: openstack loadbalancer amphora show -c compute_id -f value <master> * openstack server show -c "OS-EXT-SRV-ATTR:host" -f value <master uuid> * poweroff compute host from previous step * openstack loadbalancer failover LB_UUID * wait a few seconds * openstack loadbalancer amphora list * Wait until you have one BACKUP and one MASTER * Test connection with: nc -vz LB_FIP 80 [Regression Potential] ------------------------------------------------------------------------ Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked.
2020-10-16 16:43:47 Edward Hope-Morley description [Impact] (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state. Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder) [Test Case] * deploy Openstack with Octavia and 2 compute hosts e.g. ./generate-bundle.sh --use-stable-charms --release train --octavia --num-compute 3 * juju config octavia loadbalancer-topology=ACTIVE_STANDBY * create ubuntu vm and install apache2 (i.e. listen port 80) * create loadbalancer with vm as member and floating ip for LB vip * test connection with: nc -vz LB_FIP 80 * openstack loadbalancer amphora list * get amphora master vm uuid: openstack loadbalancer amphora show -c compute_id -f value <master> * openstack server show -c "OS-EXT-SRV-ATTR:host" -f value <master uuid> * poweroff compute host from previous step * openstack loadbalancer failover LB_UUID * wait a few seconds * openstack loadbalancer amphora list * Wait until you have one BACKUP and one MASTER * Test connection with: nc -vz LB_FIP 80 [Regression Potential] ------------------------------------------------------------------------ Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked. [Impact] (from storyboard desciption) Currently if taskflow process is interrupted (during create/update/failover - node is rebooted or service is restarted) - loadbalancer will stuck in PENDING state. Taskflow provides persistence module which allows to save flows state for recovery https://docs.openstack.org/taskflow/latest/user/persistence.html Otherwise partially created/updated/deleted resources should be moved to ERROR state when service is up again. (like it is done in Cinder) [Test Case] * deploy Openstack with Octavia and 2 compute hosts e.g. ./generate-bundle.sh --use-stable-charms --release train --octavia --num-compute 3 * juju config octavia loadbalancer-topology=ACTIVE_STANDBY * create ubuntu vm and install apache2 (i.e. listen port 80) * create loadbalancer with vm as member and floating ip for LB vip * test connection with: nc -vz LB_FIP 80 * openstack loadbalancer amphora list * get amphora master vm uuid: openstack loadbalancer amphora show -c compute_id -f value <master> * openstack server show -c "OS-EXT-SRV-ATTR:host" -f value <master uuid> * poweroff compute host from previous step * openstack loadbalancer failover LB_UUID * wait a few seconds * openstack loadbalancer amphora list * Wait until you have one BACKUP and one MASTER * Test connection with: nc -vz LB_FIP 80 [Regression Potential] While new failovers have been proven to work properly, this will resolve existing failed failovers which will require setting the LB state from PENDING_UPDATE to ERROR in the database prior to triggering a new failover. ------------------------------------------------------------------------ Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked.
2020-10-16 16:53:34 Edward Hope-Morley tags sts-sru-needed
2020-10-19 19:40:49 Corey Bryant octavia (Ubuntu Focal): status New Triaged
2020-10-19 19:40:52 Corey Bryant cloud-archive/ussuri: status New Triaged
2020-10-19 19:40:54 Corey Bryant cloud-archive/train: status New Triaged
2020-10-19 19:40:58 Corey Bryant cloud-archive/train: importance Undecided High
2020-10-19 19:41:00 Corey Bryant cloud-archive/ussuri: importance Undecided High
2020-10-19 19:41:04 Corey Bryant octavia (Ubuntu Focal): importance Undecided High
2020-11-09 14:33:34 Edward Hope-Morley cloud-archive/ussuri: status Triaged Fix Released
2020-11-09 14:33:36 Edward Hope-Morley cloud-archive/train: status Triaged Fix Released
2020-11-09 14:33:42 Edward Hope-Morley octavia (Ubuntu Focal): status Triaged Fix Released