Bug 2080926
Summary: | [cephadm][ingress]: AssertionError seen upon restarting haproxy and keepalived using service name | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Madhavi Kasturi <mkasturi> |
Component: | Cephadm | Assignee: | Redouane Kachach Elhichou <rkachach> |
Status: | CLOSED ERRATA | QA Contact: | Aditya Ramteke <aramteke> |
Severity: | low | Docs Contact: | Akash Raj <akraj> |
Priority: | unspecified | ||
Version: | 5.1 | CC: | adking, akraj, msaini, rkachach |
Target Milestone: | --- | ||
Target Release: | 6.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-17.2.6-5.el9cp | Doc Type: | Enhancement |
Doc Text: |
.Better error handling when daemon names are passed to `ceph orch restart` command
Previously, in cases where the daemon passed to `ceph orch restart` command was a haproxy or keepalived daemon, it would return a traceback. This made it unclear to users if they had made a mistake or Cephadm had failed in some other way.
With this release, better error handling is introduced to identify when the users pass a daemon name to `ceph orch restart` command instead of the expected service name. Upon encountering a daemon name, Cephadm reports and requests the user to check `ceph orch ls` for valid services to pass.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-06-15 09:15:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2180567 | ||
Bug Blocks: | 2192813 |
Comment 3
Redouane Kachach Elhichou
2022-05-31 10:21:59 UTC
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 (Moderate: Red Hat Ceph Storage 6.1 security and 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/RHSA-2023:3623 |