Back to bug 2168155
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-02-08 10:31:54 UTC | Pool ID | sst_high_availability_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-02-08 10:32:48 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-147947 | |
| Nina Hostakova | 2023-02-08 10:37:59 UTC | Blocks | 2168159 | |
| Tomas Jelinek | 2023-02-08 11:35:56 UTC | Severity | unspecified | low |
| Priority | unspecified | low | ||
| Keywords | Triaged | |||
| Tomas Jelinek | 2023-03-20 10:33:26 UTC | Link ID | Red Hat Bugzilla 1741056 | |
| Tomas Jelinek | 2023-03-20 12:43:54 UTC | Blocks | 2168159 | |
| Tomas Jelinek | 2023-04-17 15:29:36 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Status | NEW | ASSIGNED | ||
| Target Release | --- | 9.3 | ||
| Tomas Jelinek | 2023-04-18 07:48:38 UTC | Status | ASSIGNED | POST |
| Doc Text | Keyword `meta` in `pcs resource clone` and `pcs resource promotable` commands is now deprecated (it wasn't doing anything anyway) | |||
| Doc Type | Bug Fix | Deprecated Functionality | ||
| Tomas Jelinek | 2023-04-18 07:50:23 UTC | CC | mmazoure | |
| Flags | needinfo?(nhostako) needinfo?(mmazoure) | |||
| Michal Mazourek | 2023-04-19 12:51:13 UTC | Flags | needinfo?(nhostako) needinfo?(mmazoure) | |
| Dean Jansa | 2023-04-19 22:22:58 UTC | Link ID | Red Hat Issue Tracker CLUSTERQE-6633 | |
| Michal Pospisil | 2023-05-26 09:28:11 UTC | Fixed In Version | pcs-0.11.5-1.el9 | |
| Status | POST | MODIFIED | ||
| Ondrej Mular | 2023-05-30 11:15:31 UTC | Fixed In Version | pcs-0.11.5-1.el9 | |
| Status | MODIFIED | ASSIGNED | ||
| Tomas Jelinek | 2023-06-19 13:03:40 UTC | Doc Text | Keyword `meta` in `pcs resource clone` and `pcs resource promotable` commands is now deprecated (it wasn't doing anything anyway) | Not using keyword `meta` for specifying clone meta attributes in `pcs resource clone`, `pcs resource promotable` and `pcs resource create` commands is now deprecated. The `pcs resource clone` and `pcs resource promotable` commands work the same regardless whether 'meta' is specified. For `pcs resource create` command, `--future` option must be specified to enable the new arguments processing. |
| Status | ASSIGNED | POST | ||
| Michal Pospisil | 2023-06-20 16:06:26 UTC | Fixed In Version | pcs-0.11.6-1.el9 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-07-04 08:39:10 UTC | Status | MODIFIED | ON_QA |
| Lucie Vařáková | 2023-07-12 09:32:22 UTC | Docs Contact | slevine | |
| Steven J. Levine | 2023-07-17 16:59:15 UTC | Flags | needinfo?(omular) | |
| Ondrej Mular | 2023-07-18 07:36:20 UTC | Flags | needinfo?(omular) | |
| Steven J. Levine | 2023-07-18 16:43:07 UTC | Flags | needinfo?(omular) | |
| Ondrej Mular | 2023-07-19 08:29:04 UTC | Flags | needinfo?(omular) | |
| Steven J. Levine | 2023-07-19 17:48:54 UTC | Flags | needinfo?(omular) | |
| Ondrej Mular | 2023-07-20 07:17:24 UTC | Flags | needinfo?(omular) | |
| Steven J. Levine | 2023-07-20 14:19:18 UTC | Doc Text | Not using keyword `meta` for specifying clone meta attributes in `pcs resource clone`, `pcs resource promotable` and `pcs resource create` commands is now deprecated. The `pcs resource clone` and `pcs resource promotable` commands work the same regardless whether 'meta' is specified. For `pcs resource create` command, `--future` option must be specified to enable the new arguments processing. | .New `pcs` parsing requires `meta` keyword when specifying clone meta attributes To ensure consistency in the `pcs` command format, configuring clone meta attributes with the `pcs resource clone`, `pcs resource promotable`, and `pcs resource create` commands without specifying the `meta` keyword is now deprecated. Previously, the `meta` keyword was ignored in the `pcs resource clone` and `pcs resource promotable` commands. In the `pcs resource create` command, however, the meta attributes specified after the `meta` keyword when it follwed the `clone` keyword were assigned to the resource rather than to the clone. With this updated parsing algorithm, meta attributes specified after the `meta` keyword when it follows the `clone` keyword are assigned to the clone. To maintain compatibility with existing scripts which rely on the older format, you must specify the `--future` command option to enable this new argument processing when creating a cloned resource with the `pcs resource create` command. The following command now creates a resource with the meta attribute `mv=v1` and a clone with the meta attribute `mv=v2`: `pcs resource create dummy1 ocf:pacemaker:Dummy meta m1=v1 clone meta m2=v2 --future` |
| Doc Type | Deprecated Functionality | Enhancement | ||
| Red Hat Bugzilla | 2023-08-10 15:40:13 UTC | QA Contact | cluster-qe | cluster-qe |
| Steven J. Levine | 2023-08-10 17:42:26 UTC | Doc Text | .New `pcs` parsing requires `meta` keyword when specifying clone meta attributes To ensure consistency in the `pcs` command format, configuring clone meta attributes with the `pcs resource clone`, `pcs resource promotable`, and `pcs resource create` commands without specifying the `meta` keyword is now deprecated. Previously, the `meta` keyword was ignored in the `pcs resource clone` and `pcs resource promotable` commands. In the `pcs resource create` command, however, the meta attributes specified after the `meta` keyword when it follwed the `clone` keyword were assigned to the resource rather than to the clone. With this updated parsing algorithm, meta attributes specified after the `meta` keyword when it follows the `clone` keyword are assigned to the clone. To maintain compatibility with existing scripts which rely on the older format, you must specify the `--future` command option to enable this new argument processing when creating a cloned resource with the `pcs resource create` command. The following command now creates a resource with the meta attribute `mv=v1` and a clone with the meta attribute `mv=v2`: `pcs resource create dummy1 ocf:pacemaker:Dummy meta m1=v1 clone meta m2=v2 --future` | .New `pcs` parsing requires `meta` keyword when specifying clone meta attributes To ensure consistency in the `pcs` command format, configuring clone meta attributes with the `pcs resource clone`, `pcs resource promotable`, and `pcs resource create` commands without specifying the `meta` keyword is now deprecated. Previously, the `meta` keyword was ignored in the `pcs resource clone` and `pcs resource promotable` commands. In the `pcs resource create` command, however, the meta attributes specified after the `meta` keyword when it followed the `clone` keyword were assigned to the resource rather than to the clone. With this updated parsing algorithm, meta attributes specified after the `meta` keyword when it follows the `clone` keyword are assigned to the clone. To maintain compatibility with existing scripts which rely on the older format, you must specify the `--future` command option to enable this new argument processing when creating a cloned resource with the `pcs resource create` command. The following command now creates a resource with the meta attribute `mv=v1` and a clone with the meta attribute `mv=v2`: `pcs resource create dummy1 ocf:pacemaker:Dummy meta m1=v1 clone meta m2=v2 --future` |
Back to bug 2168155