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 1667066 - [RFE] pretty-printing corosync configuration
Summary: [RFE] pretty-printing corosync configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.4
Assignee: Ondrej Mular
QA Contact: cluster-qe@redhat.com
Steven J. Levine
URL:
Whiteboard:
Depends On: 1682129
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-17 11:13 UTC by Tomas Jelinek
Modified: 2021-05-18 15:12 UTC (History)
9 users (show)

Fixed In Version: pcs-0.10.8-1.el8
Doc Type: Enhancement
Doc Text:
.New command to display Corosync configuration You can now print the contents of the `corosync.conf` file in several output formats with the new `pcs cluster config [show]` command. By default, the `pcs cluster config` command uses the `text` output format, which displays the Corosync configuration in a human-readable form, with the same structure and option names as the `pcs cluster setup` and `pcs cluster config update` commands.
Clone Of:
Environment:
Last Closed: 2021-05-18 15:12:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
fix cluster nodes list formatting (4.77 KB, patch)
2021-01-11 16:25 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1667061 0 high CLOSED [RFE] provide commands for changing corosync configuration of an existing cluster 2023-02-18 04:31:53 UTC

Internal Links: 1667061

Description Tomas Jelinek 2019-01-17 11:13:59 UTC 
Pcs has 'pcs cluster corosync' command which displays content of corosync.conf from the local or a remote node. Pcs should be able to print corosync configuration in a pretty form (in a similar way it does not print CIB in its XML form). This pretty-printed corosync configuration should be included in the output of 'pcs config [show]' command. Currently, only quorum configuration is pretty-printed there. Consider adding a command for pretty-printing corosync.conf only.
Comment 9 Miroslav Lisik 2020-12-16 16:31:23 UTC 
Proposed fix + test in attachment 1739694 [details] (bz1667061 comment 12)

New command added:
* pcs cluster config...

Test:
pcs cluster config
pcs cluster config show --output-format=text
pcs cluster config show --output-format=json --corosync-conf /tmp/corosync.conf
Comment 10 Miroslav Lisik 2020-12-18 17:44:33 UTC 
Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.7-3.el8.x86_64

NOTE: format of link options might change before devel freeze

[root@r8-node-01 ~]# pcs cluster config
Cluster Name: HACluster
Transport: knet
Nodes:
  r8-node-01 (nodeid: 1)
    r8-node-01 (link: 0)
    192.168.122.121 (link: 1)
  r8-node-02 (nodeid: 2)
    r8-node-02 (link: 0)
    192.168.122.122 (link: 1)
Links:
  Link 1:
    linknumber: 1
    ping_interval: 1000
    ping_timeout: 2000
    pong_count: 5
Compression Options:
  level: 9
  model: zlib
  threshold: 150
Crypto Options:
  cipher: aes256
  hash: sha256
Totem Options:
  downcheck: 2000
  join: 50
  token: 10000
Quorum Device: net
  Options:
    sync_timeout: 2000
    timeout: 3000
  Model Options:
    algorithm: lms
    host: r8-node-03
  Heuristics:
    exec_ping: ping -c 1 127.0.0.1

[root@r8-node-01 ~]# pcs cluster config show --output-format=cmd
Warning: Quorum device configuration detected but not yet supported by this command.
pcs cluster setup HACluster \
  r8-node-01 addr=r8-node-01 addr=192.168.122.121 \
  r8-node-02 addr=r8-node-02 addr=192.168.122.122 \
  transport \
  knet \
    link \
      linknumber=1 \
      ping_interval=1000 \
      ping_timeout=2000 \
      pong_count=5 \
    compression \
      level=9 \
      model=zlib \
      threshold=150 \
    crypto \
      cipher=aes256 \
      hash=sha256 \
  totem \
    downcheck=2000 \
    join=50 \
    token=10000
Comment 14 Tomas Jelinek 2021-01-06 15:24:57 UTC 
We want to modify cluster nodes list formatting to make it more consistent with the rest of the output. It should look like this:

Nodes:
  r8-node-01:
    nodeid: 1
    Link 0 address: r8-node-01
    Link 1 address: 192.168.122.121
  r8-node-02:
    nodeid: 2
    Link 0 address: r8-node-02
    Link 1 address: 192.168.122.122
Comment 15 Tomas Jelinek 2021-01-11 16:25:22 UTC 
Created attachment 1746323 [details]
fix cluster nodes list formatting
Comment 16 Miroslav Lisik 2021-02-01 16:41:04 UTC 
Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-1.el8.x86_64

[root@r8-node-01 ~]# pcs cluster config
Cluster Name: HACluster
Transport: knet
Nodes:
  r8-node-01:
    Link 0 address: r8-node-01
    Link 1 address: 192.168.122.121
    nodeid: 1
  r8-node-02:
    Link 0 address: r8-node-02
    Link 1 address: 192.168.122.122
    nodeid: 2
Crypto Options:
  cipher: aes256
  hash: sha256
Comment 31 errata-xmlrpc 2021-05-18 15:12:05 UTC 
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 (pcs bug fix and enhancement update), 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://access.redhat.com/errata/RHEA-2021:1737
Note You need to log in before you can comment on or make changes to this bug.