Bug 1370530

Summary:	RFE: Detect current Fedora installation and present message about how to do upgrades
Product:	[Fedora] Fedora	Reporter:	Matthew Miller <mattdm>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, rcyriac, sgallagh, vanmeeuwen+fedora, vwcjtblat
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:		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 Matthew Miller 2016-08-26 14:52:15 UTC

I have seen users reports where users assumed that downloading a new ISO and running anaconda was the way to upgrade. We can do some things better on the website and in our documentation to avoid that, but I think it is still likely to happen.

If Anaconda detects an existing Fedora installation, it should present a note explaining that Anaconda doesn't do upgrades, but that upgrades are supported through fedup/dnf system-upgrade.

Comment 1 Stephen Gallagher 2016-08-26 15:00:09 UTC

As an alternate approach (I can file a separate BZ if preferred), Anaconda could regain the ability to perform upgrades by enabling the user to run a copy of `dnf system-upgrade download` in the /mnt/sysimage and then tell the user to reboot to apply the changes (assuming of course that there is a valid network connection).

Comment 2 Rejy M Cyriac 2016-08-26 15:05:48 UTC

(In reply to Stephen Gallagher from comment #1)
> As an alternate approach (I can file a separate BZ if preferred), Anaconda
> could regain the ability to perform upgrades by enabling the user to run a
> copy of `dnf system-upgrade download` in the /mnt/sysimage and then tell the
> user to reboot to apply the changes (assuming of course that there is a
> valid network connection).

Please do not make this (the ability to perform upgrades by enabling the user to run a copy of `dnf system-upgrade download` through Anaconda) as default, even if there is a valid network connection, due to network bandwidth availability constraints and issues related to network usage levels in most of the developing countries

Comment 3 Stephen Gallagher 2016-08-26 15:26:39 UTC

(In reply to Rejy M Cyriac from comment #2)
> (In reply to Stephen Gallagher from comment #1)
> > As an alternate approach (I can file a separate BZ if preferred), Anaconda
> > could regain the ability to perform upgrades by enabling the user to run a
> > copy of `dnf system-upgrade download` in the /mnt/sysimage and then tell the
> > user to reboot to apply the changes (assuming of course that there is a
> > valid network connection).
> 
> Please do not make this (the ability to perform upgrades by enabling the
> user to run a copy of `dnf system-upgrade download` through Anaconda) as
> default, even if there is a valid network connection, due to network
> bandwidth availability constraints and issues related to network usage
> levels in most of the developing countries

Just to be clear, I'm suggesting this as a user-selectable choice, not an automatic action by any stretch of the imagination. I meant that if (as Matthew suggested) Anaconda could detect an existing Fedora system on the hard drive that it could offer to optionally perform an upgrade instead of a reinstall (and then walk the user through any necessary network setup).