Bug 1575211

Summary:	SNAFU guide for interrupted upgrades
Product:	[Fedora] Fedora	Reporter:	Anatoli Babenia <anatoli>
Component:	dnf-plugins-extras	Assignee:	rpm-software-management
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	dmach, extras-orphan, jkadlcik, jmracek, mhatina, rpm-software-management, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-07 11:22:21 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:

Description Anatoli Babenia 2018-05-05 06:21:02 UTC

Description of problem:
The more people use Fedora, the more chances that something happens during upgrade - power can be shut off, or hdd may fail or whatever. The result is - system boots with errors and you can not do anything.

How reproducible:
Easily

Steps to Reproduce:
1.Get previous version of Fedora
2.Start upgrade
3.Pull out electric plug

Actual results:
https://ask.fedoraproject.org/en/question/120596/boot-hangs-after-power-failure-during-system-upgrade/

Expected results:
Page to direct people to.

Comment 1 Martin Hatina 2018-05-07 11:22:21 UTC

DNF is not able to guess what happened and direct you to proper web page. It is on the user to look for solution, because they have more information than DNF has, at least in 'catastrophic' situation like you described.

Comment 2 Anatoli Babenia 2018-05-07 23:23:30 UTC

Sorry for not being clear enough, but this is a feature request for documentation for dnf upgrade process, not about implementing smart logic in dnf itself. Users will look for solution and even could provide their own (if wiki edits are allowed for general public).