Bug 2186218
| Summary: | RHC system role: activation key registration fails if system is already registered | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Brian Smith <briasmit> | |
| Component: | rhel-system-roles | Assignee: | Pino Toscano <ptoscano> | |
| Status: | VERIFIED --- | QA Contact: | Jakub Haruda <jharuda> | |
| Severity: | unspecified | Docs Contact: | Sagar Dubewar <sdubewar> | |
| Priority: | high | |||
| Version: | 9.2 | CC: | cdonnell, djez, fkrska, jharuda, pkettman, ptoscano, rmeggins, spetrosi, toneata, vdanek | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | 9.3 | Flags: | rmeggins:
needinfo?
(pkettman) |
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | role:rhc | |||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2186908 2214282 (view as bug list) | Environment: | ||
| Last Closed: | 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: | ||||
| Bug Blocks: | 2186908, 2186913, 2214282 | |||
| Deadline: | 2023-06-12 | |||
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.