Bug 887170
Summary: | Conga enables cluster services even if disabled explicitly | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Josef Zimek <pzimek> | |
Component: | conga | Assignee: | Ryan McCabe <rmccabe> | |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 5.8 | CC: | cluster-maint, fdinitto, jpokorny, rsteiger | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | conga-0.12.2-68.el5 | Doc Type: | Bug Fix | |
Doc Text: |
Proposed text:
Each time luci, the web-based frontend of conga cluster management,
was used to start or restart a cluster, or to have previously inactivated
node rejoin it, it would make cluster services such as cman, rgmanager
or clvmd enabled at boot on the respective cluster nodes. This can
interfere with user's preferences, for instance when running 2-nodes
cluster without quorum disk and having the services disabled on purpose
on one of the nodes (to prevent fence races). To avoid this, conga
was modified so that it no longer modifies the current service runlevel
settings in the mentioned cases, while still enabling the services when
the cluster is created or a new node is added as before.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1000522 (view as bug list) | Environment: | ||
Last Closed: | 2013-10-01 00:40:20 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: | 1000522 |
Description
Josef Zimek
2012-12-14 08:49:41 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1358.html |