Release Engineering

Tasklist

FS#16274 - aif fails with unhelpful message when no net connection

Attached to Project: Release Engineering
Opened by Felix (thetrivialstuff) - Sunday, 20 September 2009, 03:29 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Saturday, 06 March 2010, 12:01 GMT
Task Type Bug Report
Category AIF
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 2009.08
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Attempting to install arch with the new aif system on 2009.08 netinstall CD, doing a net install. I forgot to turn on eth0 and give it an IP address; aif said:

WARNING: installation failed (see errors below)
error: 'openssh': not found in sync db
openssh package not found, searching for group...
Package installation FAILED
(above three lines repeat twice)

aif then tried to continue the rest of the installation anyway, which of course completely failed. At the end it printed:

Execution report:
Phase preparation: Success
Phase basics: Success
Phase system: Success
Phase finish: Success

Which is somewhat inaccurate.

The debug log (when I specified -d) provided no more information about the problem. What happens to the output of pacman, sfdisk, and all of those commands?

Recommended fix:

- No need to add extra routines to diagnose whether the network is up, etc. -- just print the output of pacman to stdout and the hundreds of "cannot connect" lines will clue the user in to this particular problem.
- Abort the entire procedure if there's a failed step. In some cases continuing could be catastrophic (e.g. if a partition table edit failed and the script goes ahead with mkfs).
- I would also like to see the output of the partitioning and mkfs commands. I really hope -f isn't specified by default on any of them, and that a failed filesystem creation will abort the entire procedure. That just seems like a sane safety feature.
This task depends upon

Closed by  Dieter Plaetinck (Dieter_be)
Saturday, 06 March 2010, 12:01 GMT
Reason for closing:  Duplicate
Comment by Felix (thetrivialstuff) - Sunday, 20 September 2009, 03:31 GMT
Sorry, aif is actually in extra, not core.
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 20 September 2009, 23:06 GMT
  • Field changed: Attached to Project (Arch Linux → Release Engineering)
"Release Engineering" project is more apropiate for this.
Comment by Dieter Plaetinck (Dieter_be) - Wednesday, 11 November 2009, 11:50 GMT
patches welcome
Comment by Dieter Plaetinck (Dieter_be) - Saturday, 06 March 2010, 12:01 GMT
This ticket is a duplicate of:
 FS#15906  - Selecting package crashes setup if network not set
 FS#15854  - package installation fails, yet it thinks all is good

We actually do mkfs -f for xfs filesystems, not for others. it's up to the users to tell aif what to do. if users tells aif to overwrite a filesystem, aif will do that. that's how it _should_ behave.

Loading...