Description of problem: The AnsbileServlet, used by cluster upgrade, fails to execute the desired playbook. There are various errors that happen depending on cluster and host names. Version-Release number of selected component (if applicable): current master How reproducible: every time Steps to Reproduce: 1. Admin Portal, cluster table 2. Select a cluster and click Upgrade 3. Click through the upgrade modal and attempt to start the upgrade Actual results: Nothing happens Expected results: The ovirt-custer-upgrade.yml playbook is started with events generated and visible on the event log. Additional info: Related to patch https://gerrit.ovirt.org/c/ovirt-engine/+/112058 Found while I was working on BZ1750426
If the cluster name, or one of the host names, contains a dash, underscore or period, the playbook is not run. A base64 encoding exception is thrown before the playbook is set to the ansible-runner-service. If the cluster name and selected host names are all alpha, the ansible-runner-service is invoked, but the parameters are incorrect.
Turns out AnsibleServlet uses a different version of Jackson than the AnsibleRunnerHttpClient. This causes strange problems with serialization. Updating the servlet to use the same version as the runner should fix the serialization problem.
Steps: 1. Admin Portal, cluster table 2. Select a cluster and click Upgrade 3. Click through the upgrade modal and attempt to start the upgrade Results: Cluster is successfully upgraded. Verified: ovirt-engine-4.4.5.7-0.1.el8ev.noarch
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.