Este contenido no está disponible en el idioma seleccionado.
Chapter 24. Clustering
Pacemaker Remote may shut down, even if its connection to the cluster is unmanaged
Previously, if a Pacemaker Remote connection was unmanaged, the Pacemaker Remote daemon would never receive a shutdown acknowledgment from the cluster. As a result, Pacemaker Remote would be unable to shut down. With this fix, if a Pacemaker Remote connection is unmanaged, the cluster now immediately sends a shutdown acknowledgement to Pacemaker Remote nodes that request shutdown, rather than wait for resources to stop. As a result, Pacemaker Remote may shut down, even if its connection to the cluster is unmanaged. (BZ#1388489)
pcs now validates the name and the host of a remote and guest node
Previously, the
pcs command did not validate whether the name or the host of a remote or guest node conflicted with a resource ID or with a cluster node, a situation that would cause the cluster not to work correctly. With this fix, validation has been added to the relevant commands and pcs does not allow a user to configure a cluster with a conflicting name or conflicting host of a remote or guest node. (BZ#1386114)
New syntax of master option in pcs resource create command allows correct creation of meta attributes
Previously, when a
pcs resource creation command included the --master flag, all options after the keyword meta were interpreted as master meta attributes. This made it impossible to create meta attributes for the primitive when the --master flag was specified. This fix provides a new syntax for specifying a resource as a master slave clone by using the following format for the command:
pcs resource create resource_id standard:provider:type|type [resource options] master [master_options...]
This allows you to specify
meta options as follows:
pcs resource create resource_id standard:provider:type|type [resource_options] meta meta_options... master [master_options...]
Additionally, with this fix, you specify a clone resource with the
clone option rather than the --clone flag, as in previous releases. The new format for specifying a clone resource is as follows:
pcs resource create resource_id standard:provider:type|type [resource_options] clone
(BZ#1378107)
