This NPE seems to be more related to ansible execution rather than to wildfly.

It is thrown here [1]

...

JsonNode okNode = readUrl(String.format("jobs/%1$s/events/%2$s", playUuid, event));

JsonNode data = okNode.get("data");

NPE>>> String action = data.get("event_data").get("task_action").asText();

...

Dana, Martin N, does this "data" object come from the ansible runner?

[1] https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/common/utils/ansible/AnsibleRunnerHttpClient.java#L223

On Wed, Jan 20, 2021 at 10:19 AM Yedidyah Bar David <didi@redhat.com> wrote:

On Wed, Jan 20, 2021 at 10:53 AM Yedidyah Bar David <didi@redhat.com> wrote:
>
> Hi all,
>
> Got NPE on patched he-basic-suite-master while adding host-1 (not
> during initial deploy). Known issue? Perhaps related to updated
> wildfly?
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/15048/
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/15048/artifact/check-patch.basic_suite_master.el8.x86_64/test_logs/basic-suite-master/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
> :
>
> 2021-01-20 08:00:27,449+01 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-2) [4da9f40c] EVENT_ID:
> ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Installing Host
> lago-basic-suite-master-host-1. restart libvirtd.
> 2021-01-20 08:00:27,452+01 ERROR
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (EE-ManagedThreadFactory-engine-Thread-2) [4da9f40c] Exception: null
> 2021-01-20 08:00:27,452+01 DEBUG
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (EE-ManagedThreadFactory-engine-Thread-2) [4da9f40c] Exception: :
> java.lang.NullPointerException

The same error fails also basic-suite-master nightly:

https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/

Last successful one is from a day ago, with engine commit 0d2c8b5b78e,
which already included wildfly 22, so perhaps that's unrelated.

>
> "restart libvirtd" task itself seems successful, based on host-deploy log.
>
> Thanks and best regards,
> --
> Didi

--
Didi