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

Pool is 'Healthy' when less than 3 nodes are healthy (2/4 are in migrating) #2729

Closed
jackyalbo opened this issue Feb 28, 2017 · 0 comments · Fixed by #2739
Closed

Pool is 'Healthy' when less than 3 nodes are healthy (2/4 are in migrating) #2729

jackyalbo opened this issue Feb 28, 2017 · 0 comments · Fixed by #2739
Assignees
@nimrod-becker
Labels
Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail

Comments

@jackyalbo
Copy link
Contributor

jackyalbo commented Feb 28, 2017 •
edited
Loading

Environment info

  • Version: 1.1.0-35ea489
  • Deployment: AZURE
  • Customer: QA

Actual behavior

  1. following previous bug Nodes stuck in migrating after moving nodes between pools and retuning to the original pool #2728 when 2/4 nodes are in 'has issues' mode
  2. the pool looks healthy - when it's not healthy and you can't write data to pool

Expected behavior

  1. status should be 'Not healthy' or 'Not enough healthy nodes'

Steps to reproduce

  1. make a pool with 3 nodes - take down one

Screenshots or Logs or other output that would be helpful

noobaa_management_console
@nimrod-becker nimrod-becker added Priority 2 High Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail labels Feb 28, 2017
@nimrod-becker nimrod-becker self-assigned this Feb 28, 2017
@nimrod-becker nimrod-becker mentioned this issue Mar 1, 2017
Merged
8 tasks
nimrod-becker added a commit that referenced this issue Mar 1, 2017
@nimrod-becker
fix for #2696 / #2729 - correct pool status on < 3 optimal nodes, add…
c9a8bb9 
… min server req in read_sys reply

FE add status for not_enough_nodes

Return minimal srv configuration (men, disk, cpu)
nimrod-becker added a commit that referenced this issue Mar 1, 2017
@nimrod-becker
fix for #2696 / #2729 - correct pool status on < 3 optimal nodes, add…
fc956dc 
… min server req in read_sys reply

FE add status for not_enough_nodes

Return minimal srv configuration (men, disk, cpu)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nimrod-becker nimrod-becker

Labels
Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail
Projects
None yet
Milestone
No milestone
2 participants
@nimrod-becker @jackyalbo