Bug 632704

Summary: If whitespace in mysql resource name then pid file is not found
Product: Red Hat Enterprise Linux 5 Reporter: Shane Bradley <sbradley>
Component: rgmanagerAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5CC: cluster-maint, djansa, edamato, sbradley, tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rgmanager-2.0.52-10.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 667222 Environment:
Last Closed: 2011-07-21 10:47:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch for config-utils to turn whitespaces to underscores none

Description Shane Bradley 2010-09-10 18:59:55 UTC
Created attachment 446576 [details]
Patch for config-utils to turn whitespaces to underscores

Description of problem:

If a mysql resource has a space in its instance name then the resource
will fail to start.

For example: "my SQLTEST"
 <service autostart="0" name="mysql" recovery="disable">
    <mysql config_file="/etc/my.cnf" listen_address="127.0.0.1" mysql_options="" 
           name="my SQLTEST" shutdown_wait="5"/>
 </service>

The solution is to convert all the whitespaces to underscores.

Version-Release number of selected component (if applicable):
rgmanager-2.0.52-6.el5_5.8

How reproducible:
Everytime

Steps to Reproduce:
1. Create a mysql cluster resource in a service
2. The name of resource should contain a whitespace
3. Start the service that contains the resource
  
Actual results:
An error will occur when service is started:
Sep 10 14:18:54 msober clurgmgrd: [17513]: <err> Checking Existence Of File /var/run/cluster/mysql/mysql:mySQLTEST.pid [mysql:my SQLTEST] > Failed - File Doesn't Exist 

Expected results:
Should not fail

Additional info:
There is a patch attached to the bz.

Comment 3 RHEL Program Management 2011-01-11 20:24:17 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2011-01-11 23:27:31 UTC
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 5 Marek Grac 2011-02-07 13:42:07 UTC
Patch from upstream will be used because it is more general solution. 

http://git.fedorahosted.org/git/?p=resource-agents.git;a=commit;h=4ae988fa61afad242a870571622f4ab2aafadc31

Comment 8 errata-xmlrpc 2011-07-21 10:47:56 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-1000.html