[Bug 1245524] Re: whoopsie fails to immediately notice/process .upload files

[Brian Murray]

** Tags removed: verification-needed
** Tags added: verification-done-saucy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1245524

Title:
  whoopsie fails to immediately notice/process .upload files

Status in “whoopsie” package in Ubuntu:
  Fix Released
Status in “whoopsie” source package in Saucy:
  Fix Committed

Bug description:
  [Impact]
  whoopsie does not immediately notice .upload files produced by apport after a crash report has all its data collected, and subsequently will not upload the .crash to the error tracker right away.  Instead whoopsie will wait 2 hours and then check /var/crash/ for new crash files and then upload the crash report.

  [Test Case]
  1) sudo rm /var/crash/*
  2) sudo service whoopsie restart
  3) Install d-feet
  4) (d-feet &); sleep 3; killall -SEGV d-feet
  5) Observe apport crash dialog and choose to send crash report
  6) Wait a bit for apport to collect data then ls -lh /var/crash/
  7) Observe a .crash file and a .upload for d-feet and no .uploaded file
  8) grep whoopsie /var/log/syslog and notice not "Parsing.*crash" message

  With the version of whoopsie from saucy-proposed you should see a
  .uploaded file and the "Parsing /var/crash/.*crash" file message.
  After installing the version of apport from -proposed be sure to
  remove the files in /var/crash as whoopsie does an initial check on
  startup for files in /var/crash/ and processes them.

  [Original Report]
  ------
  We're trying to use the whoopsie-upload-all script in apport to ensure that all .crash files get uploaded in touch images.  It seems that something is wrong with the inotify watch when running on the touch images though.

  As a workaround, we've found that running whoopsie-upload-all, waiting
  for the .upload files to appear, then restarting whoopsie will unblock
  things.

  We can work around this in ci for now, but this needs to be
  investigated further as it could cause problems down the road for
  allowing devices to upload crash data in the wild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1245524/+subscriptions