Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696024 - Partition Action should not take place before dep resolution
Summary: Partition Action should not take place before dep resolution
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-04 03:19 UTC by abrouwers
Modified: 2019-04-04 21:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
f30 Kickstart (deleted)
2019-04-04 21:18 UTC, abrouwers
no flags Details

Description abrouwers 2019-04-04 03:19:35 UTC
Description of problem:

When installing F30, I was reusing a disk which contained a root + /home partition.  I had a kickstart file located on /home, and during the install, elected to erase "root," and keep the contents of /home.

My kickstarter file had some unresolvable deps; unfortunately, by the time the installer informed me of this, the root partition was already erased, leaving me with a totally removed / unbootable system.


How reproducible:
100%

Steps to Reproduce:
1. Use KS install with insufficient deps
2. Erase existing F29 install from / partition
3. Get to anaconda dep error, cry

Expected results:
I would expect the installer to have calculated the dependencies prior to erasing the contents of partitions, in the event that there is a problem with the selection.

Comment 1 Martin Kolman 2019-04-04 11:46:27 UTC
(In reply to abrouwers from comment #0)
> Description of problem:
> 
> When installing F30, I was reusing a disk which contained a root + /home
> partition.  I had a kickstart file located on /home, and during the install,
> elected to erase "root," and keep the contents of /home.
> 
> My kickstarter file had some unresolvable deps; unfortunately, by the time
> the installer informed me of this, the root partition was already erased,
> leaving me with a totally removed / unbootable system.
> 
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. Use KS install with insufficient deps
> 2. Erase existing F29 install from / partition
> 3. Get to anaconda dep error, cry
> 
> Expected results:
> I would expect the installer to have calculated the dependencies prior to
> erasing the contents of partitions, in the event that there is a problem
> with the selection.
Hi!

I think we will need to see the kickstart in question - could you attach it (with any sensitive info removed) to the bug report ?

Anaconda supports multiple way how to specify which packages/groups/modules via the %packages section, some of which might require metadata that are only available once the RPM package are actually downloaded once installation is started. Before that Anaconda simply does not have the data it would need to resolve all the dependencies and it could be that you are hitting such a case.

Comment 2 abrouwers 2019-04-04 21:18:32 UTC
Created attachment 1552101 [details]
f30 Kickstart

Comment 3 abrouwers 2019-04-04 21:22:10 UTC
Thanks for the response - I've attached the initial KS file that I had tried.  Essentially, I took an old KS file that I had successfully used around f26 time, and updated it for f30 (using the comps + workstation KS file as a basis).  My goal was essentially a slimmed down gnome install.

(Also, IF the issue was that I was too aggressive in my package removal, it would have been nice of Anaconda to just install items that it needed to complete the install, rather than inform me it couldn't resolve dependencies with the package list).

Given your explanation, is it not possible to do that metadata / dependency resolution BEFORE the partition is reformatted?  If it's unsuccessful for some reason (and, my only option was to abort the install), it's kinda nice to have the existing partitions intact.


Note You need to log in before you can comment on or make changes to this bug.