Bug 690742 - anaconda / kickstart install crashes with undefined symbol: uuid_generate
Summary: anaconda / kickstart install crashes with undefined symbol: uuid_generate
Keywords:
Status: CLOSED DUPLICATE of bug 684742
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 09:41 UTC by robb
Modified: 2011-03-25 11:36 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-25 11:36:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
kickstart config file used for the installation process (4.11 KB, application/octet-stream)
2011-03-25 09:41 UTC, robb
no flags Details

Description robb 2011-03-25 09:41:03 UTC
Created attachment 487512 [details]
kickstart config file used for the installation process

During a PXE / kickstart installation of fedora 15 alpha, the anaconda installer crashes shortly after startup with python stacktrace ending in an undefined symbol error: uuid_generate

This error doesn't seem to get logged anywhere, but fwiw I copy some of it here from the console screen:
...
  File "/usr/sbin/anaconda", line 509 in <module>
      From pyanaconda import kickstart
  ...
      import cryptsetup
  ImportError: /lib64/libcryptsetup.so.1: undefined symbol: uuid_generate, version UUID_1.0
install exited abnormally [1/1]

At this point the installation process only offers the option to reboot.

This is anaconda 15.22

The same installation process with fedora 14 does not suffer this problem (it fails later with a different, unrelated, error :-().

I've attached my ks config file, though I don't think it really gets this far. Changing the /home volume to be non-encrypted didn't bring about any improvement.

Comment 1 Ales Kozumplik 2011-03-25 11:36:33 UTC

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


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