-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Existing A record error #1562
Comments
That's not always the appropriate response. See rhbz#1659970 (fixed by #1442) for why we error out in this case. Your issue is almost certainly a failed/forgotten uninstall of an earlier cluster; have you been running |
Yep, that's my case. No doubt that it was my fault, but since we want to make the installer very accessible to our users, it might be worthwhile to point them some directions on how to solve common errors (if that's possible). #1452 looks very useful, perhaps we could have a pointer to it in the error message? |
I have the issue happening to me every time (openshift-dev us-east-2 account), running a "destroy cluster" |
Have you removed the leaked A record? You need to recover this manually after the buggy openshift-dev reaper partially removes the cluster. Running |
openshift-dev account should be cleaning them correctly, if the installer doesn't find the private zone, the public records cannot be delete for safety. /close |
@abhinavdahiya: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I am running into similar issue but I am unable to find my domain in Hosted zones list so I can not delete my Route53 record in AWS console. Am I looking into wrong dashboard? Never mind, I found it. I need to click the parent domain first and then I found it... |
Version
What happened?
I've seen this error occasionally:
Then I head to the AWS Console and delete the records manually.
I'm not sure how often this happen out there, but it might be worthwhile to parse this AWS error and print a more helpful message to the user.
Ideally, the message would instruct the user to delete the records manually and then proceed with the installation.
The text was updated successfully, but these errors were encountered: