Bug 2005964 - After migration from OVS to OVN, octavia LB is in error state & new LB creation fails with octavia.amphorae.driver_exceptions.exceptions.TimeOutException
Summary: After migration from OVS to OVN, octavia LB is in error state & new LB creati...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia
Version: 16.1 (Train)
Hardware: All
OS: All
urgent
urgent
Target Milestone: z8
: 16.1 (Train on RHEL 8.2)
Assignee: Jakub Libosvar
QA Contact: Bruna Bonguardo
URL:
Whiteboard:
Depends On:
Blocks: 2019745
TreeView+ depends on / blocked
 
Reported: 2021-09-20 14:55 UTC by Rohini Diwakar
Modified: 2024-12-20 21:07 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-30 20:17:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2006417 1 unspecified CLOSED [Docs] emphasize that OVN --> OVS migration with iptables_hybrid firewall is not supported 2022-08-08 15:34:11 UTC
Red Hat Bugzilla 2006431 1 unspecified CLOSED [Docs] OVS-->OVN migration logging: tell customer to direct output of migration script to a file 2022-08-08 15:34:24 UTC
Red Hat Issue Tracker OSP-9746 0 None None None 2021-11-15 07:50:03 UTC

Description Rohini Diwakar 2021-09-20 14:55:38 UTC
Description of problem:
After completing the migration from OVS to OVN, observed some issues with our octavia. 
The loadbalancers that where present before the migration are now on error state.
Also, unable to create new loadbalancers.
It looks like the loadbalancer management network is having issues.
On the 3 controllers, we see the interface o-hm0, but we we can not attach to a amphora instance with ssh in this network (this was possible before the migration).

ERROR: 
+++
2021-09-20 14:20:43.141 85 ERROR octavia.controller.worker.v1.tasks.amphora_driver_tasks [-] Amphora compute instance failed to become reachable. This either means the compute driver failed to fully boot the ins
tance inside the timeout interval or the instance is not reachable via the lb-mgmt-net.: octavia.amphorae.driver_exceptions.exceptions.TimeOutException: contacting the amphora timed out
+++

Tried the lodbalancer failover. A new amphora instance is then spawned, but since there is no connectivity to the loadbalancer mgmt network, the failover fails.


Version-Release number of selected component (if applicable):
RHOSP16.1

Steps to Reproduce:
1. Create LB
2. Migrate from OVS to OVN
3.


Note You need to log in before you can comment on or make changes to this bug.