Bug 2116364 - IPfailover pod installation in OVN requires 'br-ex' interface to be added to keepalived-ipfailover configuration script
Summary: IPfailover pod installation in OVN requires 'br-ex' interface to be added to ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: aos-network-edge-staff
QA Contact: Melvin Joseph
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-08 11:46 UTC by Melvin Joseph
Modified: 2022-12-19 21:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-19 21:14:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Melvin Joseph 2022-08-08 11:46:29 UTC
Description of problem:
During the IPFailover pod installation in OVN cluster, it is noted the POD are not in `CrashLoopBackOff` state, and further investigation reveal the mis-configuration of the HA Network interface. Presently 'br-ex' interface is not included in the configuration script

If the 'br-ex' interface is added to `VBOX_INTERFACES="enp0s3 enp0s8 eth1 ens3"` in the configuration file, this can be rectified. 
This change will be impact on the automation as from 4.12 OVN will be the default network type.  

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

Cluster Platform:
open stack IPI

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Melvin Joseph 2022-08-08 11:47:59 UTC
Similar issue which was fixed 
https://bugzilla.redhat.com/show_bug.cgi?id=2062126#c3

Comment 3 mfisher 2022-12-19 21:14:00 UTC
This issue is stale and has been closed because it has been open 90 days or more with no noted activity/comments in the last 60 days.  If this issue is crucial and still needs resolution, please open a new jira issue and the engineering team will triage and prioritize accordingly.


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