| 2020-03-20 06:51:30 |
Seyeong Kim |
bug |
|
|
added bug |
| 2020-03-20 06:51:51 |
Seyeong Kim |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-03-20 06:51:51 |
Seyeong Kim |
bug task added |
|
sosreport (Ubuntu Eoan) |
|
| 2020-03-20 06:51:51 |
Seyeong Kim |
nominated for series |
|
Ubuntu Focal |
|
| 2020-03-20 06:51:51 |
Seyeong Kim |
bug task added |
|
sosreport (Ubuntu Focal) |
|
| 2020-03-20 06:51:51 |
Seyeong Kim |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-03-20 06:51:51 |
Seyeong Kim |
bug task added |
|
sosreport (Ubuntu Bionic) |
|
| 2020-03-20 06:52:00 |
Seyeong Kim |
tags |
|
sts |
|
| 2020-03-20 06:52:29 |
Seyeong Kim |
sosreport (Ubuntu Bionic): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2020-03-20 06:52:31 |
Seyeong Kim |
sosreport (Ubuntu Eoan): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2020-03-20 06:52:33 |
Seyeong Kim |
sosreport (Ubuntu Focal): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2020-03-24 00:08:53 |
Seyeong Kim |
sosreport (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-03-24 00:08:56 |
Seyeong Kim |
sosreport (Ubuntu Eoan): status |
New |
In Progress |
|
| 2020-03-24 00:08:58 |
Seyeong Kim |
sosreport (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-03-24 15:01:38 |
Eric Desrochers |
description |
[Impact]
[Test Case]
Preparing
[Regression]
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264 |
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options:
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
The commit has been +1 by lxd upstream stgraber, FWIW:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
|
| 2020-03-24 15:02:38 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2020-03-24 16:19:08 |
Eric Desrochers |
description |
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options:
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
The commit has been +1 by lxd upstream stgraber, FWIW:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options (as a sanity check):
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
The commit has been +1 by lxd upstream stgraber, FWIW:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
|
| 2020-03-24 16:21:41 |
Eric Desrochers |
description |
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options (as a sanity check):
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
The commit has been +1 by lxd upstream stgraber, FWIW:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options (as a sanity check):
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
If a problem occurs it will only impact the lxd plugin, not the other plugins nor core functionnalities.
If for some reasons a command can be executed (not found in versions installed or else). sosreport is fault tolerant, and will continue/skip the command that doesn't exist, fails, ...
FWIW, the commit has been +1 by lxd upstream himself stgraber:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
|
| 2020-03-24 16:21:57 |
Eric Desrochers |
bug |
|
|
added subscriber Bryan Quigley |
| 2020-03-24 16:22:08 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2020-03-24 16:22:18 |
Eric Desrochers |
tags |
sts |
sts sts-sponsor-slashd |
|
| 2020-03-25 05:28:54 |
Seyeong Kim |
attachment added |
|
lp1868215_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+attachment/5341304/+files/lp1868215_focal.debdiff |
|
| 2020-03-25 05:29:12 |
Seyeong Kim |
attachment added |
|
lp1868215_eoan.debdiff https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+attachment/5341305/+files/lp1868215_eoan.debdiff |
|
| 2020-03-25 05:29:25 |
Seyeong Kim |
attachment added |
|
lp18168215_bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1868215/+attachment/5341306/+files/lp18168215_bionic.debdiff |
|
| 2020-03-25 05:33:19 |
Seyeong Kim |
description |
[Impact]
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options (as a sanity check):
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
If a problem occurs it will only impact the lxd plugin, not the other plugins nor core functionnalities.
If for some reasons a command can be executed (not found in versions installed or else). sosreport is fault tolerant, and will continue/skip the command that doesn't exist, fails, ...
FWIW, the commit has been +1 by lxd upstream himself stgraber:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
[Impact]
sosreport doesn't have to collect everything related to lxd which is very huge and unhelpful that much.
This commit make sosreport collect proper info as installation types.
[Test Case]
Scenario #1
* Deploy a machine (Xenial) with lxd installed as a DEB package
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the else statement of the plugin.
Scenario #2
* Deploy a machine (Bionic and late) with lxd installed as a SNAP.
* Install sosreport
* sudo sosreport -o lxd or/and sudo sosreport -a
* Extract the archive in /tmp and go in path_to_sosreport/sos_commands/lxd
The data collection should be the one in the if statement of the plugin, only executing "lxd.buginfo" command only available in SNAP.
Scenario #3:
A quick script to run on a node to verify multiple different options (as a sanity check):
https://raw.githubusercontent.com/sosreport/sos/master/tests/simple.sh
sudo bash simple.sh /usr/bin/python3 /usr/bin/sosreport
simple.sh is a quick port of the travis tests to bash, requires root.
There is some work to incorporate this exact script into the sosreport package for autopkg testing, but meanwhile it can be run manually for verifications.
[Regression]
"lxd.buginfo" has the advantage of not needing updates whenever
lxd upstream add a new feature or find something new that’s worth capturing since LXD is now only offered as a SNAP nowadays.
The plugin will remain backward compatible with DEB and SNAP, until there is no supported lxd DEB package available.
If a problem occurs it will only impact the lxd plugin, not the other plugins nor core functionnalities.
If for some reasons a command can be executed (not found in versions installed or else). sosreport is fault tolerant, and will continue/skip the command that doesn't exist, fails, ...
FWIW, the commit has been +1 by lxd upstream himself stgraber:
https://github.com/sosreport/sos/pull/1982/
[Others]
upstream patch
- https://github.com/sosreport/sos/pull/1982/commits/bdc5ffdf5b8376ab2014ec8fbd9a878cc9d0d264
LXD upstream reference:
https://discuss.linuxcontainers.org/t/what-lxd-information-should-be-collected-by-sosreport |
|
| 2020-03-25 08:25:26 |
Ubuntu Foundations Team Bug Bot |
tags |
sts sts-sponsor-slashd |
patch sts sts-sponsor-slashd |
|
| 2020-03-25 08:25:33 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2020-03-25 17:05:01 |
Eric Desrochers |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2020-03-25 19:04:18 |
Launchpad Janitor |
sosreport (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2020-03-30 19:40:47 |
Eric Desrochers |
tags |
patch sts sts-sponsor-slashd |
patch sts sts-sponsor-slashd sts-sponsor-volunteer |
|
| 2020-03-31 23:45:23 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2020-04-06 17:42:16 |
Eric Desrochers |
tags |
patch sts sts-sponsor-slashd sts-sponsor-volunteer |
patch sts |
|
| 2020-04-06 17:52:26 |
Łukasz Zemczak |
sosreport (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-04-06 17:52:29 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-04-06 17:52:32 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-04-06 17:52:36 |
Łukasz Zemczak |
tags |
patch sts |
patch sts verification-needed verification-needed-eoan |
|
| 2020-04-06 17:58:38 |
Łukasz Zemczak |
sosreport (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-04-06 17:58:43 |
Łukasz Zemczak |
tags |
patch sts verification-needed verification-needed-eoan |
patch sts verification-needed verification-needed-bionic verification-needed-eoan |
|
| 2020-04-07 03:17:27 |
Seyeong Kim |
tags |
patch sts verification-needed verification-needed-bionic verification-needed-eoan |
patch sts verification-done-bionic verification-needed verification-needed-eoan |
|
| 2020-04-07 06:21:57 |
Seyeong Kim |
tags |
patch sts verification-done-bionic verification-needed verification-needed-eoan |
patch sts verification-done-bionic verification-done-eoan verification-needed |
|
| 2020-04-14 18:33:12 |
Launchpad Janitor |
sosreport (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-04-14 18:37:34 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-04-14 18:38:17 |
Launchpad Janitor |
sosreport (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
