Bug 1414329

Summary:	preupg suggests me to backup my system but it does not actually do any upgrade
Product:	Red Hat Enterprise Linux 6	Reporter:	Branislav Blaškovič <bblaskov>
Component:	preupgrade-assistant	Assignee:	Michal Bocek <mbocek>
Status:	CLOSED ERRATA	QA Contact:	Alois Mahdal <amahdal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.9	CC:	jmazanek, ovasik, phracek
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	preupgrade-assistant-2.3.2-1.el6	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 12:10:23 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:

Comment 2 Alois Mahdal 2017-01-19 21:05:30 UTC

Nice catch, +1 from me on this.

Indeed, preupg should not alter your system in any way; its job is solely to scan your system and create an "upgrade package": report plus some files.  You can run the scan as many times as you wish.

Comment 3 Michal Bocek 2017-02-21 22:48:05 UTC

Resolved by upstream commit https://github.com/upgrades-migrations/preupgrade-assistant/commit/f914a61304bbb87e64ad3605eb7d83ea72ba1a90

Comment 5 Alois Mahdal 2017-03-09 20:45:13 UTC

preupgrade-assistant-2.3.3-1.el6:

    # preupg 
    The Preupgrade Assistant is a diagnostics tool 
    and does not perform the actual upgrade.
    Do you want to continue? [Y/n]
    y
    Gathering logs used by the Preupgrade Assistant:
    All installed packages                                 : 01/10 ...finished (time 00:00s)
    All changed files                                      : 02/10 ...running
    [...]

The message still appears at the bottom of the report, but at least does not look like it has anything to do with the y/n confirmation.

Comment 7 errata-xmlrpc 2017-03-21 12:10:23 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0819.html