Bug 2186908

Summary:	RHC system role: activation key registration fails if system is already registered
Product:	Red Hat Enterprise Linux 8	Reporter:	Rich Megginson <rmeggins>
Component:	rhel-system-roles	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	unspecified	Docs Contact:	Sagar Dubewar <sdubewar>
Priority:	high
Version:	8.9	CC:	briasmit, cdonnell, djez, fkrska, jharuda, pkettman, ptoscano, rhel-cs-system-management-subsystem-qe, rmeggins, spetrosi, vdanek
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	8.9	Flags:	fkrska: needinfo+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	role:rhc
Fixed In Version:	rhel-system-roles-1.22.0-0.6.el8	Doc Type:	Known Issue
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.	Story Points:	---
Clone Of:	2186218
Clones:	2186913 2214283 (view as bug list)		Environment:
Last Closed:	2023-11-14 15:31:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2186218
Bug Blocks:	2186913, 2214283
Deadline:	2023-05-22

Description Rich Megginson 2023-04-14 19:47:06 UTC

+++ This bug was initially created as a clone of Bug #2186218 +++

Description of problem:
I'm using the rhc system role to register a system using an activation key. When I run the playbook the first time, it succeeds and successfully registers the system.

If I run the playbook again, it fails the second time with an error.

Version-Release number of selected component (if applicable):
RHEL system roles 1.21.1 release from Automation Hub.  

How reproducible:
Every time

Steps to Reproduce:
1.  Run playbook:

- name: Run system roles
  hosts: all
  become: true
  tasks: 
    - name: run rhc system role
      include_role:
        name: redhat.rhel_system_roles.rhc
      vars:
        rhc_state: present
        rhc_auth:
          activation_keys:
            keys: 
              - "<redacted>"
        rhc_organization: "<redacted>"

2. Playbook is successful 
3. Run same playbook again

Actual results:
The second time, the playbook fails:

TASK [redhat.rhel_system_roles.rhc : Call subscription-manager] **********************************************************************************************
fatal: [rhel8-server2.example.com]: FAILED! => {"changed": false, "msg": "parameters are mutually exclusive: activationkey|username"}

Expected results:
Playbook doesn't fail when run again.

--- Additional comment from Brian Smith on 2023-04-12 12:48:26 UTC ---

See also:  https://github.com/linux-system-roles/rhc/issues/90

Comment 15 errata-xmlrpc 2023-11-14 15:31:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:6946

Comment 16 Red Hat Bugzilla 2024-03-14 04:25:36 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days