Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
shutdown_wait option of cman Postgres-8 RA is ignored by clufter while it could be converted to "stop" option in pcs.

Version-Release number of selected component (if applicable):
6653eb19834b66b3dde4dafc1e4533e4a00df748 from next branch

How reproducible:
always

Steps to Reproduce:
1. try converting cluster.conf containing postgres-8 resource with defined shutdown_wait timeout

Actual results:
ignored

Expected results:
should be migrated to "stop"

Additional info:
none

If I am not mistaken this is actually a bug in resource-agents:
https://github.com/ClusterLabs/resource-agents/pull/584
and hence intentionally omitted in the conversion
(as that parameter had actually no effect in the past).

Alternatively give that parameter a meaning and then it would be
a bug in the conversion/clufter.

This discrepancy introduced with
https://github.com/ClusterLabs/resource-agents/commit/5e026d222796c4a898b9e157c4a90ac15b0206d9
([bug 694816])