Bug 1305287 - If dependencies for install are not met, anaconda aborts the install process at install rather than during selection
If dependencies for install are not met, anaconda aborts the install process ...
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-06 13:05 EST by stan
Modified: 2016-02-08 12:43 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-08 12:20:43 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description stan 2016-02-06 13:05:56 EST
Description of problem:
When using BFO, https://boot.fedoraproject.org/index, to install rawhide, (future f24) everything works fine for custom configuring of partitions and choosing packages to install.  Though I note that the problem of having to format existing swap still exists.  I tell anaconda to start the install, it asks for a root password, and once that is done the actual install starts.  But rawhide is very inconsistent, and when dependencies aren't met, it just bails with a message about the inconsistency.  I think it should check the add-on packages for inconsistencies before it gets to that step, the same way it checks the base package.  When there was a problem with minimal install because a library had changed and wget was no longer available, it immediately informed me.  But when I tell it to add other package selections from the right hand panel, it doesn't check them until after the root password is entered.  If it checked on selection, I could uncheck them for the install before the problem arose.

If that isn't possible, it would be good if it allowed a return to the package selection page, so different packages could be selected to try to work around the problem.

Version-Release number of selected component (if applicable):
The latest version of anaconda provided by a pxe boot to install rawhide using BFO.

How reproducible:
Every time there is a dependency error.

Steps to Reproduce:
1.  Try to install rawhide using BFO
2.  Error in dependencies of packages selected

Actual results:
Install aborts.

Expected results:
Would prefer ability to return to selection screen, or checking for dependency errors before install starts and aborts.

Additional info:

The error message for a failed dependency in the minimal package was something like 'error checking packages'.  Which can be interpreted in more than one way.  Perhaps it could be changed to 'error found while checking packages' for failures, and 'checking selected packages for errors' during consistency checking.
Comment 1 David Shea 2016-02-08 08:03:29 EST
Please attach the logs from /tmp to this bug as individual, text/plain attachments.
Comment 2 stan 2016-02-08 11:55:29 EST
I'd like to, but this was using BFO.  There is no permanent installation.  It lets me know that unless I send the logs to a remote site, or report via bugzilla, everything is gone once I quit.

I don't remember my bugzilla password.  From now on I'll write it down before I start.

Have you got any suggestions about how to access the information you request that I am missing?

I've been unable to get back to this error, since it changed the status of the partitions I want to install to, from Fedora 20 to unknown linux, and I am now getting a different error from anaconda when trying to configure them.  I will be opening a separate bugzilla for those errors.
Comment 3 David Shea 2016-02-08 12:20:43 EST
The only thing different about BFO is where the installation media comes from. Otherwise the install is exactly the same as if you had used a boot ISO.

At the time of the error, you can switch to a shell by hitting Ctrl+Alt+F2, and you can copy the logs out of the installation environment from there. If you do encounter an error dialog that offers to report a bug, using that would be ideal.
Comment 4 stan 2016-02-08 12:36:08 EST
"you can copy the logs out of the installation environment from there"

But copy them *where*?  Do I have access to a permanent system from the boot?  Is it a functioning linux setup where I can mount my functioning systems?  Is it like a rescue environment where I can mount under sysimage?  Can you point me to documentation on what to do?
Comment 5 David Shea 2016-02-08 12:43:51 EST
It's a shell in the stage2 installer environment, so it has everything that is available in the rescue environment. You can mount filesystems (including those on external devices), or use a network utility such as ftp, scp, or fpaste to copy the logs to another system.

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