Uploaded in Hirsute (current active devel release) ** Description changed:
[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] + * Login on a ceph mon node. + * Run sosreport (this can be run in various ways but for the sake of this documenation let's use the most common): + ** sosreport -a + ** sosreprot -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 debugging data + manually (outside an usual sosreport run) [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. ** Description changed: [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] - * Login on a ceph mon node. + * 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 - ** sosreprot -o ceph + ** sosreport -a + ** sosreprot -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 debugging data manually (outside an usual sosreport run) [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. ** Description changed: [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 - ** sosreprot -o ceph + ** 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 debugging data manually (outside an usual sosreport run) [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. ** Changed in: sosreport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Bionic) Importance: Undecided => Medium ** Description changed: [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 debugging data - manually (outside an usual sosreport run) + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910264 Title: [plugin][ceph] include time-sync-status for ceph mon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
