sosreport archive /var/lib/maas by default

[Louis Bouchard]

SRU justification :
Maas plugin collects more data than required.

Impact :
Without this fix, the size of the collected output get become huge (multi-Gb)

Fix :
Restrict the collected directories.

Test Case :
On a Maas server with many installation images installed, running the fixed version will not collect the large files in /var/lib/maas/ephemeral and/or /var/lib/maas/tftp

Regression :
None expected.

Original description of the problem :

When ran on a machine running as a maas cluster controller, putting the content of /var/lib/maas in the sosreport copy all the fast installer and regular iso images used to deploy vm. As a result, the archive turns to be around 3Gb of size.

[Louis Bouchard (louis)]

Marked Trusty Fixed Released as it's been fixed upstream

[Iain Lane (laney)]

sosreport is only in 12.04 via backports. The way to fix this bug there is by getting this SRUed into Saucy and then backporting to precise. Backports policy says it'll have to be backported to Quantal too, to maintain an upgrade path.

For that, please confirm the following

 [ ] sosreport 3.0-1ubuntu1 builds without changes on Quantal
 [ ] sosreport 3.0-1ubuntu1 builds without changes on Precise
 [ ] sosreport 3.0-1ubuntu1 installs and runs correctly on Quantal
 [ ] sosreport 3.0-1ubuntu1 installs and runs correctly on Precise

I'm going to add the backports tasks now, and look to sponsor the Saucy SRU. Thanks!

[Louis Bouchard (louis)]

I found out this morning that another SRU for sosreport had been started :

https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1302808

I must synchonize with Chris on this one before doing anything here

[Chris J Arges (arges)]

Let's ensure sosreport Trusty/Saucy has a critical mass of bugs fixed first, then we can worry about the backport process to Q then P. Spoke with Louis about this. Unsubscribing sponsors for now until this is sorted.
Thanks

[Louis Bouchard (louis)]

New version of the debdiff including patches for other bugs

[Louis Bouchard (louis)]

Fix for this bug and LP: #1230209, LP: 1301819, LP: #1302837

[Louis Bouchard (louis)]

The previous debdiff above is for Precise

Fix for this bug and LP: #1230209, LP: #1301819, LP: #1302837 for saucy.

[James Page (james-page)]

Louis

Thanks for the debdiffs; They look fine apart from the fact that the Description of each patch is not following the DEP-3 patch tagging guidelines - see http://dep.debian.net/deps/dep3/ for details. Please could you update - other than that looks great!

Cheers

James

[James Page (james-page)]

Louis - for the precise-backports debdiff, you need to target precise-backports rather than precise in the changelog; you will also need to complete the backport testing as Laney describes in #4.

[Louis Bouchard (louis)]

Fix for this bug and LP: #1230209, LP: #1301819, LP: #1302837 for saucy. Includes changes following jamespage's suggestion

[Louis Bouchard (louis)]

Fix for this bug and LP: #1230209, LP: #1301819, LP: #1302837 for precise-backport. Includes changes following jamespage's suggestion

[Iain Lane (laney)]

You don't need a debdiff for precise-backports - we just take the package wholesale from the source release.

I've lost track of this bug a bit - where is it fixed? We can backport from trusty to precise if you want, you just have to tell the bug that it's been tested to work without any changes to the source package.

Saucy's about to go EOL so you might want to consider not bothering with this one.

[Chris J Arges (arges)]

Sponsored for Saucy.

[Chris J Arges (arges)]

I think the overall goal is to get something into precise-backports; so hopefully that path is still available.