RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1031179 - luci should notify user if the change requires cluster restart
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: 2023-09-14 01:53 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:
Embargoed:


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

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


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