2051333 – [aws] records in public hosted zone and BYO private hosted zone were not deleted.

Bug 2051333 - [aws] records in public hosted zone and BYO private hosted zone were not deleted.

Summary: [aws] records in public hosted zone and BYO private hosted zone were not dele...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer
Sub Component:
Version:	4.10
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	---
Target Release:	4.11.0
Assignee:	Nobody
QA Contact:	Yunfei Jiang
Docs Contact:
URL:
Whiteboard:
Depends On:	1965969
Blocks:
TreeView+	depends on / blocked

Reported:	2022-02-07 03:33 UTC by Yunfei Jiang
Modified:	2022-08-10 10:47 UTC (History)
CC List:	2 users (show)
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	I am marking this as no doc update. It is unclear from this particular bz what the actual issue is. Matthew declares that there this BZ is an issue with metadata in the destroy, but claims he cannot reproduce it, QE claims it works, and there is no BZ to fix. I think this BZ was part of a larger conversation of other BZs and is probably a duplicate. I don't think we're missing anything here if we don't include docs on this.
Clone Of:	1965969
Environment:
Last Closed:	2022-08-10 10:47:24 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2022:5069	0	None	None	None	2022-08-10 10:47:40 UTC

Comment 1 Yunfei Jiang 2022-02-07 03:35:48 UTC

see https://bugzilla.redhat.com/show_bug.cgi?id=1965969#c10
issues were introduced by https://github.com/openshift/installer/pull/5343 and https://github.com/openshift/installer/pull/5494

Comment 6 Matthew Staebler 2022-03-01 15:27:41 UTC

@yunjiang I have not been able to replicate this BZ. Were you using a metadata.json that you manually created? Could you provide full install logs and the metadata.json from a failed destroy.


~~~~
# Check records in private hosted zone after install.
$ aws route53 list-resource-record-sets --hosted-zone-id=Z0807045AKSEBSUFT40G --output=json | jq '.ResourceRecordSets[].Name' -r
mstaeble.devcluster.openshift.com.
mstaeble.devcluster.openshift.com.
api-int.mstaeble.devcluster.openshift.com.
api.mstaeble.devcluster.openshift.com.


# Check records in public hosted zone after install.
$ aws route53 list-resource-record-sets --hosted-zone-id=Z3URY6TWQ91KVV --output=json | jq '.ResourceRecordSets[].Name | select(contains("mstaeble"))' -r
api.mstaeble.devcluster.openshift.com.


# Destroy the cluster.
$ openshift-install destroy cluster
<snip>
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0807045AKSEBSUFT40G id=Z0807045AKSEBSUFT40G record set=A api-int.mstaeble.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0807045AKSEBSUFT40G id=/hostedzone/Z3URY6TWQ91KVV record set=A api.mstaeble.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0807045AKSEBSUFT40G id=Z0807045AKSEBSUFT40G record set=A api.mstaeble.devcluster.openshift.com.
INFO Cleaned record sets from hosted zone          arn=arn:aws:route53:::hostedzone/Z0807045AKSEBSUFT40G id=Z0807045AKSEBSUFT40G
<snip>


# Check records in private hosted zone after destroy.
$ aws route53 list-resource-record-sets --hosted-zone-id=Z0807045AKSEBSUFT40G --output=json | jq '.ResourceRecordSets[].Name' -r
mstaeble.devcluster.openshift.com.
mstaeble.devcluster.openshift.com.


# Check records in public hosted zone after destroy.
$ aws route53 list-resource-record-sets --hosted-zone-id=Z3URY6TWQ91KVV --output=json | jq '.ResourceRecordSets[].Name | select(contains("mstaeble"))' -r
~~~~

Comment 7 Matthew Staebler 2022-03-01 15:32:09 UTC

Forgot to include that the above was run using 4.10.0-rc.6.

Comment 8 Yunfei Jiang 2022-03-02 03:00:05 UTC

