Bug 208289
Summary: | local variable 'device_is_valid' referenced before assignment | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Alex J. Avriette <avriette> | ||||
Component: | system-config-kickstart | Assignee: | Chris Lumens <clumens> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.4 | CC: | tao | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-09-27 18:24:48 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Alex J. Avriette
2006-09-27 18:00:19 UTC
Created attachment 137234 [details]
this is the "errant" ks.config and associated output
It looks like it doesn't like your raid configuration lines: raid pv.45 --fstype "physical volume (LVM)" --level=RAID1 raid.43 raid.44 raid pv.29 --fstype "physical volume (LVM)" --level=RAID0 raid.27 raid.28 Try changing --level=RAID1 to --level=1 and --level=RAID0 to --level=0 and I think this problem will go away. This is also fixed in Rawhide, and so will be fixed in RHEL5. If you require this fix in an update to RHEL4, please contact your support representative who will raise the issue through the proper channels. Removing RAID from those lines doesn't seem to change the traceback. I'd enclose another copy of the traceback, but it is entirely identical to the traceback from the first (with "RAID" in place on both lines). For what it's worth, when reading in the "new" config (without RAID on those lines), it looks like the S-C-K utility gets a little further, in that it reads a bunch of LVM partitions, but doesn't get as far as assigning mountpoints or formatting to anything. (this, judging from the output of the saved ks.cfg file after reading in the one it couldn't fully parse) I've been going through the utility manually, and I *think* I can get it to do what I want by entering everything through the main interface. I'm not sure which would take longer -- "fixing" my ks.cfg, or going through all the hassle of doing the "disk druid" stuff in system-config-kickstart (whose interface is somewhat lacking by comparison). Any ideas? |