Change metadata server to upstream requested one

Bug #1761006 reported by Robert Ancell on 2018-04-03
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
Status tracked in Bionic
Xenial
Medium
Unassigned
Artful
Medium
Unassigned
Bionic
Medium
Unassigned

Bug Description

[Impact]
fwupd is configured to use an Amazon server for downloading firmware metadata. As requested by upstream:

"The current CDN (~$100/month) is kindly sponsored by Amazon, but that won't
last forever. In the future we can switch to a 'dumb' provider like BunnyCDN
for 1/10th of the cost.

Use a CNAME we control to make switching CDN providers easy in the future."

[Test Case]
Still able to install firmware as before

[Regression Potential]
Some risk of breaking firmware updates due to server configuration, but this matches upstreams setup and is the behaviour in fwupd 1.0.6 (in bionic onwards).

Robert Ancell (robert-ancell) wrote :

Note wont fix in artful as that is about to go EOL and the existing server should continue to work until then.

Changed in fwupd (Ubuntu Bionic):
status: New → Fix Released
importance: Undecided → Medium
Changed in fwupd (Ubuntu Artful):
importance: Undecided → Medium
Changed in fwupd (Ubuntu Xenial):
importance: Undecided → Medium
Changed in fwupd (Ubuntu Artful):
status: New → Won't Fix
Changed in fwupd (Ubuntu Xenial):
status: New → Triaged
Changed in fwupd (Ubuntu Xenial):
status: Triaged → Fix Committed

Hello Robert, 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.8.3-0ubuntu3 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 on 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

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

tags: added: verification-needed verification-needed-xenial
Robert Ancell (robert-ancell) wrote :

@Mario - could you verify this?

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

Other bug subscribers