diff options
| author | Adam King <adking@dhcp-41-165.bos.redhat.com> | 2024-10-14 19:44:03 +0200 |
|---|---|---|
| committer | Adam King <adking@redhat.com> | 2024-10-24 20:51:34 +0200 |
| commit | 5818305e8094f88949a7a63c93c6d76d0efa03d9 (patch) | |
| tree | 9008ddc4fdde1f8d24137f3f94672e9e255d30f9 /src/cephadm/build.py | |
| parent | Merge pull request #59982 from rkachach/fix_issue_mgmt_gw_high_availability (diff) | |
| download | ceph-5818305e8094f88949a7a63c93c6d76d0efa03d9.tar.xz ceph-5818305e8094f88949a7a63c93c6d76d0efa03d9.zip | |
cephadm: handle "systemctl start" failures during deployment better
Previously it was assumed when the deploy command fails whatever
daemon we were trying to deploy does not exist on the host. However,
in the specific case where deploy fails trying to start the daemon's
systemd unit this is not the case. This leads us to both cleanup the
keyring for the daemon and also causes us to not trigger a refresh
of the daemons on the host which can make cephadm attempt to
deploy another daemon instead of just reporting the existing one
as failed. To get around this we need to handle that specific
failure as a success in the mgr module's deploy workflow so that
we refresh the daemons and report the failure as intended.
https://tracker.ceph.com/issues/68536
Signed-off-by: Adam King <adking@redhat.com>
Diffstat (limited to 'src/cephadm/build.py')
0 files changed, 0 insertions, 0 deletions