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.

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

Jump to bottom

[Platform] Edit Universe fails silently in case when it has decommissioned node(s) #6421

Closed
SergeyPotachev opened this issue Nov 19, 2020 · 1 comment
Closed

[Platform] Edit Universe fails silently in case when it has decommissioned node(s) #6421

SergeyPotachev opened this issue Nov 19, 2020 · 1 comment
Assignees
@gaurav061
Labels
area/platform Yugabyte Platform team/platform-hi Tickets handled by HashedIn team

Comments

@SergeyPotachev
Copy link
Contributor

Steps to reproduce:

  1. Create universe with 4 nodes in 3 AZs and RF=3.
  2. Remove node with tserver only in zone with two nodes.
  3. Do 'Release Instance' for the same node.
    This node now is in the Decommissioned state.
  4. Start the Edit Universe procedure. Add node in another AZ (where is only one node exists).
  5. Press save.

Expected result: the update should start or it should show an error message.
Actual result: Nothing happens. There is only a message in YW logs:

Hit error 400, message: {"error":"Cannot perform an edit operation on universe 72037945-837c-430d-93d0-a6705cbfd73b as it has nodes in one of [Removed, Stopped, Decommissioned] states."}
@SergeyPotachev SergeyPotachev added the area/platform Yugabyte Platform label Nov 19, 2020
@streddy-yb streddy-yb added the good first issue This is a good issue to start contributing! label Nov 30, 2020
@streddy-yb streddy-yb added the team/platform-hi Tickets handled by HashedIn team label Jan 5, 2021
@streddy-yb streddy-yb removed the good first issue This is a good issue to start contributing! label Jan 27, 2021
gaurav061 added a commit to jaydeepkumara/yugabyte-db that referenced this issue Feb 18, 2021
@gaurav061
fixed comments and added fix for yugabyte#6421
7071dad
@gaurav061
Copy link
Contributor

PR: #7078
Fix: Exact scenario wasn't reproduced however I handled the error by showing
visual feedback in case of edit-universe submit.

gaurav061 added a commit that referenced this issue Feb 19, 2021
@gaurav061
[#6346, #6477, #6421] Platform: Implemented toaster component for vis…
f1f0218 
…ual feedback (#7078)

Description: Added toaster for having visual feedback for user action.
cases covered:
1. When the user adds/delete the KMS configuration.
2. When duplicate region code is added for on-prem Provider.
3. Api error response in case of edit universe.

Test scenario:
- Adding duplicate region code for the on-prem provider notifies the user of an appropriate toaster.
-  Adding/Deleting the KMS have visual feedback to the users.
- Any error encountered during edit universe have visual feedback
polarweasel pushed a commit to lizayugabyte/yugabyte-db that referenced this issue Mar 9, 2021
@gaurav061
[yugabyte#6346, yugabyte#6477, yugabyte#6421] Platform: Implemented t…
6e07ea1 
…oaster component for visual feedback (yugabyte#7078)

Description: Added toaster for having visual feedback for user action.
cases covered:
1. When the user adds/delete the KMS configuration.
2. When duplicate region code is added for on-prem Provider.
3. Api error response in case of edit universe.

Test scenario:
- Adding duplicate region code for the on-prem provider notifies the user of an appropriate toaster.
-  Adding/Deleting the KMS have visual feedback to the users.
- Any error encountered during edit universe have visual feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaurav061 gaurav061

Labels
area/platform Yugabyte Platform team/platform-hi Tickets handled by HashedIn team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jaydeepkumara @gaurav061 @streddy-yb @SergeyPotachev