[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-09-17 Thread eyal edri (oVirt JIRA)
open, rebased it. > Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - > Still Failing! > > > Key: OVIRT-1613 > URL: https://ovirt-jir

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-30 Thread Ondra Machacek (oVirt JIRA)
ttps://gerrit.ovirt.org/#/c/81199/1 Path which fixes the job: https://gerrit.ovirt.org/#/c/81107/ > Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - > Still Failing! > > >

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-29 Thread eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri reassigned OVIRT-1613: Assignee: Ondra Machacek (was: infra) > Re: [oVirt Jenkins] ovirt-system-tests_ansible-su

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Martin Perina (oVirt JIRA)
] basic-suite-master: add cold_storage_migration test > >> > >> [Barak Korren] Adapting OST manual job to macro changes > >> > >> [Daniel Belenky] Add support for secrets and credentials to STD CI > >> > >> > >> Changes for Build #6 > &g

Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Martin Perina
On Thu, Aug 24, 2017 at 9:01 AM, Nadav Goldin wrote: > Adding @infra-support to open a ticket. > > 1. From the console logs the error seems to be: > > 02:50:07 TASK [ovirt-deploy : Import template from glance] > ** > 02:50:12 An exception occurred during task execution

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Nadav Goldin (oVirt JIRA)
.com/lago-project/lago/blob/master/tests/functional-sdk/test_sdk_sanity.py#L257 in the suite's control.sh: {code} export ANSIBLE_LOG_PATH=$PWD/exported-artifacts/ansible.log {code} > Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - >

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Barak Korren (oVirt JIRA)
d Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - > Still Failing! > > > Key: OVI

Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Barak Korren
On 24 August 2017 at 10:01, Nadav Goldin wrote: > > 3. I recommend adding '-vvv' to the ansible command. Might get more > verbose logs, but easier to debug next time. > > We might also want to save Ansible logs to somewhere other then STDOUT for easier grepping... -- Barak Korren RHV DevOps te

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Nadav Goldin (oVirt JIRA)
Nadav Goldin created OVIRT-1613: --- Summary: Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing! Key: OVIRT-1613 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1613

Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-24 Thread Nadav Goldin
Adding @infra-support to open a ticket. 1. From the console logs the error seems to be: 02:50:07 TASK [ovirt-deploy : Import template from glance] ** 02:50:12 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeErro

Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!

2017-08-23 Thread Martin Perina
Hi, Ansible test suite is failing for a few days, Lago says that it's failing on engine initialization. I've been looking on the logs, but I was unable to find any error. But there's something strange in wildfly logs on engine: 1. boot.log looks good, I see that WildFly 11 is starting 2. server.l