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

Check for fenced volumes #437

Closed
wimpers opened this issue Feb 20, 2018 · 2 comments
Closed

Check for fenced volumes #437

wimpers opened this issue Feb 20, 2018 · 2 comments
Assignees
@JeffreyDevloo
Labels
priority_critical type_enhancement
Milestone
K

Comments

@wimpers
Copy link

wimpers commented Feb 20, 2018

The HC now reports fenced volumes also as halted, this ticket is to make a distinction between fenced and halted local volumes.

https://docs.google.com/document/d/1JLli7g1Abri8O5mJkbg6lAD5CG8QLBOL60I25B1hVtc/
@wimpers wimpers added this to the K milestone Feb 20, 2018
@redlicha
Copy link
Member

There's no difference between "fenced" and "halted" volumes: halted is a volume state that is entered after a non-recoverable error is encountered, and one of these is if a volume instance is fenced. The reason for entering the halted state is emitted as an event via AMQP / RabbitMQ so that is one indication. Another indication for fencing is if the volume is actually owned by another node / running there (the ObjectRegistry can provide that info).

@JeffreyDevloo
Copy link
Contributor

Fixed by #439
Released in https://github.com/openvstorage/openvstorage-health-check/releases/tag/3.4.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffreyDevloo JeffreyDevloo

Labels
priority_critical type_enhancement
Projects
None yet
Milestone
K
Development

No branches or pull requests
3 participants
@redlicha @wimpers @JeffreyDevloo