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

Constellation cannot terminate IP resource on AWS #1886

Open
3u13r opened this issue Jun 6, 2023 · 0 comments
Open

Constellation cannot terminate IP resource on AWS #1886

3u13r opened this issue Jun 6, 2023 · 0 comments
Labels
known issue This is a known issue of the latest release

Comments

@3u13r
Copy link
Member

3u13r commented Jun 6, 2023

Issue description

When terminating a Constellation on AWS the constellation terminate outputs an error and does not fully clean up the Constellation. Only when running constellation terminate a second time, all resources are cleaned up.

To reproduce

Steps to reproduce the behavior:

  1. Create a Constellation on AWS
  2. Run constellation terminate
 euler@work:~/projects/constellation/test$ ./constellation terminate
You are about to terminate a Constellation cluster.
All of its associated resources will be DESTROYED.
This action is irreversible and ALL DATA WILL BE LOST.
Do you want to continue? [y/n]: y
Terminating
Error: terminating Constellation cluster: exit status 1
Error: deleting EC2 EIP (eipalloc-005f6369d2d588052): disassociating: AuthFailure: You do not have permission to access the specified resource.
    status code: 400, request id: fdc85569-0a89-4900-9631-bec0685479bc 

Environment

  • constellation version: 2.8.0

Expected behavior

The Constellation should be fully terminated without error.

Additional info / screenshot

To fully terminate your Constellation simply run constellation terminate again.
We are currently investigating this issue.

@3u13r 3u13r added the known issue This is a known issue of the latest release label Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
known issue This is a known issue of the latest release
Projects
None yet
Development

No branches or pull requests

1 participant