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:
ocf:heartbeat:sybaseASE fails to start when symlinks are used for sybase_home
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-30.el7_7.7.x86_64
Steps to Reproduce:
1. create ocf:heartbeat:sybaseASE using a symlink to a directory on cluster managed storage as the sybase_home attribute
Actual results:
Resource fails since the probe will return OCF_ERR_GENERIC (1) instead of OCF_NOT_RUNNING (7) or OCF_SUCCESS (0).
Expected results:
The resource agent should be configured in such a way that should be able to accurately report when the resource isn't running even when symlinks are used.
Additional info:
This appears to be the result of verify_all() which returns OCF_ERR_ARGS, but then the caller converts that to OCF_ERR_GENERIC
# Check if the parameter 'sybase_home' is a valid path.
if [[ ! -d $OCF_RESKEY_sybase_home ]]
then
ocf_log err "sybaseASE: The sybase_home '$OCF_RESKEY_sybase_home' doesn't exist."
return $OCF_ERR_ARGS
fi
------------------------------------------(cut)-----------------------------------------------------------
# Check if the directory /$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ase exists.
if [[ ! -d $OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ase ]]
then
ocf_log err "sybaseASE: The directory '$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ase' doesn't exist."
return $OCF_ERR_ARGS
fi
------------------------------------------(cut)-----------------------------------------------------------
# Check if the directory /$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ocs exists.
if [[ ! -d $OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ocs ]]
then
ocf_log err "sybaseASE: The directory '$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ocs' doesn't exist."
return $OCF_ERR_ARGS
fi
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 (resource-agents 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/RHBA-2021:1736
Description of problem: ocf:heartbeat:sybaseASE fails to start when symlinks are used for sybase_home Version-Release number of selected component (if applicable): resource-agents-4.1.1-30.el7_7.7.x86_64 Steps to Reproduce: 1. create ocf:heartbeat:sybaseASE using a symlink to a directory on cluster managed storage as the sybase_home attribute Actual results: Resource fails since the probe will return OCF_ERR_GENERIC (1) instead of OCF_NOT_RUNNING (7) or OCF_SUCCESS (0). Expected results: The resource agent should be configured in such a way that should be able to accurately report when the resource isn't running even when symlinks are used. Additional info: This appears to be the result of verify_all() which returns OCF_ERR_ARGS, but then the caller converts that to OCF_ERR_GENERIC # Check if the parameter 'sybase_home' is a valid path. if [[ ! -d $OCF_RESKEY_sybase_home ]] then ocf_log err "sybaseASE: The sybase_home '$OCF_RESKEY_sybase_home' doesn't exist." return $OCF_ERR_ARGS fi ------------------------------------------(cut)----------------------------------------------------------- # Check if the directory /$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ase exists. if [[ ! -d $OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ase ]] then ocf_log err "sybaseASE: The directory '$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ase' doesn't exist." return $OCF_ERR_ARGS fi ------------------------------------------(cut)----------------------------------------------------------- # Check if the directory /$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ocs exists. if [[ ! -d $OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ocs ]] then ocf_log err "sybaseASE: The directory '$OCF_RESKEY_sybase_home/$OCF_RESKEY_sybase_ocs' doesn't exist." return $OCF_ERR_ARGS fi