Bug 690742

Summary: anaconda / kickstart install crashes with undefined symbol: uuid_generate
Product: [Fedora] Fedora Reporter: robb <redzilla>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: akozumpl, anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-25 11:36:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
kickstart config file used for the installation process none

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 ***