RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2186218 - RHC system role: activation key registration fails if system is already registered
Summary: RHC system role: activation key registration fails if system is already regis...
Keywords:
Status: CLOSED ERRATA
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: 2024-03-07 04:25 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: 2023-11-07 08:29:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:


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
Red Hat Product Errata RHEA-2023:6390 0 None None None 2023-11-07 08:30:09 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

Comment 20 errata-xmlrpc 2023-11-07 08:29:39 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:6390

Comment 21 Red Hat Bugzilla 2024-03-07 04:25:40 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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