Bug 1918651: ingress operator doesn't report any error when one of router pods is not ready#677
Bug 1918651: ingress operator doesn't report any error when one of router pods is not ready#677brandisher wants to merge 2 commits intoopenshift:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
added
do-not-merge/work-in-progress
|
@brandisher: This pull request references Bugzilla bug 1918651, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@brandisher: This pull request references Bugzilla bug 1918651, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: brandisher The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
brandisher
force-pushed
the
BZ1918651
branch
2 times, most recently
from
2cf6e00 to
c0342d1
Compare
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
brandisher
force-pushed
the
BZ1918651
branch
from
e8a1102 to
68f7cd5
Compare
|
/retest |
brandisher
force-pushed
the
BZ1918651
branch
2 times, most recently
from
51050fb to
6ef89c5
Compare
Add computeDeploymentProgressingCondition This function is intended to compute the associated Deployments's progressing condition.
brandisher
force-pushed
the
BZ1918651
branch
from
6ef89c5 to
36eb7c2
Compare
|
/test e2e-aws |
This adds a function to search through the IngressControllers to determine if there are any with a "Progressing" condition. Additionally, this commit modifies the progressing calculation of the operator to include the status of the ICs when determining whether or not the operator is in a Progressing state.
brandisher
force-pushed
the
BZ1918651
branch
from
36eb7c2 to
f0a2b3b
Compare
|
/retest-required |
|
/retest e2e-aws-single-node |
|
@brandisher: The
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test e2e-aws-single-node |
|
Rerunning this one more time as there were some registry issues at the time of the last run. /test e2e-aws-single-node |
|
Random container build failures /test e2e-aws-single-node |
|
Trying one more time as there's several terraform related errors /test e2e-aws-single-node |
|
Closing this out as this is fixed in OCP 4.9+ |
|
@brandisher: This pull request references Bugzilla bug 1918651. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
3 participants
Issue 1: The cluster-ingress-operator reports Available: true and Progressing: false even when the number of defined in ingresscontroller/default.spec.replicas are not all available (e.g. 1/2 replicas available).
Issue 2: The cluster-ingress-operator reports Available: true and Progressing: false even when the ingresscontroller deployment reports Progressing: true.