Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
.The `kdump` role adds `authorized_keys` idempotently
Previously, the task to add `authorized_key` added an extra newline character every time. Consequently the role was not acting idempotent. With this fix, adding a new `authorized_key` works correctly and adds only a single key value idempotently.
Description of problem:
The "Write new authorized_keys if needed" task does not appear to be idempotent. When running the kdump role against a single host for a second time, it will report a change for this task, and the authorized_keys file will end up with a duplicate entry.
When running the kdump role against 2 hosts, each time the role is run, it will alternate showing a change on one host, and on the next run, the other host. The host that reports a change will have a duplicate entry in the authorized_keys file
Version-Release number of selected component (if applicable):
rhel-system-roles-1.21.1-1.el9_2.noarch
How reproducible:
Every time
Steps to Reproduce:
1. From my controlnode (rhel9-controlnode.example.com) use this inventory file and run the kdump system role several times:
all:
hosts:
rhel9-server1.example.com:
rhel9-server2.example.com:
vars:
kdump_target:
type: ssh
location: kdump.com
kdump_path: "/home/kdump/crash"
kdump_sshkey: "/root/.ssh/kdump_id_rsa"
kdump_ssh_user: kdump
kdump_ssh_server: rhel9-controlnode.example.com
Actual results:
After the initial run, subsequent runs of the role report a change on the "Write new authorized_keys if needed" task, alternating each time between showing the change on rhel9-server1.example.com and rhel9-server2.example.com. The host that reports a change will have a duplicate entry in the authorized_keys file
Expected results:
This task is idempotent and does not report changes on subsequent runs. Entries are not duplicated in the authorized_keys file.
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
Description of problem: The "Write new authorized_keys if needed" task does not appear to be idempotent. When running the kdump role against a single host for a second time, it will report a change for this task, and the authorized_keys file will end up with a duplicate entry. When running the kdump role against 2 hosts, each time the role is run, it will alternate showing a change on one host, and on the next run, the other host. The host that reports a change will have a duplicate entry in the authorized_keys file Version-Release number of selected component (if applicable): rhel-system-roles-1.21.1-1.el9_2.noarch How reproducible: Every time Steps to Reproduce: 1. From my controlnode (rhel9-controlnode.example.com) use this inventory file and run the kdump system role several times: all: hosts: rhel9-server1.example.com: rhel9-server2.example.com: vars: kdump_target: type: ssh location: kdump.com kdump_path: "/home/kdump/crash" kdump_sshkey: "/root/.ssh/kdump_id_rsa" kdump_ssh_user: kdump kdump_ssh_server: rhel9-controlnode.example.com Actual results: After the initial run, subsequent runs of the role report a change on the "Write new authorized_keys if needed" task, alternating each time between showing the change on rhel9-server1.example.com and rhel9-server2.example.com. The host that reports a change will have a duplicate entry in the authorized_keys file Expected results: This task is idempotent and does not report changes on subsequent runs. Entries are not duplicated in the authorized_keys file.