redhat-config-kickstart will not open a recently created kickstart file
Server (and Generation): All
Steps to reproduce:
1) Install Red Hat 9.0 Beta 5 (grub/everything)
3) Create a ks.cfg and save the file in /tmp
4) Click "File" and then "Open File"
5) Select the file you created and saved and click "OK"
6) Notice error messages
[root@ml350r5 root]# redhat-config-kickstart
Traceback (most recent call last):
File "/usr/share/redhat-config-kickstart/kickstartGui.py", line 255, in
File "/usr/share/redhat-config-kickstart/kickstartGui.py", line 286, in fillData
File "/usr/share/redhat-config-kickstart/basic.py", line 303, in fillData
UnboundLocalError: local variable 'iter' referenced before assignment
uname -r output: n/a
Is the issue reproducible? yes.
Action by: Bryan.Leopard
ISSUE TRACKER 16155 opened by HP as sev 2
Can you attach the kickstart file?
It will happen on any kickstart config that has a langsupport line like
Attached patch fixes
Created attachment 90301 [details]
patch to fix traceback
Patch applied. Should be fixed in redhat-config-kickstart-2.3.6-4. Thanks katzj.
FROM ISSUE TRACKER
Event posted 03-10-2003 12:29pm by Bryan.Leopard with duration of 0.00
Not fixed in beta 5.
Beta 5 contained redhat-config-kickstart-2.3.6-2. The latest tree contains
redhat-config-kickstart-2.3.6-4, which should fix the problem.
FROM ISSUE TRACKER
Event posted 03-25-2003 03:50pm by Bryan.Leopard with duration of 0.00
Still a problem in the GM product.
There are a bunch of inconsistencies in the GUI generated configuration file:
1. anaconda generated anaconda-ks.cfg includes "=" in --size=XXX
GUI generated ks.cfg files do not have this
2. The GUI will REQUIRE "=" in --server and --dir settings
3. The GUI creates swap space with a --fstype entry but with no specified type.
This prevents the kickstart file from being used during an install...
Failure to include the "=" in step 2 will prevent the GUI from opening the file.
bcl: please open a new bug with the problem you are seeing since it does not
appear to be related to the original bug reporter's issue.
I can not duplicate this problem with RHL 9. If you are still seeing this
behavior, please reopen this bug and attach the kickstart file that
redhat-config-kickstart is crashing on. Otherwise, I don't have a reproducible