Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is required as part of the fencing improvements. Need to coordinate with the infra team on what would serve their needs better, but there are two options here (run from the fencing proxy): 1. Change fenceNode's signature and add a parameter requiredStorages={}, so that the fencing will only happen if the node is not renewing its lease on the given domains. 2. Add a new API call doesNodeRenewLease(nodeDetails, storageDomains) to return boolean if the lease(s) is(are) being maintained.
Nir, please check if ClusterLock.hasHostId does the trick for us.
Verified with rhevm-3.5.0-0.12.beta.el6ev.noarch, vdsm-4.16.3-3.el7.beta.x86_64.
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format: Cause: Consequence: Fix: Result: The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html