| 2020-02-11 19:38:53 |
Eric Desrochers |
bug |
|
|
added bug |
| 2020-02-11 19:39:01 |
Eric Desrochers |
tags |
|
sts |
|
| 2020-02-11 19:39:22 |
Eric Desrochers |
sosreport (Ubuntu): status |
New |
In Progress |
|
| 2020-02-11 19:39:41 |
Eric Desrochers |
nominated for series |
|
Ubuntu Focal |
|
| 2020-02-11 19:39:41 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Focal) |
|
| 2020-02-11 19:41:32 |
Dan Streetman |
sosreport (Ubuntu Focal): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-02-11 19:41:35 |
Dan Streetman |
sosreport (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-02-11 19:42:45 |
Dan Streetman |
sosreport (Ubuntu Focal): assignee |
Eric Desrochers (slashd) |
|
|
| 2020-02-11 19:43:24 |
Dan Streetman |
sosreport (Ubuntu Focal): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-02-11 19:47:36 |
Eric Desrochers |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-02-11 19:47:36 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Eoan) |
|
| 2020-02-11 19:47:36 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2020-02-11 19:47:36 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Xenial) |
|
| 2020-02-11 19:47:36 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-02-11 19:47:36 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Bionic) |
|
| 2020-02-11 19:50:21 |
Eric Desrochers |
sosreport (Ubuntu Focal): assignee |
Eric Desrochers (slashd) |
|
|
| 2020-02-11 19:50:30 |
Eric Desrochers |
sosreport (Ubuntu Focal): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-02-11 19:52:36 |
Eric Desrochers |
bug |
|
|
added subscriber Bryan Quigley |
| 2020-02-11 19:56:13 |
Eric Desrochers |
description |
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activity to update sosreport in Ubuntu stable + Active Devel release. |
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-11 20:35:24 |
Eric Desrochers |
bug |
|
|
added subscriber Chris Johnston |
| 2020-02-11 20:35:32 |
Eric Desrochers |
bug |
|
|
added subscriber Chris Newcomer |
| 2020-02-11 20:44:38 |
Eric Desrochers |
sosreport (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-02-11 20:44:40 |
Eric Desrochers |
sosreport (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-02-11 20:44:42 |
Eric Desrochers |
sosreport (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2020-02-11 20:44:45 |
Eric Desrochers |
sosreport (Ubuntu Bionic): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-02-11 20:44:47 |
Eric Desrochers |
sosreport (Ubuntu Eoan): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-02-13 19:35:45 |
Eric Desrochers |
sosreport (Ubuntu Xenial): assignee |
|
Eric Desrochers (slashd) |
|
| 2020-02-14 21:25:17 |
Eric Desrochers |
description |
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the release (especially LTSes) will be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
[Regression Potential]
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-14 21:25:46 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the release (especially LTSes) will be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
[Regression Potential]
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
[Regression Potential]
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-15 21:28:58 |
Eric Desrochers |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951392 |
|
| 2020-02-15 21:28:58 |
Eric Desrochers |
bug task added |
|
sosreport (Debian) |
|
| 2020-02-15 21:41:08 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
[Regression Potential]
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Run sosreport in different customer scenario: server, desktop, cloud, hypervisor, instance (container, vm), physical server, ....
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-15 21:43:09 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Run sosreport in different customer scenario: server, desktop, cloud, hypervisor, instance (container, vm), physical server, ....
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-15 21:43:28 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Test new --all-logs behaviour
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-15 21:45:56 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Test new --all-logs behaviour
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Test new --all-logs behaviour
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" and "sos_logs" for warnings/errors
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-15 21:52:51 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Test new --all-logs behaviour
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" and "sos_logs" for warnings/errors
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" and "sos_logs" for warnings/errors
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-15 23:41:27 |
Bug Watch Updater |
sosreport (Debian): status |
Unknown |
New |
|
| 2020-02-16 13:50:21 |
Eric Desrochers |
sosreport (Ubuntu): status |
In Progress |
Fix Released |
|
| 2020-02-16 14:11:41 |
Eric Desrochers |
sosreport (Ubuntu Eoan): status |
New |
In Progress |
|
| 2020-02-16 14:11:44 |
Eric Desrochers |
sosreport (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-02-16 14:11:47 |
Eric Desrochers |
sosreport (Ubuntu Xenial): status |
New |
In Progress |
|
| 2020-02-17 00:46:18 |
Bug Watch Updater |
sosreport (Debian): status |
New |
Fix Released |
|
| 2020-02-19 13:29:56 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality (--upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" and "sos_logs" for warnings/errors
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" and "sos_logs" for warnings/errors
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-19 16:28:15 |
Jeff Lane |
bug |
|
|
added subscriber Jeff Lane |
| 2020-02-20 21:24:54 |
Eric Desrochers |
bug watch added |
|
https://github.com/sosreport/sos/issues/1963 |
|
| 2020-02-20 21:28:54 |
Eric Desrochers |
bug |
|
|
added subscriber Pedro Principeza |
| 2020-02-20 21:29:05 |
Eric Desrochers |
bug |
|
|
added subscriber João Pedro Seara |
| 2020-02-24 16:52:54 |
Łukasz Zemczak |
sosreport (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-02-24 16:52:57 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-02-24 16:52:58 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-02-24 16:53:04 |
Łukasz Zemczak |
tags |
sts |
sts verification-needed verification-needed-eoan |
|
| 2020-02-24 16:57:38 |
Łukasz Zemczak |
sosreport (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-02-24 16:57:45 |
Łukasz Zemczak |
tags |
sts verification-needed verification-needed-eoan |
sts verification-needed verification-needed-bionic verification-needed-eoan |
|
| 2020-02-24 19:28:11 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" and "sos_logs" for warnings/errors
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" for full report.
* Look under "sos_logs" for warnings/errors.
$ grep -v "INFO:" sos.log
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-24 19:28:42 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" for full report.
* Look under "sos_logs" for warnings/errors.
$ grep -v "INFO:" sos.log
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" for full report.
* Look under "sos_logs" for warnings/errors.
$ grep -v "INFO:" sos_logs/sos.log
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-02-27 20:06:46 |
John Lewis |
bug |
|
|
added subscriber John Lewis |
| 2020-02-28 01:01:47 |
Bryan Quigley |
bug watch added |
|
https://github.com/sosreport/sos/issues/1921 |
|
| 2020-02-28 01:02:01 |
Bryan Quigley |
tags |
sts verification-needed verification-needed-bionic verification-needed-eoan |
sts verification-done-eoan verification-needed verification-needed-bionic |
|
| 2020-02-28 17:16:31 |
Eric Desrochers |
description |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" for full report.
* Look under "sos_logs" for warnings/errors.
$ grep -v "INFO:" sos_logs/sos.log
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
[Impact]
sosreport 3.9 is now released.
It would be great to find sosreport v3.9 in supported stable releases, and active development release considering the fact that the releasea (especially LTSes) are going to be supported for a couple of years still.
Sosreport is widely use by Canonical support team to troubleshoot UA (Ubuntu Advantage) customer, other vendors and community users.
Just like we did for :
- v3.5 (LP: #1734983)
- v3.6 (LP: #1775195)
[Test Case]
* Install sosreport
* Test the new upload functionality and check if the archive is found in BrickFTP under uploads/ as it should. (e.g. sosreport -a --all-logs --upload)
* Test new --all-logs behaviour
* Make sure the new naming pattern doesn't break any current Canonical mechanism (Brickftp scripts, ...). If yes evaluate if easy fixable before considering reverting back to 'legacy' pattern.
* Run sosreport in different customer scenarios:
server, desktop, cloud, hypervisor, instance (container, vm), physical server, ...
* Extract archive and look at the content, look for 0 size file (and use common sense if legit or not)
* Look under "sos_reports" for full report.
* Look under "sos_logs" for warnings/errors.
$ grep -v "INFO:" sos_logs/sos.log
* Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection.
[Regression Potential]
Sosreport has 292 plugins that are all configured differently and configured to run under certains conditions. We can't test all possible scenarios. All we can do is idenfity the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...) . With that being said, it is definitely possible that certains plugins may not work as expected, but the risk will be very low (e.g not collecting the desired informations) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionnalities of sosreport.
[Other Informations]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.9
[Original Description]
A new version of sosreport upstream (v3.9) will be released soon.
This bug is to track activities to update sosreport in Ubuntu stable + Active Devel release. |
|
| 2020-03-02 08:14:09 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-03-02 08:24:12 |
Launchpad Janitor |
sosreport (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-03-02 13:38:17 |
Eric Desrochers |
tags |
sts verification-done-eoan verification-needed verification-needed-bionic |
sts verification-done-bionic verification-done-eoan verification-needed |
|
| 2020-03-02 15:51:33 |
Launchpad Janitor |
sosreport (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-03-12 15:25:57 |
Łukasz Zemczak |
sosreport (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2020-03-12 15:26:00 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-03-12 15:26:07 |
Łukasz Zemczak |
tags |
sts verification-done-bionic verification-done-eoan verification-needed |
sts verification-done-bionic verification-done-eoan verification-needed verification-needed-xenial |
|
| 2020-03-18 01:09:43 |
Eric Desrochers |
tags |
sts verification-done-bionic verification-done-eoan verification-needed verification-needed-xenial |
sts verification-done-bionic verification-done-eoan verification-done-xenial verification-needed |
|
| 2020-03-19 12:54:58 |
Launchpad Janitor |
sosreport (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
