Bug 988860 - virt-sysprep --firstboot option writes incorrect "99" (instead of "S99") sysv-init-style start up script
virt-sysprep --firstboot option writes incorrect "99" (instead of "S99") sysv...
Product: Virtualization Tools
Classification: Community
Component: libguestfs (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard W.M. Jones
Depends On:
Blocks: 988862 988863
  Show dependency treegraph
Reported: 2013-07-26 11:09 EDT by Richard W.M. Jones
Modified: 2013-07-26 11:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 988862 988863 (view as bug list)
Last Closed: 2013-07-26 11:13:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2013-07-26 11:09:30 EDT
Description of problem:

When you use virt-sysprep on a pre-systemd guest (eg. RHEL 6 guest),
with the --firstboot option, it writes a start-up script called


This is of course wrong.  The file should be called


As a result of the incorrect name, the firstboot script does not run.

Version-Release number of selected component (if applicable):

libguestfs 1.20.9, 1.22.4, 1.23.10

Note I have fixed this upstream already:
This bug exists so that I can check the fix goes into RHEL 6 & RHEL 7.

How reproducible:


Steps to Reproduce:

Create a small shell script that "does something useful".  eg.
It could touch a file at a known location.

virt-sysprep --firstboot ./some-script.sh -a RHEL6.guest
Try to boot the guest.

Observe whether or not the firstboot script ran when the
guest booted (eg. was the file touched?)

Additional info:

The bug was found by Nick Strugnell.
Comment 1 Richard W.M. Jones 2013-07-26 11:13:23 EDT
Closing as this bug has already been fixed upstream as
noted in the description.

Note You need to log in before you can comment on or make changes to this bug.