Bug 2003655 - [IPI ON-PREM] Keepalived chk_default_ingress track script failed even though default router pod runs on node
Summary: [IPI ON-PREM] Keepalived chk_default_ingress track script failed even though ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Yossi Boaron
QA Contact: Silvia Serafini
Depends On:
Blocks: 2013164
TreeView+ depends on / blocked
Reported: 2021-09-13 11:55 UTC by Yossi Boaron
Modified: 2022-06-30 08:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:09:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2761 0 None open Bug 2003655: [IPI ON-PREM] move Keepalived default ingress script to separate file 2021-09-14 13:58:27 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:09:51 UTC

Description Yossi Boaron 2021-09-13 11:55:12 UTC
Description of problem:

Keepalived chk_default_ingress track script [1] should succeed at nodes running an instance of default router pod. 

But Keepalived logs (from a node running default router pod instance) shows that chk_default_ingress track script failed [2].

As a result of this issue, Ingress VIP may be mistakenly assigned with a wrong node in case multiple ingress controllers run in the cluster.

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

[kni@worker-0 dev-scripts]$ oc version 
Client Version: 4.9.0-0.nightly-2021-08-28-220206

How reproducible:

Steps to Reproduce:
1. Deploy cluster
2. Check which nodes run an instance of default router pod (you can use [3] command) 
3. ssh into one of nods from step 2
4. Check Keepalived container logs 

Actual results:
chk_default_ingress track script failed 

Expected results:
chk_default_ingress track script should succeed

Additional info:


Mon Sep 13 11:27:48 2021: Script `chk_default_ingress` now returning 1
Mon Sep 13 11:27:48 2021: VRRP_Script(chk_default_ingress) failed (exited with status 1)


$ oc get pods -n openshift-ingress -o wide 
NAME                             READY   STATUS    RESTARTS   AGE   IP               NODE       NOMINATED NODE   READINESS GATES
router-default-6548d747b-6cw9f   1/1     Running   4          8d   worker-0   <none>           <none>
router-default-6548d747b-pjrw5   1/1     Running   0          8d   worker-1   <none>           <none>
[kni@worker-0 dev-scripts]$

Comment 10 errata-xmlrpc 2022-03-10 16:09:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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