Bug 1031179 - luci should notify user if the change requires cluster restart [NEEDINFO]
luci should notify user if the change requires cluster restart
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci (Show other bugs)
6.4
Unspecified Unspecified
low Severity medium
: rc
: ---
Assigned To: Ryan McCabe
cluster-qe@redhat.com
:
Depends On:
Blocks: 1075802 1172231
  Show dependency treegraph
 
Reported: 2013-11-15 15:18 EST by Jan Pokorný
Modified: 2015-10-21 18:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-21 18:11:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rsteiger: needinfo? (jpokorny)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 39903 None None None Never

  None (edit)
Description Jan Pokorný 2013-11-15 15:18:45 EST
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.