Bug 1110172 – [RFE]API to check if a host has renew its lease

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1110172 - [RFE]API to check if a host has renew its lease

Summary:	[RFE]API to check if a host has renew its lease

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	RFEs (Show other bugs)
Sub Component:
Version:	3.5.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	3.5.0
Assigned To:	Nir Soffer
QA Contact:	sefi litmanovich
Docs Contact:

URL:
Whiteboard:	storage
Keywords:	FutureFeature

Depends On:	1058022
Blocks:	1110176 1119922 rhev3.5beta 1156165
	Show dependency tree / graph

Reported:	2014-06-17 03:49 EDT by Sean Cohen
Modified:	2016-02-10 15:22 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	v4.16.2
Doc Type:	Enhancement
Doc Text:	Previously, during fencing, a host cannot be accessed through the network and administrators could not check if the host was working or not. With this update, the host can be checked using the Sanlock lease information. Now, hosts can be checked even during fencing.
Story Points:	---
Clone Of:
Clones:	1119922 (view as bug list)
Environment:
Last Closed:	2015-02-11 13:03:50 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	scohen: needinfo+ scohen: needinfo+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	28873	master	MERGED	fencing: Introduce getHostLeaseStatus API	Never
oVirt gerrit	31148	ovirt-3.5	MERGED	fencing: Introduce getHostLeaseStatus API	Never
Red Hat Product Errata	RHSA-2015:0158	normal	SHIPPED_LIVE	Important: Red Hat Enterprise Virtualization Manager 3.5.0	2015-02-11 17:38:50 EST

Groups: None (edit)

Description Sean Cohen 2014-06-17 03:49:34 EDT

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:

Comment 1 Allon Mureinik 2014-06-17 03:56:31 EDT

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.

Comment 2 Allon Mureinik 2014-06-17 11:32:30 EDT

Nir, please check if ClusterLock.hasHostId does the trick for us.

Comment 6 sefi litmanovich 2014-09-22 04:34:32 EDT

Verified with rhevm-3.5.0-0.12.beta.el6ev.noarch, vdsm-4.16.3-3.el7.beta.x86_64.

Comment 7 Julie 2015-02-01 20:49:57 EST

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 -.

Comment 9 errata-xmlrpc 2015-02-11 13:03:50 EST

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

Note You need to log in before you can comment on or make changes to this bug.