Skip to content
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

Uninstall never completes because it can't delete AMI #1339

Closed
csrwng opened this issue Feb 28, 2019 · 3 comments
Closed

Uninstall never completes because it can't delete AMI #1339

csrwng opened this issue Feb 28, 2019 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. platform/aws

Comments

@csrwng
Copy link
Contributor

csrwng commented Feb 28, 2019

Version

$ openshift-install version
openshift-install unreleased-master-457-g9596c7ffa001989c5453d8aff334f464b05c7a4d

Platform (aws|libvirt|openstack):

aws

What happened?

openshift-install destroy cluster never completes due to:

time="2019-02-28T16:36:25Z" level=debug msg="search for and delete matching resources by tag in us-east-1 matching aws.Filter{\"kubernetes.io/cluster/c3d1b23c-9718-40a5-p8tfs\":\"owned\"}"
time="2019-02-28T16:36:25Z" level=debug msg="deleting arn:aws:ec2:us-east-1:460538899914:image/ami-0f0b3ee1921278ed0: unrecognized EC2 resource type image"

What you expected to happen?

The cluster destroy to complete successfully

How to reproduce it (as minimally and precisely as possible)?

$ openshift-install destroy cluster

Anything else we need to know?

Introduced with
#1296

@dgoodwin
Copy link
Contributor

@abhinavdahiya bit of a blocker on hive side, our CI can't pass if uninstall fails.

@wking wking added kind/bug Categorizes issue or PR as related to a bug. platform/aws labels Feb 28, 2019
@wking
Copy link
Member

wking commented Feb 28, 2019

Fixed with #1340 (replacing a destroy failure with a pre-check failure, which is at least more convenient to clean up).

/close

@openshift-ci-robot
Copy link
Contributor

@wking: Closing this issue.

In response to this:

Fixed with #1340 (replacing a destroy failure with a pre-check failure, which is at least more convenient to clean up).

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. platform/aws
Projects
None yet
Development

No branches or pull requests

4 participants