DescriptionMichael J. Kidd
2021-11-29 16:47:55 UTC
Description of problem:
RHCS 4.x does not have 'time-sync.target' in systemd unit files After or Wants lines. This allows Ceph services to start before time sync and can lead to unpredictable / unstable service interactions.
Version-Release number of selected component (if applicable):
RHCS 4.x
How reproducible:
100%
Steps to Reproduce:
1. Set BIOS time to a drastically wrong time ( as could happen after a motherboard swap )
2. Boot Ceph node
Actual results:
- Ceph services start with drastically wrong system time
- Ceph services are unable to properly start/join the cluster for normal operations
Expected results:
- Ceph services wait until time-sync is complete
- Then start with proper system time and operate normally
Additional info:
Wants/After entries of 'time-sync.target' are already part of RHCS 5. Request backport of these entries to RHCS 4 for more predictable system behavior after hardware changes.
See:
https://github.com/ceph/ceph/blob/v16.2.0/src/cephadm/cephadm#L2969-L2970
Comment 7Ameena Suhani S H
2022-05-23 20:18:25 UTC
Verified that time-sync.target is active
# rpm -qa|grep ansi
ansible-2.9.27-1.el8ae.noarch
ceph-ansible-4.0.70.5-1.el8cp.noarch
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Red Hat Ceph Storage 4.3 Bug Fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:6684