Bug 1238579
| Summary: | virt-sysprep at cleanup deletes /var/spool/at/.SEQ which results in failing at | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Richard W.M. Jones <rjones> |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.2 | CC: | huzhan, jherrman, leiwang, linl, mschuppe, ptoscano, tzheng, virt-bugs, wshi |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libguestfs-1.28.1-1.43.el7 | Doc Type: | Release Note |
| Doc Text: |
The "at" program works correctly with virt-sysprep
When using the virt-sysprep utility to create a Red Hat Enterprise Linux guest template, the "at" program in the resulting guest could not be used. This update ensures that virt-sysprep does not delete /var/spool/at/.SEQ files in these guests, and "at" now works as expected.
|
Story Points: | --- |
| Clone Of: | 1229305 | Environment: | |
| Last Closed: | 2015-11-19 07:02:09 UTC | 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: | 1252514 | ||
|
Comment 1
Richard W.M. Jones
2015-07-02 08:09:55 UTC
This is ready to be built, if I can get qa-ack please. Verified with the packages: libguestfs-1.28.1-1.43.el7 Verify steps: 1. # guestfish -a RHEL-Server-7.1-64-hvm.raw -i cat /var/spool/at/.SEQ 00001 2. # virt-sysprep -a RHEL-Server-7.1-64-hvm.raw 3. # guestfish -a RHEL-Server-7.1-64-hvm.raw -i cat /var/spool/at/.SEQ 00000 The /var/spool/at/.SEQ is not removed and the value is set as '00000'. 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-2015-2183.html |