Created attachment 479173 [details]
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an updates.img. I'm using one provided by the scripts/makeupdates command included in anaconda.git. However, the image referenced in the traceback test case can be used (https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla).
2. Save the image as images/updates.img in the installation source directory
3. Boot the installer with repo=/method= pointing to the server/path that contains the installation source+packages
I'm still seeing a bug that is already confirmed fixed by the updates.img
16:56:22,199 DEBUG loader: in doLoaderMain, step = STEP_KBD
16:56:22,201 DEBUG loader: in doLoaderMain, step = STEP_METHOD
16:56:22,201 DEBUG loader: in doLoaderMain, step = STEP_DRIVER
16:56:22,201 DEBUG loader: in doLoaderMain, step = STEP_NETWORK
16:56:22,221 DEBUG loader: in doLoaderMain, step = STEP_EXTRAS
16:56:22,221 DEBUG loader: in STEP_EXTRAS, method = METHOD_URL
16:56:22,221 DEBUG loader: looking for extras for HTTP/FTP install
16:56:22,221 INFO loader: transferring http://dell-t5400.test.redhat.com/cobblerr
^^^^ it appears to have downloaded the file ...
16:56:22,317 ERR loader: Error mounting /tmp/updates-disk.img: No such file or directory
16:56:22,319 INFO loader: transferring http://dell-t5400.test.redhat.com/cobbler
16:56:22,325 ERR loader: Error downloading http://dell-t5400.test.redhat.com/cobbler/ks_mirror/F-15-Alpha-x86_64/images/product.img: HTTP response code said error
16:56:22,325 INFO loader: Loading SELinux policy
16:56:22,855 INFO loader: getting ready to spawn shell now
16:56:22,855 INFO loader: not spawning a shell
Inspecting /tmp/updates ... it doesn't seem like the symlinks were created as expected:
bash-4.2# find /tmp/updates/
Can you apply http://fpaste.org/wDUo/ to your anaconda git tree, make a new updates.img, put it in the tree, and let me know what gets printed on tty1? I don't really see any differences in the updates= vs. implicit updates code paths in loader that could explain this. I'd like to rule out anything funny happening in anaconda itself.
(In reply to comment #1)
> Can you apply http://fpaste.org/wDUo/ to your anaconda git tree, make a new
> updates.img, put it in the tree, and let me know what gets printed on tty1? I
> don't really see any differences in the updates= vs. implicit updates code
> paths in loader that could explain this. I'd like to rule out anything funny
> happening in anaconda itself.
Running anaconda 15.20, the Fedora system installer - please wait.
checking pkg /tmp/updates/pyanaconda
looking for destination /usr/lib/python2.7/site-packages/pyanaconda
calling symlink_updates(/usr/lib/python2.7/site-packages/pyanaconda, /tmp/updates/pyanaconda)
checking pkg /tmp/updates/anaconda
/tmp/updates/anaconda does not exist
Just to sum up - I was unable to figure out any way this could be happening, and James was unable to reliably reproduce it. I suggest we leave it open a little while longer just in case, but I'm leaning towards a WORKSFORME resolution soon.