Ok, so I created the gluster volumes manually. It came out that
virtualization was disabled in bios on the new servers. After enabling the
virtualization I run standard wizard for creating hosted engine and choose
gluster volume as location for it. It looks like it is ok now. Thanks.
On Thu, Oct
Yes, bq817 is the one with cockpit. Yes I can ssh locally by using full
host name too.
I checked with tcpdump and there isn't any ssh connection try during the
deployment on any of the network interfaces. Strange...
On Thu, Oct 25, 2018 at 3:15 PM Jayme wrote:
> Is the host in the error the
Is the host in the error the same host you are running cockpit from? Make
sure you can ssh not to localhost by to the hostname from the host. I.e.
on bq817storage.example.com try ssh'ing to r...@bq817storage.example.com
On Thu, Oct 25, 2018 at 9:06 AM Jarosław Prokopowski
wrote:
> And because
And because I sometimes ssh through the main (non-storage) network
interface i have local .ssh/config file on the root account with:
Host *
StrictHostKeyChecking no
On Thu, Oct 25, 2018 at 2:03 PM Jarosław Prokopowski
wrote:
> Hi,
>
> Yes ssh keys have been distributed and root remote
Hi,
Yes ssh keys have been distributed and root remote login works each way.
After I got the error I tested all connection manually and they work.
On every host I can ssh to root@localhost and to other hosts without any
problem.
That's why the error is so strange to me. I event tested ansible
You should also make sure the host can ssh to itself and accept keys
On Thu, Oct 25, 2018, 8:42 AM Jayme, wrote:
> Darn autocorrect, sshd config rather
>
> On Thu, Oct 25, 2018, 7:29 AM Jarosław Prokopowski, <
> jprokopow...@gmail.com> wrote:
>
>> Hi,
>>
>> Please help! :-) I couldn't find any
Darn autocorrect, sshd config rather
On Thu, Oct 25, 2018, 7:29 AM Jarosław Prokopowski,
wrote:
> Hi,
>
> Please help! :-) I couldn't find any solution via google.
>
> I followed this document to create oVirt hyperconverged on 3 hosts using
> cockpit wizard:
>
>
>
It looks to me like a fairly obvious ssh problem. Are the ssh keys setup
for root user and permitrootlogin yes in Asheville config?
On Thu, Oct 25, 2018, 7:29 AM Jarosław Prokopowski,
wrote:
> Hi,
>
> Please help! :-) I couldn't find any solution via google.
>
> I followed this document to
8 matches
Mail list logo
