Status: New
Owner: ----

New issue 1165 by [email protected]: gnt-cluster doesn't detect "unknown" disks as drbd failed
https://code.google.com/p/ganeti/issues/detail?id=1165

What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".

Software version: 2.12.4
Internode protocol: 2120000
Configuration format: 2120000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.12.4

gnt-cluster (ganeti v2.12.4) 2.12.4

hspace (ganeti) version v2.12.4
compiled with ghc 7.6
running on linux x86_64


What distribution are you using?

debian jessie

What steps will reproduce the problem?
1. server1 with instance a primary, server2 with instance a secondary
2. reboot server2
3. after reboot sometimes on server2 - drbd state for disk of instance a is UpToDate/UpToDate, but on server1 state is:


 9: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r---b-

4. gnt-cluster verify-disk doesn't detect that as a problem, and doesn't fix that. gnt-instance activate-disk a - fix problem correctly.

What is the expected output? What do you see instead?

gnt-cluster activate-disk should detect that problem and fix it.

Please provide any additional information below.

I think problem is that unknown state is not recognized as problem. in:
lib/backend.py problematic are states: stats.is_standalone or stats.is_diskless.

I think there should be added additional state stats.is_unknown which should point problem when state is Unknown

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply via email to