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.
Created attachment 502032[details]
A patch that returns $OCF_NOT_RUNNING instead of $OCF_ERR_ARGS inside do_monitor(
The fs.sh resource agent (ocf::redhat:fs.sh) reports an error condition (invalid parameter) when called with "monitor" if the referenced device doesn't exist. The device may not be present yet because a dependency has not been started (such as ocf::heartbeat:lvm-cluster.sh).
This error condition prevents the resource from being started -- even if the dependency is met by grouping the resources.
Name : resource-agents
Version : 3.0.12
Release : 22.el6
Reproduced every time.. requires a cluster with shared storage and properly configured CLVM, with device resources configured to only be available to one node at a time.
Explicit reproduction can be performed by simply specifying a non-existent device to the resource agent. For example:
[root@r1 ~]# OCF_RESKEY_mountpoint="/dev_rack1a" OCF_RESKEY_device="/dev/cluster_vg_01/r_lv_01" OCF_RESKEY_fstype="ext4" /usr/lib/ocf/resource.d/redhat/fs.sh monitor
<err> start_filesystem: Could not match /dev/cluster_vg_01/r_lv_01 with a real device
start_filesystem: Could not match /dev/cluster_vg_01/r_lv_01 with a real device
It would be desirable for the monitor call to return $OCF_NOT_RUNNING, which should be entirely true if the device does not exist.
I've attached a patch that returns $OCF_NOT_RUNNING instead of $OCF_ERR_ARGS inside do_monitor().
After resource-agents update:
[root@ask-04 ~]# OCF_RESKEY_device="/dev/noexist" OCF_RESKEY_fstype="ext3" /usr/lib/ocf/resource.d/redhat/fs.sh monitor
<err> start_filesystem: Could not match /dev/noexist with a real device
[fs.sh] start_filesystem: Could not match /dev/noexist with a real device
[root@ask-04 ~]# echo $?
7
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.
http://rhn.redhat.com/errata/RHSA-2011-1580.html
Created attachment 502032 [details] A patch that returns $OCF_NOT_RUNNING instead of $OCF_ERR_ARGS inside do_monitor( The fs.sh resource agent (ocf::redhat:fs.sh) reports an error condition (invalid parameter) when called with "monitor" if the referenced device doesn't exist. The device may not be present yet because a dependency has not been started (such as ocf::heartbeat:lvm-cluster.sh). This error condition prevents the resource from being started -- even if the dependency is met by grouping the resources. Name : resource-agents Version : 3.0.12 Release : 22.el6 Reproduced every time.. requires a cluster with shared storage and properly configured CLVM, with device resources configured to only be available to one node at a time. Explicit reproduction can be performed by simply specifying a non-existent device to the resource agent. For example: [root@r1 ~]# OCF_RESKEY_mountpoint="/dev_rack1a" OCF_RESKEY_device="/dev/cluster_vg_01/r_lv_01" OCF_RESKEY_fstype="ext4" /usr/lib/ocf/resource.d/redhat/fs.sh monitor <err> start_filesystem: Could not match /dev/cluster_vg_01/r_lv_01 with a real device start_filesystem: Could not match /dev/cluster_vg_01/r_lv_01 with a real device It would be desirable for the monitor call to return $OCF_NOT_RUNNING, which should be entirely true if the device does not exist. I've attached a patch that returns $OCF_NOT_RUNNING instead of $OCF_ERR_ARGS inside do_monitor().