Bug 988945
| Summary: | dlm/gfs_controld: possibly wrong default for plock_ownership attribute | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Pokorný [poki] <jpokorny> |
| Component: | luci | Assignee: | Ryan McCabe <rmccabe> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.4 | CC: | cluster-maint, fdinitto, jpokorny, rsteiger, tlavigne |
| Target Milestone: | rc | Keywords: | EasyFix |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | luci-0.26.0-74.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Inverse defaults for "POSIX Lock Ownership" (plock_ownership attribute)
in the DLM and gfs_controld sections of cluster configuration were
incorrectly assumed.
Consequence:
Luci could, upon compacting the configuration so as to be sent as a new
authoritative version within the cluster, accidentally drop information
of the mentioned configuration options being previously enabled, leading
to their effective disabling.
Fix:
Luci now assumes correct defaults for the mentioned configuration options.
Result:
Luci no longer drops the information about the mentioned configuration
options being enabled.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-11 00:16:44 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: | |||
|
Description
Jan Pokorný [poki]
2013-07-26 18:28:03 UTC
More specifically, the reported problem was with plock_ownership attribute of <dlm> within cluster.conf being assumed with different defaults depending on the tool: - dlm_controld, the effective user: 0 (plock ownership disabled) - luci, the configuration tool: 1 (enabled) This means, for instance, following scenario is plausible: 1. cluster.conf containing following snippet is loaded into luci: <dlm plock_ownership="1"/> 2. some unrelated change is made to the "configuration model" built from cluster.conf at step 1. 3. that change is to be propagated back to the cluster, hence the model is externalized, at which point plock_ownership="1" bit is dropped as it is deemed a default (and hence redundant) --> Voilà, plock ownership configuration was silently flipped from enabled to disabled. What's more, it cannot be re-enabled due to the same wrong luci's assumption; only plock_ownership="0" can ever be emitted by luci, which is the same as not emitting this parameter at all. 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. https://rhn.redhat.com/errata/RHBA-2016-0892.html |