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.
Description of problem:
RHEL 7 Atomic kickstart has this:
echo "Removing random-seed so it's not the same in every image."
rm -f /var/lib/random-seed
But in fact the random-seed is at /var/lib/systemd/random-seed, thus all Atomic images currently share the same seed.
Version-Release number of selected component (if applicable):
7.3.2
Hm. The path is indeed incorrect. However, I can't find the random seed in the current gold RHELAH cloud image.
```
# env LIBGUESTFS_BACKEND=direct guestmount --ro -a rhel-atomic-cloud-7.3.2-1.x86_64.qcow2 -m /dev/mapper/atomicos-root /mnt/guestfs/
# find /mnt/guestfs/ -name 'random-seed'
#
```
And the same for current Fedora Atomic Host. Maybe something else is deleting it?
Did you actually *observe* the random seed being identical, or were you just reading the kickstart?
(In reply to Colin Walters from comment #1)
>
> Did you actually *observe* the random seed being identical, or were you just
> reading the kickstart?
Yeah, I merely trusted the documentation :) So looks like a false positive.
> And the same for current Fedora Atomic Host. Maybe something else is
> deleting it?
I assume you are not using virt-sysprep(1) to clean up the given that there are some leftover installation time files under /root and /tmp, that would have been one possible explanation.
Thanks.
I booted two instances of the latest cloud image (rhel-atomic-cloud-7.3.4-11.x86_64.qcow2) corresponding to RHELAH 7.3.4-1 and then compared sha256 checksums of the '/var/lib/systemd/randomseed' file.
$ ssh 192.168.122.55
Warning: Permanently added '192.168.122.55' (ECDSA) to the list of known hosts.
[cloud-user@atomichost ~]$ sudo sha256sum /var/lib/systemd/random-seed
c047d4f6d5c5e52a5c2b5aad67348bac172b92b30b997d46df072355820d3df2 /var/lib/systemd/random-seed
$ ssh 192.168.122.236
Warning: Permanently added '192.168.122.236' (ECDSA) to the list of known hosts.
[cloud-user@atomichost ~]$ sudo sha256sum /var/lib/systemd/random-seed
ec03970f47fb769374aa02f5afc4a42b02ae26912606b3dbe0c8cdcefba9ccf0 /var/lib/systemd/random-seed
Based on Colin's comment in #1 and these observations, I am going to close this.