Migrate LVFS to Amazon S3
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:/
[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.
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).