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.
DescriptionJan Pokorný [poki]
2017-07-11 21:30:12 UTC
Once pcs is civil to per-operation specifications of parameters to the
respective resource, clufter needs to enable that as well, for more
complete raw CIB -> pcs commands coverage.
+++ This bug was initially created as a clone of Bug #1469801 +++
[...]
So what do I propose?
- make "monitor" operation accept any parameters supported by the agent
(modulo clashes with the operation's very own options), treat them
the same as with OCF_CHECK_LEVEL (put into <instance_attributes> for
the <op> in question)
- ditto for other operations, but require --force, because this asks for
problems (it's up to user to keep start-stop operations logically
in sync, otherwise the agent may go crazy)
- always check if the resource agent parameter specified down at the
operation level is not accidentally overridding:
- the default (i.e., the default for that is specified in meta-data)
- the same parameter set properly at the resource level
and for each, emit respective message and refuse, unless with --force
(note that "statusurl" for ocf:heartbeat:apache has no default)
- when allowing the resource agent parameters being passed on, ensure
the same validation takes places as when these are specified directly
at the resource level
--- Additional comment from Jan Pokorný on 2017-07-11 23:22:06 CEST ---
Note that this doesn't touch merely "pcs resource create", but also
"pcs resource op" family of commands.
Comment 4RHEL Program Management
2021-01-15 07:39:42 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.