Bug 2232063 - [cee/sd] Error seen after applied osd specification file
Summary: [cee/sd] Error seen after applied osd specification file
Keywords:
Status: CLOSED DUPLICATE of bug 2209319
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Volume
Version: 5.3
Hardware: x86_64
OS: All
unspecified
medium
Target Milestone: ---
: 5.3z4
Assignee: Guillaume Abrioux
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-15 06:31 UTC by Geo Jose
Modified: 2023-08-16 11:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 11:23:26 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-7213 0 None None None 2023-08-15 06:33:15 UTC

Description Geo Jose 2023-08-15 06:31:52 UTC
Description of problem:
Customer was upgraded the cluster from RHCS 4 to RHCS 5. Currently all osds are in unmanaged state... Which is expected https://bugzilla.redhat.com/show_bug.cgi?id=2131230
They are trying to apply an osd config which covers all osds in their cluster for being able to replace faulty osd devices. But when they apply the new config, they get error.

''')): cephadm exited with an error code: 1, stderr:Inferring 
config 
...
Non-zero
 exit code 1 from /bin/podman run --rm --ipc=host --stop-signal=SIGTERM 
--authfile=/etc/ceph/podman-auth.json --net=host --entrypoint 
/usr/sbin/ceph-volume --privileged --group-add=disk --init -e ...
...
...
/bin/podman: stderr --> passed data devices: 0 physical, 8 LVM
/bin/podman: stderr --> relative data size: 1.0
/bin/podman: stderr --> passed block_db devices: 0 physical, 8 LVM
/bin/podman: stderr --> 8 fast allocations != 1 num_osds

Version-Release number of selected component (if applicable):
16.2.10-138.el8cp

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Osd spec is getting error

Expected results:
Osd spec applied successfully

Additional info:


Note You need to log in before you can comment on or make changes to this bug.