-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When a dual-stack (IPv4 + IPv6) cluster is deployed on bare metal using the Agent-based Installer (ABI), a large number of router pods report NodePorts status. $ omc get pod -n openshift-ingress NAME READY STATUS RESTARTS AGE router-default-65749dbc77-22dqr 0/1 NodePorts 0 32m router-default-65749dbc77-25gdq 0/1 NodePorts 0 32m router-default-65749dbc77-25tcr 0/1 NodePorts 0 33m router-default-65749dbc77-272cd 0/1 NodePorts 0 31m router-default-65749dbc77-276db 0/1 NodePorts 0 27m router-default-65749dbc77-27shh 0/1 NodePorts 0 27m router-default-65749dbc77-285qw 0/1 NodePorts 0 32m router-default-65749dbc77-28z46 0/1 NodePorts 0 32m router-default-65749dbc77-29f7d 0/1 NodePorts 0 32m router-default-65749dbc77-2bgxq 0/1 NodePorts 0 33m : $ omc get pod -n openshift-ingress | wc -l 1787
Version-Release number of selected component (if applicable):
Red Hat OpenShift Container Platform 4.19.2
How reproducible:
Always
Steps to Reproduce:
1. Deploy a dual-stack cluster using Agent-based Installer
2. Confirm router pods status
3.
Actual results:
Many router pods are in NodePorts status
Expected results:
Router pods are working fine
Additional info:
This issue does not occur when the cluster is deployed in a virtual environment.
