Bug 1016522

Summary:	upgrade.log is empty
Product:	[Fedora] Fedora	Reporter:	Martin Krizek <mkrizek>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	kparal, tflink, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-13 15:44:25 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 Martin Krizek 2013-10-08 10:11:30 UTC

Description of problem:
After upgrading F19 to F20 using fedup-cli, /var/log/upgrade.log is empty. Both /var/log/upgrade.log and /var/log/upgrade.log.old existed before running the upgrade. /var/log/upgrade.log.old contains previous /var/log/upgrade.log (which is correct) after the upgrade.

Version-Release number of selected component (if applicable):
fedup-0.7.3-7

How reproducible:
Always

Steps to Reproduce:
1. both /var/log/upgrade.log and /var/log/upgrade.log.old exist
2. run fedup-cli and reboot
3. run upgrade item from grub

Actual results:
/var/log/upgrade.log is empty. Previous /var/log/upgrade.log is successfuly moved to /var/log/upgrade.log.old

Expected results:
/var/log/upgrade.log contains information about the upgrade.

Additional info:

Comment 1 Kamil Páral 2013-10-08 11:55:58 UTC

I can confirm this bug.

Comment 2 Kamil Páral 2013-10-09 11:16:41 UTC

I've found out that upgrade.log is empty _always_. So you can disregard comment 0, there is simply no contents in any case.

Comment 3 Fedora End Of Life 2015-01-09 20:09:36 UTC

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

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 19 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 4 Kamil Páral 2015-01-13 15:44:03 UTC

This is fixed when upgrading F20 -> F21.