Bug 1793627
Summary: | gcp destroy cluster panics "nil pointer dereference" when deleting dns records | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jeremiah Stuever <jstuever> |
Component: | Installer | Assignee: | Jeremiah Stuever <jstuever> |
Installer sub component: | openshift-installer | QA Contact: | Yang Yang <yanyang> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | low | ||
Priority: | unspecified | ||
Version: | 4.4 | ||
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:25:48 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1788708 |
Description
Jeremiah Stuever
2020-01-21 17:24:23 UTC
This appears to be happening when destroy identifies DNS records to be deleted from a zone, but the records are deleted by something else before destroy actually deletes them. Verified with 4.4.0-0.nightly-2020-02-12-004057 Steps for verification are as below: 1, Create an IPI cluster on GCP 2, Delete 1 record set manually 3, Destroy the cluster DEBUG Listing DNS Zones DEBUG Found cluster private dns zone: yybz1-zfzvk-private-zone DEBUG Found parent dns zone: qe DEBUG Deleting 1 recordset(s) in zone qe INFO Deleted 1 recordset(s) in zone qe DEBUG Deleting 6 recordset(s) in zone yybz1-zfzvk-private-zone INFO Deleted 6 recordset(s) in zone yybz1-zfzvk-private-zone DEBUG Deleting DNS zones yybz1-zfzvk-private-zone INFO Deleted DNS zone yybz1-zfzvk-private-zone Installer is not panic hence moving it to verified state. 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 |