Bug 690265 - Most of ASEHAagent.sh parameters should not be 'unique'
Summary: Most of ASEHAagent.sh parameters should not be 'unique'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rgmanager
Version: 5.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 668957 719046
TreeView+ depends on / blocked
 
Reported: 2011-03-23 18:25 UTC by Julio Entrena Perez
Modified: 2018-11-26 19:48 UTC (History)
7 users (show)

Fixed In Version: rgmanager-2.0.52-22.el5
Doc Type: Bug Fix
Doc Text:
Cause: Several attributes of the ASEHAagent resource agent were marked 'unique' but should not have been. Consequence: Unnecessary resource attribute collisions. Fix: Make attributes not 'unique' Result: No more unnecessary resource attribute collisions.
Clone Of:
Environment:
Last Closed: 2012-02-21 06:19:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ASEHAagent.sh diff (1.17 KB, patch)
2011-03-23 18:27 UTC, Julio Entrena Perez
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 711852 0 high CLOSED second ASEHA agent wont start - Unique attribute collision 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2012:0163 0 normal SHIPPED_LIVE rgmanager bug fix and enhancement update 2012-02-20 15:07:03 UTC

Internal Links: 711852

Description Julio Entrena Perez 2011-03-23 18:25:41 UTC
Description of problem:
Attempting to create two Sybase resources results in an unique attribute collision, since all the resourge agent parameters have the unique="1" attribute.

Version-Release number of selected component (if applicable):
rgmanager-2.0.52-9.el5

How reproducible:
Always.

Steps to Reproduce:
1. Create two Sybase cluster resources and their corresponding services:

<ASEHAagent deep_probe_timeout="300" interfaces_file="/opt/sybase/interfaces" login_file="/opt/sybase/ase1_login_file" name="syb_ase1" server_name="ase1" shutdown_timeout="200" start_timeout="300" sybase_ase="ASE-15_0" sybase_home="/opt/sybase" sybase_ocs="OCS-15_0" sybase_user="sybase"/>
<ASEHAagent deep_probe_timeout="300" interfaces_file="/opt/sybase/interfaces" login_file="/opt/sybase/ase2_login_file" name="syb_ase2" server_name="ase2" shutdown_timeout="200" start_timeout="300" sybase_ase="ASE-15_0" sybase_home="/opt/sybase" sybase_ocs="OCS-15_0" sybase_user="sybase"/>
<service autostart="0" domain="fd_n1" exclusive="0" name="svc_ase1" recovery="relocate">
...
  <ASEHAagent ref="syb_ase1"/>
</service>
<service autostart="0" domain="fd_n1" exclusive="0" name="svc_ase2" recovery="relocate">
...
  <ASEHAagent ref="syb_ase2"/>
</service>

2. Validate the cluster.conf file:
# rg_test test /etc/cluster/cluster.conf

3.
  
Actual results:
# rg_test test /etc/cluster/cluster.conf
Running in test mode.
Error: Unique attribute collision. type=ASEHAagent attr=sybase_home value=/opt/sybase
Error storing ASEHAagent resource
Error: Reference to nonexistent resource syb_ase2 (type ASEHAagent)
Loaded 24 resource rules
...

Expected results:
# rg_test test /etc/cluster/cluster.conf
Running in test mode.
Loaded 24 resource rules
...

Additional info:
Only the 'name' and 'server_name' parameters should be unique.

Comment 1 Julio Entrena Perez 2011-03-23 18:27:03 UTC
Created attachment 487111 [details]
ASEHAagent.sh diff

Comment 11 Lon Hohberger 2012-01-19 19:21:00 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Several attributes of the ASEHAagent resource agent were marked 'unique' but should not have been.

Consequence: Unnecessary resource attribute collisions.

Fix: Make attributes not 'unique'

Result: No more unnecessary resource attribute collisions.

Comment 12 errata-xmlrpc 2012-02-21 06:19:03 UTC
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/RHBA-2012-0163.html


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