Bug 151321 – gnbd assumes that the cluster node name = uname -n. This is no longer true.

Bug 151321 - gnbd assumes that the cluster node name = uname -n. This is no longer true.

Summary:	gnbd assumes that the cluster node name = uname -n. This is no longer true.

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Cluster Suite
Classification:	Red Hat
Component:	gnbd (Show other bugs)
Sub Component:
Version:	4
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ben Marzinski
QA Contact:	Cluster QE
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-16 17:19 EST by Ben Marzinski
Modified:	2010-01-27 13:04 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-01-27 13:04:57 EST
Type:	---
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 Ben Marzinski 2005-03-16 17:19:10 EST

If gulm or cmam use anything other than the value of uname -n for the cluster
nodename, gnbd will be using the wrong name.  This means that gnbd will not be
able to correctly fence the server. Also, unless the nodename parameter for
fence_gnbd is equal to uname -n, fence_gnbd will return false successes, allowing
corruption to occur.

Comment 1 Ben Marzinski 2005-03-16 17:43:57 EST

I changed the default behaviour of gnbd to get the nodename from magma.  If gnbd
is being used for some non-clustered purpose, the magma check can be overriden by
using the -n option to gnbd_import or gnbd_serv.  When -n is used, gnbd will
simply use uname -n.

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