| 2021-01-05 16:07:04 |
Eric Desrochers |
bug |
|
|
added bug |
| 2021-01-05 16:07:16 |
Eric Desrochers |
bug |
|
|
added subscriber Dan Hill |
| 2021-01-05 16:07:22 |
Eric Desrochers |
bug |
|
|
added subscriber Ponnuvel Palaniyappan |
| 2021-01-05 16:07:25 |
Eric Desrochers |
tags |
|
seg sts |
|
| 2021-01-05 16:12:27 |
Eric Desrochers |
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.
Issues:
https://github.com/sosreport/sos/issues/2356
PR:
https://github.com/sosreport/sos/pull/2357/commits/7859968b6e5e26c11d4bf4d8349646bd74723e52 |
[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
Upstream documentation about the option:
https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/
[Test Case]
[Where problems could occur]
[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.
Issues:
https://github.com/sosreport/sos/issues/2356
PR:
https://github.com/sosreport/sos/pull/2357/commits/7859968b6e5e26c11d4bf4d8349646bd74723e52 |
|
| 2021-01-05 16:12:49 |
Eric Desrochers |
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
Upstream documentation about the option:
https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/
[Test Case]
[Where problems could occur]
[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.
Issues:
https://github.com/sosreport/sos/issues/2356
PR:
https://github.com/sosreport/sos/pull/2357/commits/7859968b6e5e26c11d4bf4d8349646bd74723e52 |
[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
Upstream documentation about the option:
https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/
[Test Case]
[Where problems could occur]
[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. |
|
| 2021-01-05 16:13:04 |
Eric Desrochers |
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
Upstream documentation about the option:
https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/
[Test Case]
[Where problems could occur]
[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. |
[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]
[Where problems could occur]
[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. |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Bionic) |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
nominated for series |
|
Ubuntu Focal |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Focal) |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Hirsute) |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-01-05 16:13:14 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Groovy) |
|
| 2021-01-05 16:13:35 |
Eric Desrochers |
sosreport (Ubuntu Hirsute): assignee |
|
Eric Desrochers (slashd) |
|
| 2021-01-05 16:13:38 |
Eric Desrochers |
sosreport (Ubuntu Hirsute): status |
New |
In Progress |
|
| 2021-01-05 16:13:41 |
Eric Desrochers |
sosreport (Ubuntu Hirsute): importance |
Undecided |
Low |
|
| 2021-01-05 16:13:50 |
Eric Desrochers |
sosreport (Ubuntu Groovy): assignee |
|
Ponnuvel Palaniyappan (pponnuvel) |
|
| 2021-01-05 16:13:59 |
Eric Desrochers |
sosreport (Ubuntu Focal): assignee |
|
Ponnuvel Palaniyappan (pponnuvel) |
|
| 2021-01-05 16:14:06 |
Eric Desrochers |
sosreport (Ubuntu Bionic): assignee |
|
Ponnuvel Palaniyappan (pponnuvel) |
|
| 2021-01-05 16:33:39 |
Eric Desrochers |
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]
[Where problems could occur]
[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. |
[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. |
|
| 2021-01-05 16:34:11 |
Eric Desrochers |
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]
* 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. |
[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
[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. |
|
| 2021-01-05 16:34:26 |
Eric Desrochers |
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
** 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. |
[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)
[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. |
|
| 2021-01-05 16:34:44 |
Eric Desrochers |
sosreport (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2021-01-05 16:34:46 |
Eric Desrochers |
sosreport (Ubuntu Groovy): importance |
Undecided |
Medium |
|
| 2021-01-05 16:34:50 |
Eric Desrochers |
sosreport (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2021-01-05 16:42:34 |
Eric Desrochers |
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 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. |
[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. |
|
| 2021-01-05 23:08:34 |
Launchpad Janitor |
sosreport (Ubuntu Hirsute): status |
In Progress |
Fix Released |
|
| 2021-01-07 13:53:02 |
Ponnuvel Palaniyappan |
sosreport (Ubuntu Bionic): status |
New |
In Progress |
|
| 2021-01-07 13:53:04 |
Ponnuvel Palaniyappan |
sosreport (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-01-07 13:53:06 |
Ponnuvel Palaniyappan |
sosreport (Ubuntu Groovy): status |
New |
Incomplete |
|
| 2021-01-07 13:53:08 |
Ponnuvel Palaniyappan |
sosreport (Ubuntu Groovy): status |
Incomplete |
In Progress |
|
| 2021-01-07 13:53:47 |
Ponnuvel Palaniyappan |
attachment added |
|
bionic.debdiff https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1910264/+attachment/5450255/+files/bionic.debdiff |
|
| 2021-01-07 13:54:22 |
Ponnuvel Palaniyappan |
attachment added |
|
focal.debdiff https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1910264/+attachment/5450256/+files/focal.debdiff |
|
| 2021-01-07 13:54:43 |
Ponnuvel Palaniyappan |
attachment added |
|
groovy.debdiff https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1910264/+attachment/5450257/+files/groovy.debdiff |
|
| 2021-01-07 15:20:57 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2021-01-07 15:21:11 |
Eric Desrochers |
tags |
seg sts |
seg sts sts-sponsors-slashd |
|
| 2021-01-27 13:31:08 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2021-01-28 13:21:40 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2021-02-18 09:48:13 |
Łukasz Zemczak |
sosreport (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-02-18 09:48:15 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-02-18 09:48:17 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2021-02-18 09:48:21 |
Łukasz Zemczak |
tags |
seg sts sts-sponsors-slashd |
seg sts sts-sponsors-slashd verification-needed verification-needed-groovy |
|
| 2021-02-18 09:51:27 |
Łukasz Zemczak |
sosreport (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-02-18 09:51:33 |
Łukasz Zemczak |
tags |
seg sts sts-sponsors-slashd verification-needed verification-needed-groovy |
seg sts sts-sponsors-slashd verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-02-19 22:08:41 |
Ponnuvel Palaniyappan |
attachment added |
|
time-sync-verification-focal.txt https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+attachment/5465390/+files/time-sync-verification-focal.txt |
|
| 2021-02-19 22:08:58 |
Ponnuvel Palaniyappan |
tags |
seg sts sts-sponsors-slashd verification-needed verification-needed-focal verification-needed-groovy |
seg sts sts-sponsors-slashd verification-done-focal verification-needed verification-needed-groovy |
|
| 2021-02-19 23:40:08 |
Ponnuvel Palaniyappan |
attachment added |
|
time-sync-verification-groovy.txt https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+attachment/5465394/+files/time-sync-verification-groovy.txt |
|
| 2021-02-19 23:40:37 |
Ponnuvel Palaniyappan |
tags |
seg sts sts-sponsors-slashd verification-done-focal verification-needed verification-needed-groovy |
seg sts sts-sponsors-slashd verification-done-focal verification-done-groovy verification-needed |
|
| 2021-03-23 20:32:06 |
Eric Desrochers |
sosreport (Ubuntu Groovy): status |
Fix Committed |
In Progress |
|
| 2021-03-25 14:15:17 |
Łukasz Zemczak |
sosreport (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-03-25 14:15:24 |
Łukasz Zemczak |
tags |
seg sts sts-sponsors-slashd verification-done-focal verification-done-groovy verification-needed |
seg sts sts-sponsors-slashd verification-done-focal verification-needed verification-needed-groovy |
|
| 2021-03-29 12:38:52 |
Łukasz Zemczak |
tags |
seg sts sts-sponsors-slashd verification-done-focal verification-needed verification-needed-groovy |
seg sts sts-sponsors-slashd verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-03-29 13:05:16 |
Łukasz Zemczak |
sosreport (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2021-03-29 13:05:23 |
Łukasz Zemczak |
tags |
seg sts sts-sponsors-slashd verification-needed verification-needed-focal verification-needed-groovy |
seg sts sts-sponsors-slashd verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
|
| 2021-04-01 17:44:48 |
Ponnuvel Palaniyappan |
attachment added |
|
time-sync-bionic-sru-verify.txt https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+attachment/5483226/+files/time-sync-bionic-sru-verify.txt |
|
| 2021-04-01 17:45:06 |
Ponnuvel Palaniyappan |
tags |
seg sts sts-sponsors-slashd verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
seg sts sts-sponsors-slashd verification-done-bionic verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-04-01 17:47:11 |
Ponnuvel Palaniyappan |
attachment added |
|
time-sync-focal-sru-verify.txt https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+attachment/5483227/+files/time-sync-focal-sru-verify.txt |
|
| 2021-04-01 17:47:37 |
Ponnuvel Palaniyappan |
tags |
seg sts sts-sponsors-slashd verification-done-bionic verification-needed verification-needed-focal verification-needed-groovy |
seg sts sts-sponsors-slashd verification-done-bionic verification-done-focal verification-needed verification-needed-groovy |
|
| 2021-04-01 18:09:45 |
Ponnuvel Palaniyappan |
attachment added |
|
time-sync-groovy-sru-verify.txt https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1910264/+attachment/5483241/+files/time-sync-groovy-sru-verify.txt |
|
| 2021-04-01 18:10:03 |
Ponnuvel Palaniyappan |
tags |
seg sts sts-sponsors-slashd verification-done-bionic verification-done-focal verification-needed verification-needed-groovy |
seg sts sts-sponsors-slashd verification-done verification-done-bionic verification-done-focal verification-done-groovy |
|
| 2021-04-07 13:23:24 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2021-04-12 17:02:04 |
Launchpad Janitor |
sosreport (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-04-12 17:02:26 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-04-12 17:10:11 |
Launchpad Janitor |
sosreport (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-04-12 17:16:54 |
Launchpad Janitor |
sosreport (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
