[Bug 2054395] Re: [sru] sos upstream 4.7.0

[Athos Ribeiro]

Thanks for the reply, Arif.

Regarding the new upstream version: I understand it is not practical to
go for 4.7.1 now given your explanation. Let's go with 4.7.0 then.

As for the bogus debdiffs, please, fix them and make them apply cleanly
with debdiff-apply. This will at least slightly reduce the burden on the
sponsors, given that in the current state, they will either need to make
the changes themselves or pay attention to the patch reject file
generated in the process.

Finally, for the maintainer field in d/control, please go through
https://wiki.ubuntu.com/DebianMaintainerField so you understand why
Julian did change that field in the past. However, dpkg also carries a
change due to LP: #1951988, making dpkg-source also accept
@canonical.com addresses. This is fair based on the reasoning discussed
in the wikipage linked here. Hence, the change should be OK, and we
should most likely update that wiki page.

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

Title:
  [sru] sos upstream 4.7.0

Status in Ubuntu Pro:
  New
Status in Ubuntu Pro 18.04 series:
  New
Status in sosreport package in Ubuntu:
  In Progress
Status in sosreport source package in Focal:
  In Progress
Status in sosreport source package in Jammy:
  In Progress
Status in sosreport source package in Mantic:
  In Progress
Status in sosreport source package in Noble:
  In Progress
Status in sosreport source package in Oracular:
  In Progress

Bug description:
  [ Impact ]

  * A new sosreport version is available upstream, and following the
  https://wiki.ubuntu.com/SosreportUpdates policy for stable release
  exception we will now SRU the sosreport 4.7.0 upstream release.

  * This release introduces a couple of new plugins as well as bugfixes
  done between the previous Ubuntu 4.5.6 sosreport version and the new
  4.7.0.

  
  [ Test Plan ]

   * The detailed test plan can be found on
  https://wiki.ubuntu.com/SosreportUpdates and should be tested by a
  couple of users.

  [ Where problems could occur ]

  * Some plugins might stop working, and this will show when running
  sosreport.

  * Uploading to S3 needs the python3-boto3 dependency installed.

  * If there is an issue with a plugin that is causing instability to
  the system, this can be disabled by running 'sosreport -n
  <plugin_name>'.

  * Currently running sos collect with Juju 3 is -not- working, even for
  the current  4.5.6 Ubuntu version, we are working upstream on a fix
  here: https://github.com/sosreport/sos/pull/3422 this is not part of
  the core functionality of sos, and one can still run sos report
  manually on the nodes.

  [ Other Info ]
   
  * Useful plugins that are now part of 4.7.0 and could do some testing:

  * runtime/lxd We have added an LXD runtime so that we can gather data directly from LXD, same with what one would do with k8s.
  * plugins/canonical_livepatch_onprem.py will gather data from livepatch-server
  * plugins/ceph.py add Reef release commands and gather microceph data
  * plugins/coredump.py will capture coredump info from coredumpctl
  * plugins/infinidat.py will gather data from servers that make use if the Infinidat storage solution
  * plugins/kubernetes.py will now gather container information from microk8s
  * plugins/mellanox_firmware.py will gather data from mellanox devices
  * plugins/openstack_masakari.py will gather data from openstack masakari
  * plugins/openstack_masakarimonitors.py will gather data from openstack masakari monitors
  * plugins/vectordev.py will gather the config from vectordev (cos-proxy)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions