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

[Athos Ribeiro]

Thanks, Arif.

The contents are correct as per the upstream release.

For the `X-Python3-Version: >= 3.6` entry in d/control, I kept wondering
if it is this needed in anything other than bionic and I wonder how the
SRU team will look at that. Unless we are supporting upgrade paths that
would skip a release, e.g., upgrading directly from xenial to focal,
jammy, or noble, this would have no effect at all in all but a bionic
debdiff. No need to remove the entry though, I am just leaving this
comment as a note for the SRU review later (let the SRU team decide on
this one). Still, if you want to keep it, you will need to file the SRU
template paperwork in the related bug (LP: #2038648).

In oracular, the last patch added is now a variation of an upstream
commit so it applies correctly to the current version. In that case, you
can keep the original patch file with just that hunk that did not apply
removed. The Origin DEP3 header can be set to "backport,
GITHUB_COMMIT_URL".

I also have a nitpick for d/patches:
on the "Origin" DEP3 header field entries, would you mind pointing to commits instead of PRs? this would make it clearer to whoever looks at the patch that the change was already accepted upstream without the need to open the URLs to verify if that is the case.
      e.g., instead of
      Origin: upstream, https://github.com/sosreport/sos/pull/3545
      use
      Origin: upstream, https://github.com/sosreport/sos/commit/7e81246fcfd35e17a69bc3d40400cd123e8ca7bf
      etc.

The mantic's debian/changelog file is missing entries for
python3-packaging and python3-yaml. I did not review jammy and focal
assuming they will also have similar instances of the cases listed
above. Let's get oracular in a "ready to upload" shape, then we can go
back fixing the SRUs, WDYT?

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