Back to bug 1386114

Who When What Removed Added
Tomas Jelinek 2016-10-26 14:54:16 UTC Priority unspecified high
Fabio Massimo Di Nitto 2016-11-08 07:59:48 UTC CC fdinitto
Radek Steiger 2017-01-23 17:23:54 UTC CC rsteiger
Tomas Jelinek 2017-02-03 15:25:35 UTC Status NEW ASSIGNED
Assignee tojeline idevat
Tom Lavigne 2017-05-17 16:38:03 UTC CC tlavigne
Ivan Devat 2017-05-25 08:38:16 UTC Status ASSIGNED POST
Ivan Devat 2017-05-30 10:06:34 UTC Status POST ASSIGNED
Ivan Devat 2017-05-31 12:31:15 UTC Status ASSIGNED MODIFIED
Fixed In Version pcs-0.9.158-3.el7
errata-xmlrpc 2017-05-31 12:53:29 UTC Status MODIFIED ON_QA
Ivan Devat 2017-06-06 14:56:35 UTC Doc Text Cause:
pcs does not do all necessary validations of the name and the host of a remote node.

Consequence:
Cluster does not work correctly when the name or the host of a remote conflicts with a resource id or with a cluster node host.

Fix:
Necessary validation was added to relevant commands.

Result:
Pcs does not allow to put into cluster configuration the conflicting name or the conflicting host of remote node.
Doc Type If docs needed, set a value Release Note
Ivan Devat 2017-06-06 15:00:50 UTC Doc Text Cause:
pcs does not do all necessary validations of the name and the host of a remote node.

Consequence:
Cluster does not work correctly when the name or the host of a remote conflicts with a resource id or with a cluster node host.

Fix:
Necessary validation was added to relevant commands.

Result:
Pcs does not allow to put into cluster configuration the conflicting name or the conflicting host of remote node.
Cause:
pcs does not do all necessary validations of the name and the host of a remote and guest node.

Consequence:
Cluster does not work correctly when the name or the host of a remote or guest node conflicts with a resource id or with a cluster node host.

Fix:
Necessary validation was added to relevant commands.

Result:
Pcs does not allow to put into cluster configuration the conflicting name or the conflicting host of remote or guest node.
Lenka Špačková 2017-06-08 08:26:21 UTC Docs Contact slevine
Steven J. Levine 2017-06-09 21:34:37 UTC Doc Text Cause:
pcs does not do all necessary validations of the name and the host of a remote and guest node.

Consequence:
Cluster does not work correctly when the name or the host of a remote or guest node conflicts with a resource id or with a cluster node host.

Fix:
Necessary validation was added to relevant commands.

Result:
Pcs does not allow to put into cluster configuration the conflicting name or the conflicting host of remote or guest node.
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.
Flags needinfo?(idevat)
Ivan Devat 2017-06-12 05:49:43 UTC Flags needinfo?(idevat)
Radek Steiger 2017-06-30 13:03:04 UTC Status ON_QA VERIFIED
Radek Steiger 2017-06-30 13:03:20 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1466789
Lenka Špačková 2017-07-28 14:48:55 UTC Doc Text 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.
*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.
errata-xmlrpc 2017-08-01 18:24:40 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2017-08-01 14:24:40 UTC
Pasi Karkkainen 2017-08-02 07:32:16 UTC CC pasik

Back to bug 1386114