Staebler, you're right, all records were deleted successfully, using 4.10.0-rc.6.
I'm wondering is there any change between 4.10.0-0.nightly-2022-01-10-014106 (https://bugzilla.redhat.com/show_bug.cgi?id=1965969#c10) and 4.10.0-rc.6? b/c I got different results in these two versions.



## Records in private zone after install
> aws route53 list-resource-record-sets --hosted-zone-id=Z09075602HZ0U2U9F711E --output=json | jq '.ResourceRecordSets[].Name' -r
yunjiang-r53a.qe.devcluster.openshift.com.
yunjiang-r53a.qe.devcluster.openshift.com.
api-int.yunjiang-r53a.qe.devcluster.openshift.com.
api.yunjiang-r53a.qe.devcluster.openshift.com.
\052.apps.yunjiang-r53a.qe.devcluster.openshift.com.

## Records in public zone after install
> aws route53 list-resource-record-sets --hosted-zone-id=Z3B3KOVA3TRCWP --output=json | jq '.ResourceRecordSets[].Name | select(contains("yunjiang-r53a"))' -r
api.yunjiang-r53a.qe.devcluster.openshift.com.
\052.apps.yunjiang-r53a.qe.devcluster.openshift.com.


## Records in private zone after destroy
> aws route53 list-resource-record-sets --hosted-zone-id=Z09075602HZ0U2U9F711E --output=json | jq '.ResourceRecordSets[].Name' -r
yunjiang-r53a.qe.devcluster.openshift.com.
yunjiang-r53a.qe.devcluster.openshift.com.

## Records in public zone after destroy
> aws route53 list-resource-record-sets --hosted-zone-id=Z3B3KOVA3TRCWP --output=json | jq '.ResourceRecordSets[].Name | select(contains("yunjiang-r53a"))' -r
<nothing>

## destroy log
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E id=Z09075602HZ0U2U9F711E record set=A api-int.yunjiang-r53a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E id=/hostedzone/Z3B3KOVA3TRCWP record set=A api.yunjiang-r53a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E id=Z09075602HZ0U2U9F711E record set=A api.yunjiang-r53a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E id=/hostedzone/Z3B3KOVA3TRCWP record set=A \052.apps.yunjiang-r53a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E id=Z09075602HZ0U2U9F711E record set=A \052.apps.yunjiang-r53a.qe.devcluster.openshift.com.
INFO Cleaned record sets from hosted zone          arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E id=Z09075602HZ0U2U9F711E
INFO Removed tag kubernetes.io/cluster/yunjiang-r53a-gqf7r: shared  arn=arn:aws:route53:::hostedzone/Z09075602HZ0U2U9F711E
INFO Time elapsed: 4m12s

Comment 9 Yunfei Jiang 2022-03-21 04:16:27 UTC

verified against 4.11.0-0.nightly-2022-03-20-160505

INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6 id=Z0304524GTZJCIU9G9L6 record set=A api-int.yunjiang-bz33a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6 id=/hostedzone/Z3B3KOVA3TRCWP record set=A api.yunjiang-bz33a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6 id=Z0304524GTZJCIU9G9L6 record set=A api.yunjiang-bz33a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6 id=/hostedzone/Z3B3KOVA3TRCWP record set=A \052.apps.yunjiang-bz33a.qe.devcluster.openshift.com.
INFO Deleted                                       arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6 id=Z0304524GTZJCIU9G9L6 record set=A \052.apps.yunjiang-bz33a.qe.devcluster.openshift.com.
INFO Cleaned record sets from hosted zone          arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6 id=Z0304524GTZJCIU9G9L6
INFO Removed tag kubernetes.io/cluster/yunjiang-bz33a-7dwfv: shared  arn=arn:aws:route53:::hostedzone/Z0304524GTZJCIU9G9L6
INFO Time elapsed: 3m16s

Comment 14 errata-xmlrpc 2022-08-10 10:47:24 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069

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