Bug 2258542
Summary: | ceph-objectstore-tool and ceph-bluestore-tool fail with mount error post upgrade | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Harsh Kumar <hakumar> |
Component: | Cephadm | Assignee: | Adam King <adking> |
Status: | CLOSED ERRATA | QA Contact: | Harsh Kumar <hakumar> |
Severity: | urgent | Docs Contact: | Akash Raj <akraj> |
Priority: | unspecified | ||
Version: | 7.0 | CC: | adking, akraj, bhubbard, ceph-eng-bugs, cephqe-warriors, nojha, rzarzyns, tserlin, vdas, vumrao |
Target Milestone: | --- | Keywords: | Automation, Regression |
Target Release: | 7.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ceph-18.2.1-99.el9cp | Doc Type: | Bug Fix |
Doc Text: |
.Using the '--name NODE' flag with the cephadm shell to start a stopped OSD no longer returns the wrong image container
Previously, in some cases, when using the `cephadm shell --name NODE` command, the command would start the container with the wrong version of the tools. This would occur when a user has a newer ceph container image on the host than the one that their OSDs are using.
With this fix, Cephadm determines the container image for stopped daemons when using the cephadm shell command with the `--name` flag. Users no longer have any issues with the `--name` flag, and the command works as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-13 14:24:35 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: | |||
Bug Blocks: | 2267614, 2298578, 2298579 |
Description
Harsh Kumar
2024-01-16 03:41:26 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 (Critical: Red Hat Ceph Storage 7.1 security, enhancements, 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-2024:3925 |