Bug 589522
Summary: | KickstartValueError: The following problem occurred on line 22 of the kickstart file: Specified nonexistent disk sda in partition command | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Pavel Holica <pholica> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 6.0 | ||||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-05-10 14:20:47 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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 582286 | ||||||||
Attachments: |
|
Description
Pavel Holica
2010-05-06 11:18:40 UTC
*** Bug 589525 has been marked as a duplicate of this bug. *** Does sda exist? Please attach /tmp/syslog and /tmp/storage.log. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Created attachment 412841 [details]
storage.log
No, sda doesn't exist.
Created attachment 412842 [details]
syslog
Then this is functioning as designed - kickstart is more strict now in what it will accept, and referring to a disk that does not exist is no longer accepted. I understand thad installation shouldn't continue. But problem is, that this is traceback and user shouldn't see any traceback. Please correct me if I'm wrong. It doesn't really matter here whether it's a traceback or not. You still see the real error message, and the installation was going to halt right then anyway. Functionally, there's no real difference between what you got and what you wanted to have. I don't think there's really a need to work on handling that and redisplaying it in a slightly different format. |