Re: Orchestrator: Cannot add node after mistake

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Aha. The error message is in the original complain. Very well. Carry on,
everyone.

On Fri, 19 Jun 2020 at 4:33 pm, John Zachary Dover <zac.dover@xxxxxxxxx>
wrote:

> Simon,
>
> Could you post the unhelpful error message? I can’t rewrite cephadm, but I
> can at least document this error message.
>
> Zac Dover
> Documentation
> Ceph
>
> On Fri, 19 Jun 2020 at 4:28 pm, Simon Sutter <ssutter@xxxxxxxxxxx> wrote:
>
>> After some hours of searching around in the docs and finaly taking a look
>> at the sourcecode of cephadm, I figured out it has to do with the docker
>> software (podman in my case).
>>
>> So I figured out that podman is not installed on the new node.
>> I never installed podman on any node so I don't know if my installation
>> was not good, or if cephadm just had a problem installing it.
>>
>> Also the message in the error is not very meaningful.
>>
>> For example, if I forget to install python3, the "python3 is not
>> installed" message is very clear.
>>
>>
>> Simon
>>
>> ________________________________
>> Von: Simon Sutter <ssutter@xxxxxxxxxxx>
>> Gesendet: Donnerstag, 18. Juni 2020 14:09:18
>> An: ceph-users@xxxxxxx
>> Betreff:  Orchestrator: Cannot add node after mistake
>>
>> Hello,
>>
>>
>> I did a mistake, while deploying a new node on octopus.
>> The node is a fresh installed Centos8 machine.
>> Bevore I did a "ceph orch host add node08" I pasted the wrong command:
>>
>> ceph orch daemon add osd node08:cl_node08/ceph
>>
>> That did not return anything, so I tried to add the node first with the
>> host add command, but now I get an error:
>> Error ENOENT: New host node08 (node08) failed check: ['Traceback (most
>> recent call last):', '  File "<stdin>", line 4580, in <module>', '  File
>> "<stdin>", line 3592, in command_check_host', "UnboundLocalError: local
>> variable 'container_path' referenced before assignment"]
>>
>>
>> I'm not a developer, so I don't know where to look, and how to fix this.
>>
>> I tried to reboot every node, to see if it's just a cached problem, but
>> no luck there.
>> Do any of you know how to fix this?
>>
>>
>> Thanks in advance,
>>
>> Simon
>> _______________________________________________
>> ceph-users mailing list -- ceph-users@xxxxxxx
>> To unsubscribe send an email to ceph-users-leave@xxxxxxx
>> _______________________________________________
>> ceph-users mailing list -- ceph-users@xxxxxxx
>> To unsubscribe send an email to ceph-users-leave@xxxxxxx
>>
>
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux