Bug 1773676
| Summary: | [IPI on Azure] [Azure CI] New cluster installations are failing on Destroying the bootstrap resources step | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Etienne Simard <esimard> |
| Component: | Installer | Assignee: | Abhinav Dahiya <adahiya> |
| Installer sub component: | openshift-installer | QA Contact: | Johnny Liu <jialiu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | anusaxen, jialiu, mifiedle, wsun |
| Version: | 4.3.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-04 11:15:36 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: | |||
|
Comment 1
Anurag saxena
2019-11-18 22:52:12 UTC
Move to 4.4, if it doesn't recur we'll close this. Is this still happening? Hello Scott, My teammates and I confirm that we haven't seen the error since November. I think you can close this if you're able to confirm it also hasn't appeared in the CI logs after Indexing is finished (https://ci-search-ci-search-next.svc.ci.openshift.org/?search=&maxAge=336h&context=2&type=all) Now that the CI search portal is back to normal, I confirmed that we haven't seen the Azure errors in CI lately: https://ci-search-ci-search-next.svc.ci.openshift.org/?search=failed+to+destroy+using+Terraform&maxAge=336h&context=2&type=all 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-2020:0581 |