Bug 1153813

Summary: Include fedora-release-standard -> nonproduct rename in Fedora 21 Beta
Product: [Fedora] Fedora Reporter: Kalev Lember <kalevlember>
Component: fedora-releaseAssignee: Dennis Gilmore <dennis>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: awilliam, dennis, jdisnard, kevin, mruckman, robatino, sgallagh, va.orlov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedBlocker
Fixed In Version: fedora-release-21-0.16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-20 23:01: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:
Bug Depends On:    
Bug Blocks: 1043124    

Description Kalev Lember 2014-10-16 20:51:23 UTC
Please include the new fedora-release build that renames fedora-release-standard -> nonproduct in Fedora 21 Beta. It's a rather disruptive change, needs comps updates etc, but pulling it in now rather than after Beta makes sure we can properly test the upgrade path from F20.

Fedup is going to have a hardcoded list of product names (server, workstation, cloud, nonproduct) and is going to give an option to choose between those 4 for F20 upgrades. Being able to rely on the new naming makes it possible to better test upgrades ahead of the final release.

I'll link the build ID here once dgilmore has kicked off the new fedora-release build.

Comment 1 Fedora Blocker Bugs Application 2014-10-16 20:55:30 UTC
Proposed as a Blocker for 21-beta by Fedora user sgallagh using the blocker tracking app because:

 "For each one of the release-blocking package sets, it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed. The user must be made to specify which Product (or none) they wish to have running when upgrade is complete." (Proposed critertion in discussion)

This fix must go in to enable the fedup changes to support this criterion.

Comment 2 Adam Williamson 2014-10-16 21:27:47 UTC
+1 blocker, per c#1. Since we're going to have to do this, let's get it in ASAP - dgilmore and I will try to get it into TC4.

Comment 3 Kevin Fenzi 2014-10-16 21:28:25 UTC
+1 blocker, but please please lets not paint the bikeshed anymore? ;)

Comment 4 Mike Ruckman 2014-10-16 21:30:16 UTC
+1 blocker

Comment 5 Adam Williamson 2014-10-16 21:31:16 UTC
That's enough for acceptedblocker status, I'll list it in the TC4 request.

Comment 6 Fedora Update System 2014-10-17 00:06:13 UTC
fedora-release-21-0.16 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/fedora-release-21-0.16

Comment 7 Fedora Update System 2014-10-17 19:44:01 UTC
Package fedora-release-21-0.16:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedora-release-21-0.16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-13090/fedora-release-21-0.16
then log in and leave karma (feedback).

Comment 8 Adam Williamson 2014-10-17 23:18:09 UTC
Doesn't need to be a proposed FE if it's an acceptedblocker.

Comment 9 Fedora Update System 2014-10-20 23:01:25 UTC
fedora-release-21-0.16 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Vlad_7 2014-10-22 12:19:29 UTC
Problem still present in other place.
While updating F20 -> F21 with tool "fedora-upgrade":
-------------------------------------
... some useless messages skipped ...

What is your option? (cloud/server/workstation/standard)  standard
Resolving Dependencies
--> Running transaction check
---> Package fedora-release-nonproduct.noarch 0:21-0.16 will be installed
--> Processing Conflict: fedora-release-cloud-21-0.16.noarch conflicts fedora-release-nonproduct
--> Processing Conflict: fedora-release-nonproduct-21-0.16.noarch conflicts fedora-release-cloud
--> Finished Dependency Resolution
Error: fedora-release-nonproduct conflicts with fedora-release-cloud-21-0.16.noarch
Error: fedora-release-cloud conflicts with fedora-release-nonproduct-21-0.16.noarch
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Comment 11 Stephen Gallagher 2014-10-22 12:34:58 UTC
fedora-upgrade is not the standard, supported upgrade mechanism (that is fedup).

Please file any bugs related to fedora-upgrade against its component.