Bug 1031179

Summary:	luci should notify user if the change requires cluster restart
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Pokorný [poki] <jpokorny>
Component:	luci	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED WONTFIX	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.4	CC:	cfeist, cluster-maint, jpokorny, rsteiger
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-21 22:11:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1075802, 1172231

Description Jan Pokorný [poki] 2013-11-15 20:18:45 UTC

This will require some research and perhaps going one level deeper
(per-cluster and per-node granularity), but offhand:

- adding a fence device/instance that requires unfencing
  [bug 865161 comment 19]

> The docs should be updated to state that the cluster must be stopped
> while adding a fence device that requires unfencing.  (It's probably
> safest to stop the cluster while adding any fencing, but the argument
> for that is not quite so clear.)
> 
> It would also be nice if the ccs command refused to add unfencing to a
> live cluster, with an error stating the same.

Note: if there was a proper analysis in place, it would have been
      clearly a requirement for luci from the beginning

Comment 5 Red Hat Bugzilla 2023-09-14 01:53:48 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days