Back to bug 2186218

Who When What Removed Added
Red Hat Bugzilla 2023-04-12 12:47:31 UTC Pool ID sst_system_roles_rhel_9
Pino Toscano 2023-04-12 12:57:42 UTC Link ID Github linux-system-roles/rhc/issues/90
Pino Toscano 2023-04-12 12:58:14 UTC Assignee rmeggins ptoscano
Status NEW ASSIGNED
Red Hat One Jira (issues.redhat.com) 2023-04-12 12:59:13 UTC Link ID Red Hat Issue Tracker RHELPLAN-154529
Rich Megginson 2023-04-12 13:52:12 UTC Doc Type If docs needed, set a value Bug Fix
CC rmeggins
Whiteboard role:rhc
RHEL Program Management 2023-04-12 13:52:22 UTC Keywords Triaged
Rich Megginson 2023-04-13 14:34:23 UTC Link ID Github linux-system-roles/rhc/pull/92
Rich Megginson 2023-04-14 19:46:20 UTC Status ASSIGNED MODIFIED
Rich Megginson 2023-04-14 19:47:06 UTC Blocks 2186908
Rich Megginson 2023-04-14 20:07:47 UTC Blocks 2186913
Lucie Vařáková 2023-04-17 14:17:40 UTC Docs Contact sdubewar
Doc Type Bug Fix Known Issue
Sagar Dubewar 2023-04-19 05:46:06 UTC Flags needinfo?(ptoscano)
CC ptoscano
Pino Toscano 2023-04-20 11:55:38 UTC Doc Text Cause: a bug in the logic that uses the specified activation keys

Consequence: in cause a system is already registered and activation keys are specified, the execution of the `rhc` system role fails

Workaround (if any): (not exactly nice and/or elegant...) do not specify activation keys on a system that is already registered

Result:

This will be fixed in a following update of the `rhel-system-roles` package.
Flags needinfo?(ptoscano)
Sagar Dubewar 2023-04-21 12:14:08 UTC Doc Text Cause: a bug in the logic that uses the specified activation keys

Consequence: in cause a system is already registered and activation keys are specified, the execution of the `rhc` system role fails

Workaround (if any): (not exactly nice and/or elegant...) do not specify activation keys on a system that is already registered

Result:

This will be fixed in a following update of the `rhel-system-roles` package.
.The `rhc` system role fails on already registered systems when `rhc_auth` contains activation keys

Executing playbook files on already registered systems fails if activation keys are specified for the `rhc_auth` parameter. To workaround this issue, do not specify activation keys when executing the playbook file on the already registered system.
Rich Megginson 2023-04-28 20:27:45 UTC Status MODIFIED POST
Rich Megginson 2023-04-29 00:14:02 UTC Target Release --- 9.3
CC cdonnell, djez, jharuda, vdanek
Flags needinfo?(djez) needinfo?(jharuda) needinfo?(vdanek) needinfo?(cdonnell)
Jakub Haruda 2023-05-01 21:43:19 UTC QA Contact rhel-cs-system-management-subsystem-qe jharuda
Rich Megginson 2023-05-04 20:40:41 UTC Fixed In Version rhel-system-roles-1.22.0-0.6.el9
Status POST MODIFIED
errata-xmlrpc 2023-05-04 20:43:26 UTC Status MODIFIED ON_QA
Jakub Haruda 2023-06-06 13:40:10 UTC Status ON_QA VERIFIED
Flags needinfo?(jharuda)
Rich Megginson 2023-06-11 17:29:38 UTC CC fkrska, pkettman
Flags needinfo?(djez) needinfo?(vdanek) needinfo?(cdonnell) needinfo?(fkrska) needinfo?(pkettman) needinfo?(briasmit)
Brian Smith 2023-06-12 12:34:01 UTC Flags needinfo?(briasmit)
Filip Krska 2023-06-12 13:00:08 UTC Priority unspecified high
RHEL Program Management Team 2023-06-12 13:18:14 UTC Blocks 2214282
RHEL Program Management Team 2023-06-12 13:18:18 UTC Keywords ZStream
Filip Krska 2023-06-12 13:30:11 UTC Keywords ZStream
Flags needinfo?(fkrska)
Deadline 2023-06-12
Rich Megginson 2023-06-12 19:22:28 UTC Flags needinfo?(ptoscano)
Pino Toscano 2023-06-26 08:56:55 UTC Doc Text .The `rhc` system role fails on already registered systems when `rhc_auth` contains activation keys

Executing playbook files on already registered systems fails if activation keys are specified for the `rhc_auth` parameter. To workaround this issue, do not specify activation keys when executing the playbook file on the already registered system.
Cause:
The `rhc` system role did not properly handle the case when the `rhc_auth` parameter contained activation keys, and the system was already registered.

Consequence:
Executing playbook files on already registered systems failed if activation keys were specified for the `rhc_auth` parameter.

Fix:
The `rhc` system role was fixed to handle all the types of credentials in all the cases.

Result:
Executing playbook files on already registered systems works fine, no matter which kind of credentials are specified using the `rhc_auth` parameter.
Doc Type Known Issue Bug Fix
Flags needinfo?(ptoscano)
Sagar Dubewar 2023-07-05 08:15:39 UTC Doc Text Cause:
The `rhc` system role did not properly handle the case when the `rhc_auth` parameter contained activation keys, and the system was already registered.

Consequence:
Executing playbook files on already registered systems failed if activation keys were specified for the `rhc_auth` parameter.

Fix:
The `rhc` system role was fixed to handle all the types of credentials in all the cases.

Result:
Executing playbook files on already registered systems works fine, no matter which kind of credentials are specified using the `rhc_auth` parameter.
.The `rhc` system role no longer fails on the registered systems when `rhc_auth` contains activation keys

Previously, a failure occurred when you executed playbook files on the registered systems with the activation key specified in the `rhc_auth` parameter. This issue has been resolved. It is now possible to execute playbook files on the already registered systems, even when activation keys are provided in the `rhc_auth` parameter.
Oneata Mircea Teodor 2023-07-07 09:20:09 UTC Keywords ZStream
CC toneata

Back to bug 2186218