Bug 2014710 - TestIngressStatus test is broken on Azure
Summary: TestIngressStatus test is broken on Azure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Miciah Dashiel Butler Masters
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks: 2014711
TreeView+ depends on / blocked
 
Reported: 2021-10-15 23:44 UTC by Miciah Dashiel Butler Masters
Modified: 2022-08-04 22:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-12 04:39:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 672 0 None open Bug 2014710: test/e2e: updateDNSConfig: Replace integer literals 2021-11-02 02:33:58 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:39:32 UTC

Description Miciah Dashiel Butler Masters 2021-10-15 23:44:14 UTC
Description of problem:

The recently added TestIngressStatus test fails on Azure, causing the e2e-azure-operator CI jobs in the cluster-ingress-operator repository to fail consistently.


OpenShift release version:

The test was added in OpenShift 4.9.  


Cluster Platform:

Azure.


How reproducible:

Consistently.


Steps to Reproduce (in detail):
1. Run the e2e-azure-operator CI job.  


Actual results:

The e2e-azure-operator CI job consistently fails.  See https://github.com/openshift/cluster-ingress-operator/pull/659#issuecomment-943881965 for an example failure.


Expected results:

The e2e-azure-operator CI job should pass.  


Impact of the problem:

The e2e-azure-operator CI job is broken, which prevents us from using it to validate PRs on Azure.


Additional info:

The new test was introduced in https://github.com/openshift/cluster-ingress-operator/pull/641.  A fix was posted in https://github.com/openshift/cluster-ingress-operator/pull/662 and has already merged into the master branch.  I am filing this Bugzilla report so that we will be able to link the PR to a Bugzilla report and then backport the fix to the release-4.9 branch.

Comment 2 Hongan Li 2021-10-18 07:41:13 UTC
the test e2e-azure-operator looks good, moving to verified.

Comment 3 Miciah Dashiel Butler Masters 2021-11-02 02:33:41 UTC
Changes were requested on the release-4.9 backport[1], so I am making those changes on the main branch and will open a new backport PR that incorporates those changes.  

1. https://github.com/openshift/cluster-ingress-operator/pull/664#pullrequestreview-793432926

Comment 7 errata-xmlrpc 2022-03-12 04:39:16 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.

https://access.redhat.com/errata/RHSA-2022:0056


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