Delay reporting of system metrics when there is no network while running g-i-s

[Didier Roche-Tolomelli]

[Impact]

 * When users are running gnome-initial-setup (first login), if they don't have any network configured, the metrics reports silently drop the request. We are thus ignoring those reports.
 * There is now the willingness to have those reports included. The less intrusive way is to drop a pending report file and then having a service (only activated by a systemd path unit) started, doing exponential backoff until a network is detected. It doesn't impact thus CPU or network usage.
 * Reusing the previously pending report ensure we really send that data that the user acked upon.

[Test Case]

 * Disconnect from any network
 * Run ubuntu-report send yes
 * Check that there is a pending report in ~/.cache/ubuntu-report
 * Connect to a network
   -> the file should disappear and be sent after a couple of minutes.

[Regression Potential]

 * The feature has been heavily tested and backed by new tests.
 * Any error is already ignored by gnome-initial-setup, so we would end up in the same situation than today.

---

We need to provide a way to still report them (save for later and collect via a service)

[Didier Roche-Tolomelli (didrocks)]

Uploaded in cosmic via:

ubuntu-report (1.1.0cosmic) cosmic; urgency=medium

  * debian/gbp.conf: remove prebuild hook as exported in build-already now

ubuntu-report (1.1.0) bionic; urgency=medium

  * Delay reporting of system metrics when there is no network.
    A service then kicks in and try to report with exponential
    backoff until success (LP: #1774354)
  * Ensure that LANG is the user's language reported even in OEM
    mode (LP: #1765672)
  * Collect physical screen size (LP: #1771976)
  * Incorrect regex for GPU info (LP: #1765614)

[Łukasz Zemczak (sil2100)]

Hello Didier, or anyone else affected,

Accepted ubuntu-report into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-report/1.1.0 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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!

[Jean-Baptiste Lallement (jibel)]

SRU verification for Bionic:
I have reproduced the problem with ubuntu-report 1.0.11 in bionic and have verified that the version of ubuntu-report 1.1.0 in -proposed fixes the issue.

Marking as verification-done

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-report - 1.1.0

---------------
ubuntu-report (1.1.0) bionic; urgency=medium

  * Delay reporting of system metrics when there is no network.
    A service then kicks in and try to report with exponential
    backoff until success (LP: #1774354)
  * Ensure that LANG is the user's language reported even in OEM
    mode (LP: #1765672)
  * Collect physical screen size (LP: #1771976)
  * Incorrect regex for GPU info (LP: #1765614)

 -- Didier Roche <email address hidden> Thu, 31 May 2018 09:58:03 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for ubuntu-report 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.