Red Hat Bugzilla – Bug 966117
[RFE] engine: after several vdsm restart on spm we continue to select the host as spm if it's priority is high
Last modified: 2015-01-24 05:52:09 EST
Created attachment 751733 [details]
Description of problem:
In a 3 hosts cluster, I have 1 host which has SPM priority as high and 2 other hosts with SPM priority as low.
I ran some tests in which I restarted vdsm several times on the spm within 1 hour and but I see that when the host has spm priority high we will never move the spm to a different host.
seems to me that if a host which has spm priority high has several vdsm restarts in one hour we should probably select a different host as spm and alert the user in event log.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. in a 3 hosts cluster select the spm as priority high and the two other hosts as spm priority low.
2. restart the vdsm several times
we keep selecting the same host as spm because it has spm priority high
if vdsm restarted several times with in 1 hour on the host, even if its priority high, we should select a different host as SPM.
Additional info: engine and host logs.
this is an RFE imo, not a bug.
as the spm selection/priority is currently handled by infra - we should decide whether we leave it under storage.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.