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:

virt-sysprep's cron-spool operations removes /var/spool/at/.SEQ . .SEQ contains at job counter (5 digit hex)
/var/spool/at]$ cat .SEQ 
00001

# virt-sysprep --list-operations
..
cron-spool * Remove user at-jobs and cron-jobs

Removing this file results in that at can not be used afterwards without manual create of this file:

[root@localhost /var/spool/at]$ at now + 1 minute
Cannot open lockfile /var/spool/at/.SEQ: No such file or directory

.SEQ file needs to be recreated to fix this. We should reset the counter manually by changing the /var/spool/at/.SEQ file to 00000, or recreate after deleted by virt-sysprep.

Version-Release number of selected component (if applicable):
* libguestfs-tools-c-1.20.11-11.el6.x86_64
* # virt-sysprep -V
virt-sysprep 1.20.11

How reproducible:
always

Steps to Reproduce:
1. [root@localhost /var/spool/at]$ rm -f .SEQ 
2. [root@localhost /var/spool/at]$ at now + 1 minute
Cannot open lockfile /var/spool/at/.SEQ: No such file or directory

Actual results:
[root@localhost /var/spool/at]$ at now + 1 minute
Cannot open lockfile /var/spool/at/.SEQ: No such file or directory

Expected results:
at works without manual action after virt-sysprep

Additional info:

Fixed upstream with:
775e68c4613fabaa3b48ea3dc8d45ac74b93682b (minor refactoring)
a614f3451d1e2cc4f29b1bc7f0d88519c432b2c8 (minor refactoring)
261be1f952aa984b460ff8d88d962c490df4ffcf

Verified with the packages:
libguestfs-1.20.11-16.el6.x86_64
libguestfs-tools-c-1.20.11-16.el6.x86_64
# virt-sysprep -V
virt-sysprep 1.20.11


Verify steps:
1. # cd  /var/spool/at/

2.# cat .SEQ
00001

3. # virt-sysprep --list-operations
abrt-data * Remove the crash data generated by ABRT
bash-history * Remove the bash history in the guest
blkid-tab * Remove blkid tab in the guest
......

4. # at now +1 minute
at>

No error occurs.


So verified.

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, 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://rhn.redhat.com/errata/RHBA-2016-0762.html