Bug 1377136

Summary:	Updating from FC22 to FC25, brings the system to a unusable login window
Product:	[Fedora] Fedora	Reporter:	David Hill <dhill>
Component:	dnf-plugins-extras	Assignee:	rpm-software-management
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	25	CC:	dhill, dmach, ignatenko, jkadlcik, jmracek, mblaha, rpm-software-management, vmukhame, wwoods, zbyszek
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:	2017-11-30 07:02:31 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:

Description David Hill 2016-09-18 22:59:52 UTC

Description of problem:
Updaing from FC22 to FC25 brings the system to an unusable login window .  I could type the username/password but then would be brought back to the login window after a short time with a black screen.   I've managed to gain access to the console and was able to update to latest FC25 which solved the problem.   I was wondering if this is the expected behavior or if DNF should have updated to the latest FC25 from the beginning.

Version-Release number of selected component (if applicable):
Latest

How reproducible:
Always

Steps to Reproduce:
1. Install FC22
2. Update to FC25
3. Try to login

Actual results:
Goes back to login windows

Expected results:
Logs in

Additional info:
Shouldn't DNF also use the "updates" repository and update to latest?

Comment 1 Zbigniew Jędrzejewski-Szmek 2016-11-29 02:19:20 UTC

N+3 upgrades (i.e. skipping two versions) are not officially supported. They should usually work, but aren't systematically tested, and when things break, you're on your own. Unless you changed the default configuration, "updates" repository should be enabled and system-upgrade should install packages from there. If it didn't, it's most likely because of some conflict between packages that made a single-step upgrade impossible, but was somehow solved by the two-step upgrade (with the second part done manually by you). If you have the dnf history for both upgrades, we can maybe figure out what happened.

Comment 2 Fedora End Of Life 2017-11-16 19:28:31 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Marek Blaha 2017-11-30 07:02:31 UTC

N+3 upgrades are not supported.