yes
Am 11.03.21 um 15:46 schrieb Kai Stian Olstad:
> Hi Sebastian
>
> On 11.03.2021 13:13, Sebastian Wagner wrote:
>> looks like
>>
>> $ ssh pech-hd-009
>> # cephadm ls
>>
>> is returning this non-existent OSDs.
>>
>> can you verify that `cephadm ls` on that host doesn't
>> print osd.355 ?
>
>
Hi Kai,
looks like
$ ssh pech-hd-009
# cephadm ls
is returning this non-existent OSDs.
can you verify that `cephadm ls` on that host doesn't
print osd.355 ?
Best,
Sebastian
Am 11.03.21 um 12:16 schrieb Kai Stian Olstad:
> Before I started the upgrade the cluster was healthy but one
>
On 11.03.2021 15:47, Sebastian Wagner wrote:
yes
Am 11.03.21 um 15:46 schrieb Kai Stian Olstad:
To resolve it, could I just remove it with "cephadm rm-daemon"?
That worked like a charm, and the upgrade is resumed.
Thank you Sebastian.
--
Kai Stian Olstad
Hi Sebastian
On 11.03.2021 13:13, Sebastian Wagner wrote:
looks like
$ ssh pech-hd-009
# cephadm ls
is returning this non-existent OSDs.
can you verify that `cephadm ls` on that host doesn't
print osd.355 ?
"cephadm ls" on the node does list this drive
{
"style": "cephadm:v1",
