Bug 1736804 - appliance-creator should abort early instead of wipe output image and --cache
Summary: appliance-creator should abort early instead of wipe output image and --cache
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: appliance-tools
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2019-08-02 05:17 UTC by Warren Togami
Modified: 2019-09-15 18:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
original-ks.cfg (2.54 KB, text/plain)
2019-08-02 05:20 UTC, Warren Togami
no flags Details

Description Warren Togami 2019-08-02 05:17:20 UTC
Description of problem:
I previously used appliance-creator with Fedora 24 armhfp with similar command line options. Now it succeeds with Fedora 30 aarch64 but with two problems.

# appliance-creator -c /root/kickstarts/original-ks.cfg \
                  -d -v --logfile /tmp/appliance.log    \
                  --cache /var/cache/pkgcache           \
                  -o app-output --format raw --name fedora30image
...

moving disks to stage location
writing image XML to /var/tmp/imgcreate-p1z0virl/out/fedora30image.xml
creating destination dir: app-output/fedora30image
moving /var/tmp/imgcreate-p1z0virl/out/fedora30image.xml to app-output/fedora30image/fedora30image.xml
Finished

Problem #1 the specified --cache directory contains RPMS during the build but is is wiped empty afterward.

Problem #2 the -o output image is missing after the build. The specified -o directory contains only that .xml file.


Version-Release number of selected component (if applicable):
appliance-tools-009.0-5.fc30.noarch

Comment 1 Warren Togami 2019-08-02 05:20:46 UTC
Created attachment 1599489 [details]
original-ks.cfg

kickstart copied from Fedora-Minimal-30-1.2.aarch64.raw.xz

Comment 2 Ben Cotton 2019-08-13 17:06:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 3 Ben Cotton 2019-08-13 18:36:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 4 Warren Togami 2019-09-15 18:57:24 UTC
The real bug here is appliance-creator will happily install a chroot without any storage defined, declare success then delete it. Perhaps appliance-creator should detect that no storage was defined and abort early?


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