On Thu, Oct 8, 2020 at 5:13 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Oct 8, 2020 at 5:08 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Oct 8, 2020 at 4:59 PM Dana Elfassy <delfassy@redhat.com> wrote:
And also please attach the content of the file found at: /etc/ansible-runner-service/config.yaml
On Thu, Oct 8, 2020 at 5:55 PM Dana Elfassy <delfassy@redhat.com> wrote:
Hi Gianluca, Please execute the following command on your engine, save the output into a file and attach it: sudo journalctl -u ansible-runner-service Dana
Thanks for answering, Dana.
[root@ovmgr1 ansible-runner-service]# sudo journalctl -u ansible-runner-service -- Logs begin at Tue 2020-10-06 11:12:46 CEST, end at Thu 2020-10-08 17:02:25 CEST. -- -- No entries -- [root@ovmgr1 ansible-runner-service]#
[root@ovmgr1 ansible-runner-service]# cat /etc/ansible-runner-service/config.yaml
version: 1 playbooks_root_dir: '/usr/share/ovirt-engine/ansible-runner-service-project' ssh_private_key: '/etc/pki/ovirt-engine/keys/engine_id_rsa' port: 50001 target_user: root log_path: '/var/log/ovirt-engine' [root@ovmgr1 ansible-runner-service]#
I noticed that both on engine and on host the "ansible-runner" package is not installed. Is it correct and only ansible-runner-service package to be installed only on the engine? Also, does the "service" in the name imply that I should have any systemd or other kind of related service on engine? Finally, I have to use a proxy for dnf/yum. To be able to run "engine-setup" on engine I had to set http_proxy and https_proxy eng variables inside the shell session, because it seems that engine-setup was not able to leverage the global configuration. Could it be something similar due to the host having to use a proxy too (that I already setup in /etc/dnf/dnf.conf)? Just a guess.
Gianluca
Also, the host already existed in 4.3. I upgraded the standalone engine from 4.3.10 to 4.4.2 following the guide. Now to update my hosts I put a host into maintenance, removed the host from the gui, reinstalled the server in CentOS 8.2 with same network parameters, and then add new host with the same name/hostname as before. Could it be a problem to reuse the host?
Gianluca
Any other thing to check to be able to provision a node in 4.4.2 using plain CentOS 8.2 host? Thanks, Gianluca