Skip to content
This repository has been archived by the owner on May 9, 2022. It is now read-only.

Improve failure handling #17

Open
4 tasks
wgwoods opened this issue Oct 9, 2013 · 2 comments
Open
4 tasks

Improve failure handling #17

wgwoods opened this issue Oct 9, 2013 · 2 comments

Comments

@wgwoods
Copy link
Contributor

wgwoods commented Oct 9, 2013

Basically, when the system crashes, we should probably display an error message and tell the user how boned they are, and let them choose between a shell and rebooting.

More specifically - if the upgrade-prep service fails, we should:

  • print a message about the failure
  • log failure to /var/log/upgrade.log
  • do the "root password for debugging or reboot" prompt
  • reboot if no activity after ~60 sec
@wgwoods
Copy link
Contributor Author

wgwoods commented Oct 9, 2013

@wgwoods wgwoods removed this from the 0.9.0 milestone Oct 13, 2014
@wgwoods
Copy link
Contributor Author

wgwoods commented Oct 29, 2014

We might also want fedup to provide info about failures via fedup status or fedup log - see #51 for more thoughts on commandline/workflow stuff.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant