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

Provide the option to rollback to previous main.tf configuration when a build error happens #118

Open
cmd-ntrf opened this issue Apr 25, 2024 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@cmd-ntrf
Copy link
Member

A user tried to change the instance type from c2-7.5gb-31-avx2 to g1-8gb-c4-22gb. This triggered on Terraform side the following error:

Error: Error waiting for instance (80f2fbd3-57ea-4426-a51b-0b7dfaf1bb71) to resize: unexpected state 'ACTIVE', wanted target 'VERIFY_RESIZE'. last error: %!s(<nil>)

which indicates that OpenStack is unable to migrate the c2 instance to a g1 instance.

While I don't think it would have been possible to completely prevent the user from trying to migrate. MC-Hub could have done better on two aspects:

  1. It should have reported the entire error message so the user would have had a better idea of what was happening.
  2. MC-Hub should have provided the ability to the user to rollback its configuration to the most recent one that was built correctly.

As it is currently implemented, after the user press the apply button, the configuration that triggered a build error is saved in the database and the preceding one cannot be recovered. This leaves the user will only one choice to remember what the previous configuration was and try to fix it manually by trial and error.

@cmd-ntrf cmd-ntrf added bug Something isn't working enhancement New feature or request labels Apr 25, 2024
@cmd-ntrf cmd-ntrf self-assigned this Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant