Doug Knight wrote:
All,
I am in the process of upgrading my servers from 2.0.8 to 2.1.3. I had
planned on setting all my resources on the primary to unmanaged, to
conduct the installation while the resources continued to run. However,
following the instructions here:
http://www.linux-ha.org/v2/upgrade/reattach
and watching the GUI status of the resources, the setting of
is_managed_default had no effect. I grepped the cib.xml (cibadmin -Q |
grep managed) I discovered two different attributes; is_managed_default
= false, and is-managed-default = true. When I deleted
is_managed_default, then set is-managed-default to false, the GUI
reflected all processes as unmanaged. Checking the DTD delivered with
the 2.0.8 version on the primary, all I see is is_managed_default
defined. So, which is it, is_managed_default or is-managed-default? Same
goes for is_managed vs is-managed.
is-managed-default, although it may be is_managed_default is also
accepted (as with default-resource-stickiness and
default_resource_stickiness).
For an individual resource, it has to be is_managed with an underscore.
Regards
Dominik
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
