Bug 1031179 - luci should notify user if the change requires cluster restart [NEEDINFO]
Summary: luci should notify user if the change requires cluster restart
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.4
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1075802 1172231
TreeView+ depends on / blocked
 
Reported: 2013-11-15 20:18 UTC by Jan Pokorný [poki]
Modified: 2015-10-21 22:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-21 22:11:06 UTC
Target Upstream Version:
rsteiger: needinfo? (jpokorny)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 865161 0 unspecified CLOSED fence_scsi requires both fencing and unfencing section in cluster.conf 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Solution) 39903 0 None None None Never

Internal Links: 865161

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


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