Hi David,
you can always prohibit root and also make an exclusion for specific hosts
(like oVirt's Engine).
Maybe something like :
Match Address 192.168.2.5
PermitRootLogin yes
Source:
https://www.cyberciti.biz/faq/match-address-sshd_config-allow-root-loginfrom-one_ip_address-on-linux
Thank you, Ritesh.
Those logs were perfect, and I immediately found the problem.
This was my fault.
I had disabled Root Login in /etc/ssh/sshd_config (because let's face it, we
all can agree that logging in as root over ssh is normally a bad idea!)
I just updated that from "no" to "prohibit-pass
Hello,
Can you check at which task the upgrade has struck. Please share the
relevant log at the time.
To check at which tasks it failed ssh to ovirt engine and navigate to
directory /var/log/ovirt-engine/host-deploy/ and also share the vdsm logs
from host as well.
On Sun, May 23, 2021 at 7:
I'm saw something similar on a test cluster on CentOS 8.3.
You can take it out of global maintenance mode by navigating the engine UI
to edit cluster -> scheduling policy and turn off global maintenance there.
Not sure what else is going on. It wants me to put all three hosts into
maintenance mod
4 matches
Mail list logo
