Bug 2186218 - RHC system role: activation key registration fails if system is already registered [NEEDINFO]
Summary: RHC system role: activation key registration fails if system is already regis...
Keywords:
Status: VERIFIED
Alias: None
Deadline: 2023-06-12
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 9.3
Assignee: Pino Toscano
QA Contact: Jakub Haruda
Sagar Dubewar
URL:
Whiteboard: role:rhc
Depends On:
Blocks: 2186908 2186913 2214282
TreeView+ depends on / blocked
 
Reported: 2023-04-12 12:47 UTC by Brian Smith
Modified: 2023-07-07 09:20 UTC (History)
10 users (show)

Fixed In Version: rhel-system-roles-1.22.0-0.6.el9
Doc Type: Bug Fix
Doc Text:
.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.
Clone Of:
: 2186908 2214282 (view as bug list)
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:
rmeggins: needinfo? (pkettman)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles rhc issues 90 0 None closed Activation key registration fails if system is already registered 2023-04-15 07:11:11 UTC
Github linux-system-roles rhc pull 92 0 None Merged Do not pass fake creds when activation keys are specified 2023-04-15 07:11:12 UTC
Red Hat Issue Tracker RHELPLAN-154529 0 None None None 2023-04-12 12:59:13 UTC

Description Brian Smith 2023-04-12 12:47:31 UTC
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.

Comment 1 Brian Smith 2023-04-12 12:48:26 UTC
See also:  https://github.com/linux-system-roles/rhc/issues/90


Note You need to log in before you can comment on or make changes to this bug.