Bug 1886940
Summary: | CI tests on api.ci.openshift.com can timeout waiting for dns response | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jeremy Poulin <jpoulin> |
Component: | Multi-Arch | Assignee: | Deep Mistry <dmistry> |
Status: | CLOSED DUPLICATE | QA Contact: | Jeremy Poulin <jpoulin> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.6 | CC: | danili, dmistry, smilner |
Target Milestone: | --- | Keywords: | TestOnly |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
[sig-builds][Feature:Builds] oc new-app should succeed with a --name of 58 characters
|
|
Last Closed: | 2021-02-20 20:42:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeremy Poulin
2020-10-09 19:01:01 UTC
Hi @Deep, will this bug be resolved before the end of this sprint (Oct. 24th)? If not, can we add the "UpcomingSprint" tag? Hi Deep, will this bug be resolved by the end of this sprint (Nov 14th)? If not, can we add the "UpcomingSprint" label? Adding UpcomingSprint per Deep Hi Deep, will this bug be resolved before the end of this sprint (Dec 5th)? If not, can we add "UpcomingSprint"? Hi Deep, I am doing this exercise one week early because most people are out next week. 1. Do you think this bug will be resolved before the end of this sprint (December 26th)? If not, I'd like to add "UpcomingSprint" 2. Do you think this bug's Target Release is still 4.7.0? If it does not target 4.7, can we set it to blank value "---"? Lots of updates for this issue today: I was able to reproduce the issue in a live state. Debugging threads: https://coreos.slack.com/archives/C017UFPQA4X/p1609863078302400 https://coreos.slack.com/archives/CBN38N3MW/p1609864629064900 Based on the second thread listed above, our best bet is to update to one of the 4.x clusters set up for CI, since there is no way to resolve dns issues in the 3.11 cluster we currently run in. Since this is happening so close to the 4.7 release, I've notified CI stakeholders and plan to have this scheduled outage set up so that we can plan to have it post release of 4.7. In the meantime, I've instructed our teams to file patches to disable tests that rely on external networking in the 3.11 cluster. https://coreos.slack.com/archives/C017UFPQA4X/p1609866503321700 Hi Deep, do you think this bug will be resolved before the end of this sprint (Feb. 6th)? If not, can we set the "Reviewed-in-Sprint" flag to "+"? Closing this as duplicate of the networking instability bug, since both are tracking the cluster migration to 4.x. *** This bug has been marked as a duplicate of bug 1846875 *** |