Bug 245171

Summary: attr inheritance should try all direct ancestors
Product: [Retired] Red Hat Cluster Suite Reporter: Lon Hohberger <lhh>
Component: rgmanagerAssignee: Marek Grac <mgrac>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint, jhahm
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-1000 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-21 21:53:14 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:

Description Lon Hohberger 2007-06-21 13:51:38 UTC
+++ This bug was initially created as a clone of Bug #231521 +++

Description of problem:

The special non-OCF inherit flag for rgmanager's resource agents currently only
inherits from the parent resource.  For example, if the "nfslock" attr  is
inherited from the parent "service" for <fs> a la ineherit="service%nfslock",
and the service is structured thusly:

  <service nfslock="1">
    <fs/>
    <fs/>
  </service>

Things work fine.  However, if there's a necessary parent-child relationship
between two <fs/> agents, the second one will not inherit the nfslock parameter:

  <service nfslock="1">
    <fs> <!-- nfslock inherited -->
      <fs/> <!-- nfslock *not* inherited -->
    </fs>
  </service>

So, the inherit-flag should check parents-of-parents until a parent <service>
tag is found, or there are no more parents (e.g. service has no parents, so we
can't check its ancestors).

Comment 1 Marek Grac 2007-06-22 08:41:02 UTC
Patches in CVS

Comment 4 errata-xmlrpc 2007-11-21 21:53:14 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 the 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/RHBA-2007-1000.html