Bug 13682
| Summary: | kickstart doesn't initialize the partition table | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Joshua LeVasseur <jtl> |
| Component: | anaconda | Assignee: | Michael Fulbright <msf> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-07-17 19:52:16 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: | |||
behavior verified ... thanks for the report! Should be fixed in internal development tree. |
The kickstart script refuses to initialize the partition table of a new drive. It reverts to interactive mode to ask the user whether the partition table should be initialized. The kickstart script ignores the 'zerombr yes' command. Solution: In anaconda/text.py, the NewtFstab object initialization forces the zeroMbr parameter to 0 (around source line 207). It should pass todo.zeroMbr as the parameter. Change the line to: todo.fstab = NewtFstab(todo.setupFilesystems, todo.serial, todo.zeroMbr, 0, todo.intf.waitWindow, todo.intf.messageWindow)