Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1869368

Summary:	Just after adding host to Engine - Failed to execute Ansible host-deploy role: Internal server error
Product:	[oVirt] ovirt-engine	Reporter:	David <david.hepler>
Component:	ovirt-host-deploy-ansible	Assignee:	Martin Perina <mperina>
Status:	CLOSED NOTABUG	QA Contact:	Yaning Wang <yaniwang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4.1.10	CC:	bugs, michal.skrivanek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-20 08:46:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David 2020-08-17 17:41:55 UTC

Description of problem:

Receiving error "Host HOSTNAME-01 installation failed. Failed to execute Ansible host-deploy role: Internal server error. Please check logs for more details: /var/log/ovirt-engine/ansible-runner-service.log."

This is similar (but not the same) to Bug 1784010: https://bugzilla.redhat.com/show_bug.cgi?id=1784010# that was supposed to be fixed in Engine 4.4.0

The host has been reinstalled multiple times, same result. The log "/var/log/ovirt-engine/ansible-runner-service.log" is empty and couldn't see any other recently written logs that had much to help.

Version-Release number of selected component (if applicable):
oVirt Engine: 4.4.1.10
oVirt Node: "4.4.1-2020080418" and "4.4.1-2020072310"

How reproducible:

Steps to Reproduce:
1. Simply install a node
2. Try to add the node (IP or FQDN)
3. Install fails right away

Actual results:
Receiving error "Host HOSTNAME-01 installation failed. Failed to execute Ansible host-deploy role: Internal server error. Please check logs for more details: /var/log/ovirt-engine/ansible-runner-service.log."

Expected results:
New host added to oVirt successfully

Additional info:
This is my first ever bugzilla submission, please let me know if I could do something better.

I upgraded the oVirt Engine from 4.3.9 to 4.4.0. I added newly installed oVirt 4.4 hosts, migrated VMs to new hosts and removed old 4.3 hosts. I then changed the compatibility level to 4.4. Last week I updated the engine to 4.4.1.10. I then wanted to install the most recent host patches, which failed from oVirt Engine but was successful from the host. That host was non-responsive after it's reboot.
I removed the host (no time to debug) and reinstalled it (using both oVirt Node "4.4.1-2020080418" and "4.4.1-2020072310".

Comment 1 Michal Skrivanek 2020-08-18 04:10:46 UTC

Can you please attach logs?

Comment 2 RHEL Program Management 2020-08-18 04:10:54 UTC

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 3 David 2020-08-18 09:45:20 UTC

I can attach logs but after doing more analysis of my problem (I'm a one-person show and only started with oVirt at 4.3) it looks like I have a general problem where Ansible is not running any kind of playbooks. (Check update also fails with the same error and the current "ansible-runner-service.log" has 0 bytes. Before I waste your and my time, would it make more sense for me just to reinstall my oVirt Engine first and see if I can get things working that way?

As for the logs, which logs should I attach? As I said, the current ansible-runner-service.log is empty...

Comment 4 David 2020-08-19 21:41:45 UTC

I have solved my problem by reinstalling ovirt engine. I am not sure what the problem was, but I am not sure it was actually a bug as the problem was resolved after backing up my engine, reinstalling it and restoring the database.

This case can be closed.