** Description changed:

  [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:
+ 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: 
+ 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

** Description changed:

  [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:
+ 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

** Tags added: sts-sponsor-slashd

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

Title:
  SRU: [lxd] Drop db collection and introduce lxd.buginfo

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to