Skip to content

Updated README.md with instructions how to clean conflicting IAM profiles #1124

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.

Sign up for GitHub

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

Closed
ekuric wants to merge 1 commit into from
Closed

Updated README.md with instructions how to clean conflicting IAM profiles #1124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,3 +53,26 @@ openshift-install destroy cluster
Note that you almost certainly also want to clean up the installer state files too, including `auth/`, `terraform.tfstate`, etc.
The best thing to do is always pass the `--dir` argument to `install` and `destroy`.
And if you want to reinstall from scratch, `rm -rf` the asset directory beforehand.


### Troubleshouting installation
Copy link
Member

@wking wking Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't belong in the project README. We have a platform-agnostic troubleshooting doc in docs/user/troubleshooting.md (already linked from the project README), and AWS-specific troubleshooting docs should go in a new docs/user/aws/troubleshooting.md (like our existing docs/user/openstack/troubleshooting.md).

Copy link
Author

@ekuric ekuric Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can send it there if this is not best place ... ?


```Cleanup``` step *should* tear down everything created during the previous installation, however sometimes the installer may report error messages like the ones below:
Copy link
Member

@wking wking Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide steps to reproduce? I'd much rather fix this bug (if it still exists) than document workarounds.

Copy link
Author

@ekuric ekuric Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wking either destroy step was interrupted, or stopped due to network issue, but I do not have clear reproducer. When I wanted to install new cluster it was not possible due to error described here, but possible after applying fix described here ... thanks to @dobbymoodge for suggestions

Copy link
Member

@wking wking Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... either destroy step was interrupted, or stopped due to network issue...

There are lots of ways this could go wrong. The most reliable approach to cleaning it up should be to re-launch destroy. Can you post logs showing that a fresh destroy call failed to delete the profile or other resource? I'm not even clear on how you were able to run a new create cluster without having previously had a successful destroy cluster on the previous cluster. What version of the installer were you running? 0.10.1 has #1039, with some destroy cluster fixes.

Copy link
Author

@ekuric ekuric Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q: Can you post logs showing that a fresh destroy call failed to delete the profile or other resource?
a: unfortunately I do not have it.
prior to every install I do git pull, ./hack/build.sh - so I was on latest.


```
ERROR Error: Error applying plan:
ERROR
ERROR 3 errors occurred:
ERROR * module.bootstrap.aws_iam_instance_profile.bootstrap: 1 error occurred:
ERROR * aws_iam_instance_profile.bootstrap: Error creating IAM instance profile test-bootstrap-profile:

FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply using Terraform
```
This happens when the installer tries to create an IAM instance profile with a name that matches an existing instance profile. This usually means that IAM instance profiles from a previous installation by the user didn't get deleted during an earlier cluster teardown.

To fix this problem it is necessary to delete conflicting IAM profiles and retry.
To delete problematic IAM profiles follow [list-instance-profiles](https://docs.aws.amazon.com/cli/latest/reference/iam/list-instance-profiles.html) and [delete-instance-profile](https://docs.aws.amazon.com/cli/latest/reference/iam/delete-instance-profile.html) which can be summarized to
```
$ aws iam list-instance-profiles | grep USER
$ aws iam delete-instance-profile --instance-profile-name PROFILE_NAME
```