[Cluster-devel] [PATCH] resource-agents: Find any descendant IP resource of a service

Michael Bunk bunk at iat.uni-leipzig.de
Fri Sep 30 09:01:59 UTC 2011

Am 28.09.2011 22:35, schrieb Lon Hohberger:
> On 09/28/2011 07:19 AM, Michael Bunk wrote:
>> Not just immediate children.  This fixes errors in sylog like this:
>> rgmanager[xxxx]: Looking For IP Addresses [apache:apache]>  Failed -
>> No IP Addresses Found
> I -think- it was intentional; if it's not at the top level, you can do
> things like:
>   <service>
>     <apache>
>       <ip/>
>     </apache>
>   </service>
> The // will then find that IP, but the configuration generated by apache
> resource agent will be incorrect and cause the Apache instance to fail
> to start: it will try to bind to the IP address.
> I suppose that's a degenerate case, however.

Yes, that is pathological... but our case - which worked in RHEL 4 -
looks like this:

  <script ref="tiebreaker">
     <script file="/etc/cluster/drbd0" name="drbd0" ...>
        <fs device="/dev/drbd0" ...>
          <ip ...>

It doesn't feel right to make the ip resource a sibling of the
tiebreaker script.

If <ip> resources are required to be put directly under <service>, then
the docs (without having read them every word) should mention this and
the XML schema for cluster.conf should enforce it.


More information about the Cluster-devel mailing list