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

[Athos Ribeiro]

Oh, there is one additional issue:

debdiff-apply failis with

File man/en/sosreport.1 is not a regular file -- refusing to patch
2 out of 2 hunks ignored

...

Traceback (most recent call last):
  File "/usr/bin/debdiff-apply", line 382, in <module>
    sys.exit(main(sys.argv[1:]))
             ^^^^^^^^^^^^^^^^^^
  File "/usr/bin/debdiff-apply", line 331, in main
    debdiff_apply(patch, patch_name, args)
  File "/usr/bin/debdiff-apply", line 207, in debdiff_apply
    call_patch(patch_str, "--dry-run", "-f")
  File "/usr/bin/debdiff-apply", line 139, in call_patch
    return subprocess.run(
           ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['patch', '-p1', '--dry-run', '-f']' returned non-zero exit status 1.

I can still apply it with `patch`, but it would be nice to check that
(it seems it is trying to patch that symlink). How are you generating
the debdiff?

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