Description of problem:
Today we can manually fence a host in RHEVM. What it actually does is clear the SPM last holder written in the master meta-data.
If a user is doing a manual fence on host which is not really down we get into a situation in which some host is maintaining the lease on the SPM on one hand but the storage meta-data does not indicate who is that host.
When a host renew the lease update the master meta-data and by that avoid a inconsistent state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actually what should be is that the MD won't contain this information at all, only the lease itself.
When querying for this information, vdsm will obtain it by reading the lease.
This is the right way to do it, but it would require a major change in RHEVM though.
Why does it require a major change in RHEVM?
If SPMStatus will get the SPM information from the lease as you suggested instead of the MD it will be transparent to RHEVM. Or am i missing something?
(In reply to comment #2)
> Why does it require a major change in RHEVM?
> If SPMStatus will get the SPM information from the lease as you suggested
> instead of the MD it will be transparent to RHEVM. Or am i missing something?
Because there won't be a way to "zero" out the values as there is today without REALLY scsi fencing the node.
This means that the logic in RHEVM will have to change in this regard.
IMO that's a good thing.
Actually what i understand from it is that RHEVM won't need to go to the storage for manual fencing at all.
All we have to do is reset the SPM internally.
(In reply to comment #4)
> IMO that's a good thing.
> Actually what i understand from it is that RHEVM won't need to go to the
> storage for manual fencing at all.
> All we have to do is reset the SPM internally.
That's not the right logic, but let's discuss this at length when we get to implementing this.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.