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 1337671 - Oracle12c resource status check fails if username is longer than 8 characters in pacemaker cluster
Summary: Oracle12c resource status check fails if username is longer than 8 characters...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1317578
Blocks: 1269194
TreeView+ depends on / blocked
 
Reported: 2016-05-19 19:00 UTC by Oyvind Albrigtsen
Modified: 2019-11-14 08:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1317578
Environment:
Last Closed: 2016-07-22 20:16:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Oyvind Albrigtsen 2016-05-19 19:00:43 UTC
+++ This bug was initially created as a clone of Bug #1317578 +++

Description of problem:

Oracle resource agent for Oracle12c in RHEL 7 cluster contain status check which performs grep of "ps" output for Oracle user based on environment variable $ORACLE_OWNER. However if the $ORACLE_OWNER value contains more than 8 characters the `ps` cuts the username in output so the grep won't succeed causing status check to fail.


From sources of resource-agents (RHEL 7.1), ClusterLabs-resource-agents-5434e96/heartbeat/oralsnr:


269 show_procs() {
270     ps -e -o pid,user,args |
271         grep '[t]nslsnr' | grep -w "$listener" | grep -w "$ORACLE_OWNER"


EXAMPLE:
========
If $ORACLE_OWNER is "oracle123" it will be displayed in `ps -e -o pid,user,args` output as "oracle1+" and the check (above line #271) will fail causing the status check to fail.
========


"ps" offers -U <username> parameter to list only processes related to <username> so we could use it instead of grepping the user itself. The `ps -U $ORACLE_OWNER` should work also if the username is longer than 8 characters


Version:
RHEL 7.1, resource-agents-3.9.5

How reproducible:
Always

--- Additional comment from Oyvind Albrigtsen on 2016-03-16 13:02:13 CET ---

Tested and working as expected:
https://github.com/ClusterLabs/resource-agents/pull/781

Comment 2 John Ruemker 2016-07-22 20:16:18 UTC
This issue was resolved in the customer's environment by applying a fix to pacemaker that prevented an issue which incorrectly applied a COLUMN_WIDTH of 80 to pacemaker environments that was then getting handed down to the oralsnr agent.  So, to our knowledge there are no customers needing this for RHEL 6, and in fact I don't expect this bug should even be present in RHEL 6 assuming you're on a non-affected version of pacemaker.  

I'm going to close this out.  

-John


Note You need to log in before you can comment on or make changes to this bug.