Bug 1561930
| Summary: | kickstart: "clearpart --list" does not work | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Telka <marcel> |
| Component: | anaconda | Assignee: | Jiri Konecny <jkonecny> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | high | Docs Contact: | Sharon Moroney <smoroney> |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | anaconda-maint-list, atodorov, extras-qa, g.kaviyarasu, jkonecny, jonathan, jstodola, linux, marcel, mattmc, mkolman, pasik, smoroney, vanmeeuwen+fedora, vponcova, vslavik |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | anaconda-21.48.22.136-1 | Doc Type: | Bug Fix |
| Doc Text: |
The "clearpart" Kickstart command can now be used on disk partitions
Previously, using the Kickstart command "clearpart --list=<part>" (where <part> is a partition on a disk) during installation worked for disks but not disk partitions.
As a consequence, Anaconda stopped the installation with the message:
Device <part> given in clearpart device list does not exist.
This update removes the restriction and supports clearing on disk partitions.
|
Story Points: | --- |
| Clone Of: | 1410335 | Environment: | |
| Last Closed: | 2018-10-30 07:53:20 UTC | Type: | Bug |
| 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: | 1557360 | ||
|
Description
Marcel Telka
2018-03-29 08:28:18 UTC
Verified with anaconda-21.48.22.143-2.el7.x86_64.rpm, -0724.0 compose. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3035 |