Description of problem: As of the time of this report, this test is in the top 3 flakes. https://testgrid.k8s.io/redhat-openshift-release-informing#redhat-canary-openshift-ocp-installer-e2e-azure-4.2&sort-by-flakiness Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
seems it is also failing heavily on GCP https://testgrid.k8s.io/redhat-openshift-release-informing#redhat-canary-openshift-ocp-installer-e2e-gcp-4.2&sort-by-flakiness
Looks like a duplicate of bug 1743728: The DNS provider failed to ensure the record: failed to update dns a record: *.apps.ci-op-xq7nkb8s-282fe.ci.azure.devcluster.openshift.com: dns.RecordSetsClient#CreateOrUpdate: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client '80fc851c-f9e3-41c2-87f2-3a05358d85f7' with object id '80fc851c-f9e3-41c2-87f2-3a05358d85f7' does not have authorization to perform action 'Microsoft.Network/dnsZones/A/write' over scope '/subscriptions/d38f1e38-4bed-438e-b227-833f997adf6a/resourceGroups/os4-common/providers/Microsoft.Network/dnsZones/ci.azure.devcluster.openshift.com/A/*.apps.ci-op-xq7nkb8s-282fe' or the scope is invalid. If access was recently granted, please refresh your credentials." However, as the the test is superfluous, removing it is a reasonable solution.
We believe this was solved by https://github.com/openshift/origin/pull/23688. Let's open new bugs as necessary.
checked testgrid and it passed in recent ci job, so moving to verified. https://testgrid.k8s.io/redhat-openshift-release-informing#redhat-canary-openshift-ocp-installer-e2e-azure-4.2&sort-by-flakiness=
This test is still flaky in e2e-azure and is one of our flakiest tests. Do I need to open another BZ to get this fixed?
Let's not re-open this bug.
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, 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/RHBA-2019:2922