Bug 251944 - Traceback possibly when running %pre script
Summary: Traceback possibly when running %pre script
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-13 16:09 UTC by Orion Poplawski
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-08-14 15:47:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
kickstart script (7.11 KB, text/plain)
2007-08-14 15:14 UTC, Orion Poplawski
no flags Details

Description Orion Poplawski 2007-08-13 16:09:46 UTC
Description of problem:

Get the following traceback doing a PXE/kickstart install (rest has scrolled off
the screen):

File "/usr/lib/python2.5/subprocess.py", line 593, in __init__
  errread, errwrite)
File "/usr/lib/python2.5/subprocess.py", line 1079, in _execute_child
  raise child_exception
TypeError: coercing to Unicode: need string or buffer, NoneType found

Last vt3 message:

INFO: Running kickstart %%pre script(s)

%pre script:
#!/usr/bin/sh
#Debugging
set -x

Comment 1 Chris Lumens 2007-08-13 17:06:11 UTC
Please attach the entire traceback message.  It should still be on tty3 in its
entirety, unless it's a really long traceback.

Comment 2 Orion Poplawski 2007-08-13 17:52:24 UTC
It's definitely from executing the %pre script - removing the %pre section
allows it to proceed.

There is no traceback logged on tty3, just the normal anaconda messages, last of
which is the info message I mentioned above.

Comment 3 Chris Lumens 2007-08-14 15:11:29 UTC
Can you attach your complete kickstart script?

Comment 4 Orion Poplawski 2007-08-14 15:14:18 UTC
Created attachment 161273 [details]
kickstart script

Comment 5 Orion Poplawski 2007-08-14 15:47:44 UTC
Works in today's (20070814) rawhide.

Comment 6 Chris Lumens 2007-08-14 15:52:39 UTC
Glad it works, because that was a truly bizarre bug and I wasn't getting much
closer to figuring out what was going on.


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