https://bugzilla.redhat.com/show_bug.cgi?id=1343661 --- Doc Text *updated* by Steven J. Levine <slevine@xxxxxxxxxx> --- _clufter_ rebased to version 0.59.5 The _clufter_ packages, available as a Technology Preview, have been upgraded to upstream version 0.59.5, which provides a number of bug fixes, new features, and user experience enhancements over the previous version. Among the notable updates are the following: * The `ccs2pcs` conversion utility now properly propagates or adds monitor action. * The `pcs2pcscmd{,-needle}` command now propagates the cluster name correctly. Previously, the cluster name was mistakenly dropped, resulting in a command that confused the first cluster node for the cluster name as in, for example, `pcs cluster setup --start --name node1 node2 node3`. * The `ccs2pcs` commands no longer generate accidentally broken values of attributes marked as having an ID type in the schema. * With *2pcscmd* commands, the `clufter` tool no longer suggests `pcs cluster cib *file* --config`, which does not currently work for subsequent local-modification `pcs` commands. Instead it suggests `pcs cluster cib *file*`. * The `clufter` tool outputs now may vary significantly depending on the specified distribution target since the tool now aligns the output with what the respective environment, such as the `pcs` version, can support. Because of this, your distribution or setup may not be supported, and you should not expect that one sequence of `pcs` commands that the `clufter` tool produces is portable to a completely different environment. * The `clufter` tool now supports several new features of the `pcs` tool, including quorum devices. Additionally, the `clufter` tool supports older features recently added to the `pcs` tool, including ticket constraints, and resource sets for colocation and order constraints. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx