Bug 1496489
Summary: | After upgrading to Fedora 27: Failed to Update - Too many results returned | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | František Zatloukal <fzatlouk> | ||||||||||
Component: | gnome-software | Assignee: | Richard Hughes <rhughes> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 27 | CC: | awilliam, gnome-sig, jonha87, klember, rhughes, robatino | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | RejectedBlocker AcceptedFreezeException | ||||||||||||
Fixed In Version: | gnome-software-3.26.1-3.fc27 | Doc Type: | If docs needed, set a value | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2017-10-30 01:53:18 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: | 1396705 | ||||||||||||
Attachments: |
|
Description
František Zatloukal
2017-09-27 14:49:27 UTC
Created attachment 1331464 [details]
Log from upgrade - dnf
Created attachment 1331465 [details]
Log from upgrade - PackageKit
Created attachment 1331466 [details]
Error message after upgrade
I got the same error after doing a upgrade with gnome-software according to this instructions: https://fedoraproject.org/wiki/QA:Testcase_upgrade_gnome-software_current_workstation Proposed as a Blocker and Freeze Exception for 27-final by Fedora user jonha using the blocker tracking app because: This might not technically violate the "There must be no [...] crash notifications on [...] first login after a default install of a release-blocking desktop." criterion, because it happens after an upgrade and not after installation and it shows an "update failed" notification instead of a crash notification. But I think this is similar enough (in spirit) to be considered. This happened to all Workstation installations I upgraded to F27 Beta via both dnf and gnome-software and it should at least be investigated, because it is very confusing to get an "update failed" notification after a successful upgrade. Created attachment 1343094 [details]
Notification Screenshot
Note that in addition to the gnome-software error you get an annoying and confusing notification after every login.
Note that software upgrades generally work despite the error message.
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=789477 I debugged this and it's the F27 gnome-software that's incorrectly showing an error there. Builds fixing this under way. gnome-software-3.26.1-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e25cbf4b94 I'm -1 blocker on this. I'm probably +1 FE to try and ensure this doesn't affect day 1 upgrades, though, so long as the fix is fairly safe - Kalev? Yep, it's a targeted fix, and should be safe to pull in for final. +1 FE from me as well. Discussed at 2017-10-26 Fedora 27 Final go/no-go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-10-26/f27-final-and-server-beta-go-no-go-meeting.2017-10-26-17.00.html . Rejected as a blocker as it doesn't actually seem to violate the criteria at all - the upgrade *works* fine, there's just a bogus error. However, accepted as a freeze exception issue as this obviously doesn't look good and it'd be nice to avoid people hitting it between now and the 0-day update push. gnome-software-3.26.1-3.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |