Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: 4.12.z
Component/s: Networking / router
Labels:

Severity:
Important
Regression:
No
Story Points:
12
Sprint:
Sprint 254, NE Sprint 255, NE Sprint 256
sprint_count:
3
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Customer Impact:

Customer Escalated

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:
PX Priority Data:

Description of problem:

    Ingress Operator always remain in the progressing state

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

    4.12.40

How reproducible:

    Always in customer enviornment

Summary:

The cluster operator ingress always remains in the progressing state with the message that current replicas doesn't match to the desired replicas. However, the when checking number of pods in openshift-ingress it matches the number of replicas defined in ingresscontroller.

Adding more details in the comment section.

is caused by

OCPBUGS-34757 [4.12] Ingress Operator is needlessly reverting default values in Internal Services

Closed

OCPBUGS-34110 [Backport 4.12] The ingress-operator spuriously updates ingressClass on startup

Closed

OCPBUGS-34888 [Backport 4.12] Ingress operator performs spurious updates in response to API's defaulting of router deployment's router container's ports' hostPort field when using HostNetwork

Closed

OCPBUGS-35027 [Backport 4.12] Ingress operator attempts spurious deletes of the client CA configmap when deleting an IngressController that has a client TLS configured

Closed

OCPBUGS-35304 [Backport 4.12] TestHostNetworkPort is half serial and half parallel

Closed

Assignee:: Candace Holman

Reporter:: Himank Chaturvedi

QA Contact:: Shudi Li

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 2024/05/14 4:18 PM

Updated:: 2024/07/03 5:30 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates