Back to bug 1378107

Who When What Removed Added
Ivan Devat 2016-09-21 13:46:45 UTC Status NEW ASSIGNED
Tomas Jelinek 2016-10-26 13:08:01 UTC Priority unspecified medium
Tomas Jelinek 2016-11-03 10:24:22 UTC Summary Missbehaviour of the flag --master in "pcs resource create" command Misbehavior of the flag --master in "pcs resource create" command
Radek Steiger 2017-01-23 16:14:40 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1395226
Radek Steiger 2017-01-23 16:15:35 UTC CC rsteiger
Ivan Devat 2017-01-31 14:17:59 UTC Doc Text Cause:
Pcs incorrectly identifies commandline arguments when a user runs "pcs resource create" command with flag "--master".

Consequence:
Pcs puts a different contents into the cib than the user expects according to the documentation.

Fix:
Correct the identification of commandline arguments.

Result:
Pcs puts a correct contents into the cib.
Doc Type If docs needed, set a value Bug Fix
Ivan Devat 2017-01-31 14:24:31 UTC Status ASSIGNED POST
Ivan Devat 2017-02-20 08:01:54 UTC Status POST MODIFIED
Fixed In Version pcs-0.9.156-1.el7
errata-xmlrpc 2017-02-20 08:58:26 UTC Status MODIFIED ON_QA
Radek Steiger 2017-05-17 12:35:25 UTC Status ON_QA VERIFIED
Tomas Jelinek 2017-06-02 08:30:51 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1458153
Tomas Jelinek 2017-06-02 11:33:06 UTC Status VERIFIED ASSIGNED
Tomas Jelinek 2017-06-05 15:26:39 UTC Status ASSIGNED ON_QA
Radek Steiger 2017-06-12 13:44:02 UTC Status ON_QA VERIFIED
errata-xmlrpc 2017-08-01 18:22:57 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2017-08-01 14:22:57 UTC
Steven J. Levine 2018-03-12 16:57:22 UTC CC slevine
Doc Text Cause:
Pcs incorrectly identifies commandline arguments when a user runs "pcs resource create" command with flag "--master".

Consequence:
Pcs puts a different contents into the cib than the user expects according to the documentation.

Fix:
Correct the identification of commandline arguments.

Result:
Pcs puts a correct contents into the cib.
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 following options were interpreted as master "meta"a 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
Flags needinfo?(idevat)
Ondrej Faměra 2018-03-13 00:08:48 UTC CC ofamera
Steven J. Levine 2018-03-13 03:30:06 UTC Doc Text 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 following options were interpreted as master "meta"a 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
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 following options 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
Ivan Devat 2018-03-13 09:02:07 UTC Flags needinfo?(idevat)
Steven J. Levine 2018-03-13 15:27:52 UTC Doc Text 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 following options 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
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

Back to bug 1378107