Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 690265 - Most of ASEHAagent.sh parameters should not be 'unique'
Most of ASEHAagent.sh parameters should not be 'unique'
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rgmanager (Show other bugs)
5.6
All Linux
medium Severity medium
: rc
: ---
Assigned To: Lon Hohberger
Cluster QE
:
Depends On:
Blocks: 719046 668957
  Show dependency treegraph
 
Reported: 2011-03-23 14:25 EDT by Julio Entrena Perez
Modified: 2012-02-21 01:19 EST (History)
7 users (show)

See Also:
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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-21 01:19:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0163 normal SHIPPED_LIVE rgmanager bug fix and enhancement update 2012-02-20 10:07:03 EST

  None (edit)
Description Julio Entrena Perez 2011-03-23 14:25:41 EDT
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 14:27:03 EDT
Created attachment 487111 [details]
ASEHAagent.sh diff
Comment 11 Lon Hohberger 2012-01-19 14:21:00 EST
    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 01:19:03 EST
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.