Bug 851151
Summary: | [LOG] sanlock error: "ReleaseHostIdFailure: Cannot release host id" when vdsm service is restarted during async task | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Haim <hateya> | ||||
Component: | vdsm | Assignee: | Sergey Gotliv <sgotliv> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Haim <hateya> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | unspecified | CC: | abaron, amureini, bazulay, fsimonce, hateya, iheim, jkt, lpeer, sgotliv, yeylon | ||||
Target Milestone: | --- | ||||||
Target Release: | 3.3.0 | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | storage | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-01-09 18:24:26 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Haim
2012-08-23 11:32:18 UTC
Created attachment 606514 [details]
vdsm log
For what I see the problem is that HSM.prepareForShutdown() doesn't include an explicit stopSpm call. The domainMonitor tries to release the lockspace but it fails since the SPM resource is still in use. With safelease the HSM.__releaseLocks() (called in the prepareForShutdown flow) does something really similar to stopSpm. Fede, does this still happen? (In reply to comment #8) > Fede, does this still happen? Yes. At the moment this message indicates that the vdsm service has been restarted without stopping the SPM first (safe anyway since sanlock will notice that the process has gone away and release it). In the future (when the volume leases will be used) this message might become more frequent (on HSMs too) and we might want to find a way to silence it. still relevant with planned changes to spm? |