sts-sponsors team mailing list archive

[Ubuntu SRU Bot <1910264@xxxxxxxxxxxxxxxxxx>]

All autopkgtests for the newly accepted sosreport (4.1-1ubuntu0.18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

sosreport/4.1-1ubuntu0.18.04.1 (s390x, arm64, i386, ppc64el, amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#sosreport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [plugin][ceph] include time-sync-status for ceph mon

Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Committed
Status in sosreport source package in Focal:
  Fix Committed
Status in sosreport source package in Groovy:
  Fix Committed
Status in sosreport source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  This will be useful to know if there is a clock skew.

  The option has been first introduced in Luminous (v12) which is part
  of Ubuntu since Bionic/18.04LTS as follows:

  # rmadison ceph
   ceph | 12.2.4-0ubuntu1          | bionic
   ceph | 12.2.13-0ubuntu0.18.04.4 | bionic-security
   ceph | 12.2.13-0ubuntu0.18.04.5 | bionic-updates
   ceph | 15.2.1-0ubuntu1          | focal
   ceph | 15.2.5-0ubuntu1          | groovy
   ceph | 15.2.5-0ubuntu1.1        | groovy-security
   ceph | 15.2.7-0ubuntu0.20.04.1  | focal-updates
   ceph | 15.2.7-0ubuntu0.20.10.1  | groovy-updates
   ceph | 15.2.7-0ubuntu1          | hirsute
   ceph | 15.2.7-0ubuntu3          | hirsute-proposed

  Ceph mons might get into time sync problems if ntp/chrony
  isn't installed or configured correctly. Since Luminous
  release, upstream support 'time-sync-status' to detect this
  more easily.

  This information used to be part of ceph health structured output
  prior to Luminous but was removed in favor of the separate ceph time-
  sync-status command.

  Upstream documentation about the option:
  https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/

  [Test Case]

  * Connect to a ceph mon node via ssh/juju ssh/...
  * Run sosreport (this can be run in various ways but for the sake of this documenation let's use the most common):
   ** sosreport -a
   ** sosreport -o ceph

  [Where problems could occur]

  If something arise after this change. It will only affect the data
  collection of the ceph plugin. It won't affect other plugins nor core
  functionalities.

  Worse case scenario would be that user will have to collect ceph
  debugging data manually (outside a usual sosreport run) in order to
  provide it to a third-party support vendor.

  [Other information]

  Issues:
  https://github.com/sosreport/sos/issues/2356

  PR:
  https://github.com/sosreport/sos/pull/2357/commits/7859968b6e5e26c11d4bf4d8349646bd74723e52

  [Original Description]

  Ceph mons might get into time sync problems if ntp/chrony
  isn't installed or configured correctly. Since Luminous
  release, upstream support 'time-sync-status' to detect this
  more easily.

  This information used to be part of ceph health structured output
  prior to Luminous but was removed in favor of the separate ceph time-
  sync-status command.

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