Bug 920764 - livemedia-creator fails to make an ISO image using --novirt
Summary: livemedia-creator fails to make an ISO image using --novirt
Status: CLOSED DUPLICATE of bug 906031
Alias: None
Product: Fedora
Classification: Fedora
Component: lorax
Version: 18
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2013-03-12 17:08 UTC by D. Marlin
Modified: 2013-04-26 21:25 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-04-26 21:25:19 UTC


Attachments (Terms of Use)
log of livemedia-creator run, with traceback. (3.25 KB, text/x-log)
2013-03-12 17:08 UTC, D. Marlin
no flags Details

Description D. Marlin 2013-03-12 17:08:19 UTC
Created attachment 709080 [details]
log of livemedia-creator run, with traceback.

Description of problem:

When using livemedia-creator in --novirt mode to make an ISO image, it fails with a traceback (see attached).


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

  anaconda-18.37.12-1.fc18.x86_64
  lorax-18.31-1.fc18.x86_64


How reproducible:

  Consistently


Steps to Reproduce:
1.  install/update to the anaconda and lorax versions specified
2.  run livemedia-creator:

  livemedia-creator \
    --no-virt --make-iso \
    --ks=./F18-test.ks

3.
  
Actual results:

A traceback occurs indicating an error:

  Error: Error accessing file for config file:///tmp/anaconda-yum.conf


Expected results:

ISO is created with no errors.


Additional info:

The command was run as 'root' and SELinux was disabled.

The file in question does exist:

  -rw-r--r-- 1 root root  325 Mar 12 11:33 /tmp/anaconda-yum.conf

After the error occurs, the process does not appear to terminate, even after being interrupted with Ctrl-C.

Comment 1 Brian Lane 2013-04-26 21:25:19 UTC
This was actually a curl problem.

*** This bug has been marked as a duplicate of bug 906031 ***


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