|Summary:||Allow unique attributes in resources to collide if the resources will never coexist|
|Product:||[Retired] Red Hat Cluster Suite||Reporter:||Lon Hohberger <lhh>|
|Component:||rgmanager||Assignee:||Lon Hohberger <lhh>|
|Status:||CLOSED WONTFIX||QA Contact:||Cluster QE <mspqa-list>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-05-03 15:08:24 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Lon Hohberger 2007-01-26 17:48:08 UTC
Description of problem: First appearance of this feature is here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=224462 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 resources. [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 17:56:58 UTC
Additionally, clurgmgrd should log things (not just print to stdout) when resource collisions are found.
Comment 2 Lon Hohberger 2007-01-26 22:41:31 UTC
Logging part is in CVS in all branches that are not frozen or obsolete.
Comment 3 Lon Hohberger 2007-05-03 15:08:24 UTC
This would be a complicated change for little actual benefit.