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

[Arif Ali]

@athos-ribeiro @eeickmeyer

I created the debdiff by comparing the 2 .dsc files, and indeed it
include the file, as well it's symbolic linked file to be changed. I
have re-ran the debdiff locally again this morning, and I can see the
same thing. I can remove the offending section, and have been able to do
a debdiff-apply; I can upload this debdiff if required.

The maintainer was originally changed by Julian on version
4.5.6-0ubuntu3 when a rebuild was done, not sure why, and this is for
the case for only noble and oracular; the others are still the old
maintainer. We are changing the maintainer soon, but we need to change a
few things internally for that and hence were going to leave it as is.

The upstream project minor releases are created as a requirement for
RedHat, and hence the primary maintainer that is RH does those releases.
The core release cadence is 6 months, February and August. We plan to
stick to that release process and potentially one intermediate. We have
an internal testing criteria that can take some time to get our releases
out, and hence the SRU was started a month after release, and you can
see the release numbers in my PPA https://launchpad.net/~arif-
ali/+archive/ubuntu/sosreport-dev.

Happy to amend anything that is required and get this moving forward.

-- 
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