Red Hat Bugzilla – Bug 1212904
better integration with standalone (unbundled) clufter package for cluster configuration conversion
Last modified: 2015-11-19 04:36:48 EST
+++ This bug was initially created as a clone of Bug #1133897 +++ In the mentioned 7.1 bug, the aim was in providing initial/TechPreview feature to allow the users of the old (not-pcs-managed) cluster stack to migrate to the new one (pcs-friendly) while retaining the original configuration in the conversion process as completely as possible. This functionality is provided by clufter project code base of which was for time pressing reasons bundled as a subpackage of pcs. As the clufter is usable on its own (via "clufter" command provided) and the relationship to pcs is not so tight to justify the burden of a shared comaintenance of single SRPM, unbundling/split into a separate component is planned (as already happened for RHEL 6.7 timeframe, where standalone clufter has been included). Hence this bug serves to track the relevant tasks on the pcs side: 1. get rid of clufter bundling (i.e., restore the state prior to RHEL 7.1 where clufter was first introduced in 7.* line) 2. possibly teach pcs to facilitate "conversion to pcs commands" (starting with either old stack configuration, or actual file-level configuration of the new stack); see [bug 1171312 comment 13]
Inclusion of clufter as a standalone package is tracked as [bug 1212909] and is a (partial - point 1. from above) prerequisite for this one.
*** Bug 1159375 has been marked as a duplicate of this bug. ***
Clufter has been moved to a standalone package. Conversion of a cluster configuration to a sequence of pcs commands is not ready yet on clufter's side.
re [comment 0]: > Hence this bug serves to track the relevant tasks on the pcs side: TODO checklist revmap: 1. get rid of clufter bundling -- DONE 2. possibly teach pcs to facilitate "conversion to pcs commands" 3. propagate information about whether to use colorization of clufter library output when run from within pcs - in that case, clufter can have incorrect information whether it is outputting to terminal (can be run in pseudo-terminal) to that piece of information detected directly by pcs should be passed down the call-chain
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/RHSA-2015-2290.html