Migrate LVFS to Amazon S3

Bug #1612365 reported by Mario Limonciello
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Unassigned
Yakkety
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

 * The current fwupd implementation bangs on an instance of LVFS (which runs on OpenShift). As more distros have been picking up fwupd, it's become apparent that openshift can't scale and carry the load.
 * This has meant that FW updates can't be distributed in a timely manner and a lot of clients time out

 * Upstream is moving all data to Amazon S3 instead and keeping the LVFS openshift instance only as the frontend for OEM use.
This change happened upstream in this commit:
https://github.com/hughsie/fwupd/commit/96e1ea6b265728aad5bf43f18009abb3befc34a0

[Test Case]

1) Update to new fwupd package
2) run fwupdmgr refresh

Make sure that no errors are reported

[Regression Potential]

 * Regression potential is low. The data is still signed with the same keys, it's just been moved to a different backend.

Revision history for this message
Mario Limonciello (superm1) wrote :

I've uploaded this to yakkety and xenial proposed. Yakkety is FTBFS for unrelated reasons but the code is there (https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1612429).

Changed in fwupd (Ubuntu Xenial):
status: New → In Progress
Changed in fwupd (Ubuntu Yakkety):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fwupd - 0.7.0-0ubuntu7

---------------
fwupd (0.7.0-0ubuntu7) yakkety; urgency=medium

  * Download metadata from Amazon S3 instead. (LP: #1612365)

 -- Mario Limonciello <email address hidden> Thu, 11 Aug 2016 12:46:46 -0500

Changed in fwupd (Ubuntu Yakkety):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Mario, or anyone else affected,

Accepted fwupd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/0.7.0-0ubuntu4.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in fwupd (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Mario Limonciello (superm1) wrote :

Yep, just verified on xenial it's all good.

$ apt policy fwupd
fwupd:
  Installed: 0.7.0-0ubuntu4.3
  Candidate: 0.7.0-0ubuntu4.3
  Version table:
 *** 0.7.0-0ubuntu4.3 500
        500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     0.7.0-0ubuntu4.2 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
     0.7.0-0ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
$ cat /etc/fwupd.conf
[fwupd]

# The download URI to use for LVFS metadata
#
# If you want to use testing firmware then change this value to:
# https://s3.amazonaws.com/lvfsbucket/downloads/firmware-testing.xml.gz
DownloadURI=https://s3.amazonaws.com/lvfsbucket/downloads/firmware.xml.gz

# If we should verify option ROM images
EnableOptionROM=true
$ fwupdmgr refresh
$

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package fwupd - 0.7.0-0ubuntu4.3

---------------
fwupd (0.7.0-0ubuntu4.3) xenial-proposed; urgency=medium

  * Download metadata from Amazon S3 instead. (LP: #1612365)

 -- Mario Limonciello <email address hidden> Thu, 11 Aug 2016 15:47:41 -0500

Changed in fwupd (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for fwupd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.