Bug 1091762 – Need to make a small change to sanlock documentation

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

Bug 1091762 - Need to make a small change to sanlock documentation

Summary:	Need to make a small change to sanlock documentation

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	rhev-docs@redhat.com
QA Contact:	ecs-bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-04-27 18:31 EDT by Jodi Biddle
Modified:	2014-11-09 17:29 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-08-25 01:57:16 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Jodi Biddle 2014-04-27 18:31:44 EDT

3.3 documentation, Chapter 19, sections 19.1.5, step 3 states:

"If a package such as the kernel was updated, you must reboot the host to get the new functionality. If a package such as VDSM or libvirt was updated, you must restart that service to get the new functionality."

Need to add - "if sanlock is updated, you should restart sanlockd, libvirtd and vdsmd" 
Perhaps, it could be simpler to suggest restarting the host.

Comment 1 Jodi Biddle 2014-04-27 18:39:00 EDT

For reference, the above comment was lifted from this bug: 

https://bugzilla.redhat.com/show_bug.cgi?id=1080931

Comment 2 Jodi Biddle 2014-04-27 18:40:01 EDT

As per Allon's suggestion, I have shortened the step to simply read: 

"Restart the host to ensure all updates are correctly applied."

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