build-artifacts are failing because glusterfs is not signed. Sandro opened a bug On Tue, Mar 5, 2019 at 11:57 AM oVirt Jenkins <jenkins@ovirt.org> wrote:

A system test invoked by the "ovirt-4.3" change queue including change 98234,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 97519,2 (ovirt-node-ng-image) that this change depends on or is based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97519,2 (ovirt-node-ng-image) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it.

For further details about the change see: https://gerrit.ovirt.org/#/c/98234/1

For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97519/2

For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/123/ _______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BABZPGFFRU5YU5...