Question about asking for help

Robert Knight knight at princeton.edu
Tue Jan 29 23:26:13 UTC 2013


On 1/29/2013 4:39 PM, Dan Horák wrote:
> Robert Knight píše v Út 29. 01. 2013 v 15:50 -0500:
>> On 01/29/2013 12:59 PM, Dan Horák wrote:
>>> Robert Knight píše v Út 29. 01. 2013 v 10:31 -0500:
>>>> At this point, it just sits there forever.
>>> seems my attempt ends with the same messages ...
>>>
>> So, I stuck a user "install" into that kickstart (f18-part.ks) so that I
>> could interact with the install.  While the logs to seem to show that
>> things ended successfully, on the installer screen, I see:
>>
>> Traceback (most recent call last):
>>     File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line
>> 91, in run
>>       threading.Thread.run(self, *args, **kwargs)
>>     File "/usr/lib64/python2.7/threading.py", line 504, in run
>>       self.__target(*self.__args, **self.__kwargs)
>>     File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line
>> 135, in doInstall
>>       writeBootLoader(storage, payload, instClass, ksdata)
>>     File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py",
>> line 2312, in writeBootLoader
>>       storage.bootloader.write()
>>     File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py",
>> line 952, in write
>>       self.install()
>>     File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py",
>> line 2070, in install
>>       message = iutil.reIPL(self.stage1_name)
>>     File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line
>> 892, in reIPL
>>       for disk in anaconda.storage.disks:
>> NameError: global name 'anaconda' is not defined
> hm, same problem as https://bugzilla.redhat.com/show_bug.cgi?id=904245
> that I ascribed to the use of FBA disk originally, but got it today also
> with CKD (all in Hercules). There seems to be a difference between real
> iron and Hercules ...
That just a straight-up defect in the anaconda module iutil.py. There is 
no "anaconda" included.  There are other places where there is 
"storage.disks" in the code, so I'm guessing (and will check some time 
tonight) that removing the "anaconda." prefix will make that failure go 
away.
>
>> wherein it had tried a "chreipl" and it had failed.  I don't believe
>> there's more to do at this point.  lsreipl shows the expected device
>> already set up.  There are two more processes with /mnt/sysimage, one
>> being anaconda and the other bash.
>>
>> I guess I'll try hacking the iutil.py file before things start...
>
The bad news is that when this is fixed, we're going to see "Unable to 
set reIPL device to..."  followed by this: "After shutdown, please 
perform a manual IPL from ... to continue installation.", so that's not 
what's keeping it from booting.

This module on which it appears likely to be stuck is for network 
tracking to make firewalls work, I believe.  Could this just be the 
defect that your replacement initrd corrected?

Regards,
Robert


More information about the s390x mailing list