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

[platform] Unable to reuse On-premise instance incase previouse universe failed / deleted #6758

Closed
jaydeepkumara opened this issue Dec 29, 2020 · 2 comments · Fixed by #6970
Assignees
Labels
area/platform Yugabyte Platform team/platform-hi Tickets handled by HashedIn team

Comments

@jaydeepkumara
Copy link
Contributor

Steps:-

  1. Configure On-premise provider
  2. Create the universe.
  3. Delete the previously created universe.
  4. Goto On-premise provider manage instance page, the previous instance will have the universe as n/a and it not allowed to delete.
  5. Goto create Universe, The previous instance is not appearing while creating.

Manage instance screenshot, after deleting universe, Delete is disabled for unattched intance

Screenshot from 2020-12-29 20-24-00

Availability zone is not appearing even if one instance is not attached to any universe.

Screenshot from 2020-12-29 20-26-44

@jaydeepkumara jaydeepkumara added the area/platform Yugabyte Platform label Dec 29, 2020
@jaydeepkumara jaydeepkumara changed the title [platform] Unable to reuse on promise instance incase previouse universe failed / deleted [platform] Unable to reuse On-premise instance incase previouse universe failed / deleted Dec 29, 2020
@jaydeepkumara jaydeepkumara added the team/platform-hi Tickets handled by HashedIn team label Dec 30, 2020
mahendranbhat added a commit that referenced this issue Feb 16, 2021
…ete. (#6970)

Summary:
Once we delete the on-premise universe, we have to clear the node instance so that we can use the node to create another universe.

Testing:
1. Add instance under on-premise
2. Created the universe with the instance ( should get failed)
3. Delete the universe.
4. Used the same instance to create another universe. ( should be possible after the change )

Reviewed by: Sergey Potachev
polarweasel pushed a commit to lizayugabyte/yugabyte-db that referenced this issue Mar 9, 2021
… got delete. (yugabyte#6970)

Summary:
Once we delete the on-premise universe, we have to clear the node instance so that we can use the node to create another universe.

Testing:
1. Add instance under on-premise
2. Created the universe with the instance ( should get failed)
3. Delete the universe.
4. Used the same instance to create another universe. ( should be possible after the change )

Reviewed by: Sergey Potachev
@mahendranbhat
Copy link
Contributor

#8263
2.4 backport PR

mahendranbhat added a commit that referenced this issue May 4, 2021
…e universe failed / deleted (#8263)

Description: Once we delete the onpremis universe, we have to clear the node instance so that we can use the node instance to create another universe.

Testing:
Added instance under onpremis
Created the universe with the instance. ( should get failed )
Delete the universe.
Used the same instance to create another universe.
Did the testing in master branch and in local master branch.
Local branch compilation and test cases ran successfully.
The change is not affecting anything else.

Reviewers: Arnav, Sergey
Reviewed by: Arnav
@mahendranbhat
Copy link
Contributor

Backported to 2.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform Yugabyte Platform team/platform-hi Tickets handled by HashedIn team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants