Bug 224608 - Allow unique attributes in resources to collide if the resources will never coexist
Allow unique attributes in resources to collide if the resources will never c...
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: rgmanager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2007-01-26 12:48 EST by Lon Hohberger
Modified: 2009-04-16 16:21 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-03 11:08:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lon Hohberger 2007-01-26 12:48:08 EST
Description of problem:  First appearance of this feature is here:


A user was attempting to use the same mountpoint for two different file systems
as part of two independent services which would never coexist due to restricted
failover domain configurations.

Actual results: Illegal configuration.

Expected results: Not fully explored.

This might not be possible since rgmanager was designed to allow coexistence of
all resources on a single node for a given configuration - even if the requisit
device(s) were not present for all nodes.

Since placement of resources is separate from resource definitions, this is
difficult to solve using failover domains.  However, it may be possible to solve
this at least partially using the inter-service dependencies which are being
explored:  If two services have 'colocate' set to 'never', it may be permissable
to allow collisions of "unique" attributes between those services' private

[Note: Primary attributes will *not* be allowed to collide, their resource
placement policies notwithstanding.]

This is a feature request.
Comment 1 Lon Hohberger 2007-01-26 12:56:58 EST
Additionally, clurgmgrd should log things (not just print to stdout) when
resource collisions are found.
Comment 2 Lon Hohberger 2007-01-26 17:41:31 EST
Logging part is in CVS in all branches that are not frozen or obsolete.
Comment 3 Lon Hohberger 2007-05-03 11:08:24 EDT
This would be a complicated change for little actual benefit.

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