<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 24, 2017 at 9:01 AM, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Adding @infra-support to open a ticket.<br>
<br>
1. From the console logs the error seems to be:<br>
<br>
02:50:07 TASK [ovirt-deploy : Import template from glance]<br>
******************************<br>
02:50:12 An exception occurred during task execution. To see the full<br>
traceback, use -vvv. The error was: AttributeError: 'TemplatesModule'<br>
object has no attribute 'wait_for_import'<br>
02:50:12 fatal: [lago-ansible-suite-master-<wbr>engine]: FAILED! =><br>
{"changed": false, "failed": true, "msg": "'TemplatesModule' object<br>
has no attribute 'wait_for_import'"}<br>
02:50:12 to retry, use: --limit<br>
@/home/jenkins/workspace/<wbr>ovirt-system-tests_ansible-<wbr>suite-master/ovirt-system-<wbr>tests/ansible-suite-master/<wbr>engine.retry<br>
<br>
Maybe something changed recently in the Ansible roles?<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Ahh, somehow it didn't come to my mind that in console might be more than in artifacts :-(<br></div><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">I will post a fix for that.<br></div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2. There is a bug in the suite, that when the ansible deploy fails,<br>
the logs are not collected. That is why you see no logs(the logs you<br>
see are right after 'initialize_engine', and not after the ansible<br>
failure).<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Hmm, I will take a look to other suites what's the difference around collecting logs and post a fix for that<br></div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
3. I recommend adding '-vvv' to the ansible command. Might get more<br>
verbose logs, but easier to debug next time. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Thanks,<br>
<br>
Nadav.<br></blockquote><div><br><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Thanks a lot!<br><br></div><div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">Martin<br></div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>> wrote:<br>
> Hi,<br>
><br>
> Ansible test suite is failing for a few days, Lago says that it's failing on<br>
> engine initialization. I've been looking on the logs, but I was unable to<br>
> find any error. But there's something strange in wildfly logs on engine:<br>
><br>
> 1. boot.log looks good, I see that WildFly 11 is starting<br>
> 2. server.log also looks good, I see engine was deployed, but it seems to me<br>
> that it's not complete (like WildFly was killed during engine deployment)<br>
> 3. engine.log is completely empty - that's very strange, but it's probably<br>
> related to my suspicion above<br>
><br>
> In lago logs I can see that ovirt-engine service is being started, but no<br>
> info about being killed/stop.<br>
><br>
> Any idea what could have happened?<br>
><br>
> Thanks a lot<br>
><br>
> Martin<br>
><br>
><br>
> On Thu, Aug 24, 2017 at 4:50 AM, <<a href="mailto:jenkins@jenkins.phx.ovirt.org">jenkins@jenkins.phx.ovirt.org</a><wbr>> wrote:<br>
>><br>
>> Project:<br>
>> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>ovirt-system-tests_ansible-<wbr>suite-master/</a><br>
>> Build:<br>
>> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>ovirt-system-tests_ansible-<wbr>suite-master/7/</a><br>
>> Build Number: 7<br>
>> Build Status: Still Failing<br>
>> Triggered By: Started by timer<br>
>><br>
>> ------------------------------<wbr>-------<br>
>> Changes Since Last Success:<br>
>> ------------------------------<wbr>-------<br>
>> Changes for Build #5<br>
>> [Eyal Shenitzky] basic-suite-master: add cold_storage_migration test<br>
>><br>
>> [Barak Korren] Adapting OST manual job to macro changes<br>
>><br>
>> [Daniel Belenky] Add support for secrets and credentials to STD CI<br>
>><br>
>><br>
>> Changes for Build #6<br>
>> No changes<br>
>><br>
>> Changes for Build #7<br>
>> [Your Name] Use a long name with special chars as a network name<br>
>><br>
>> [Barak Korren] Fix small bug in slave repo setup<br>
>><br>
>> [Daniel Belenky] mock_runner fix empty mrmap bug<br>
>><br>
>><br>
>><br>
>><br>
>> -----------------<br>
>> Failed Tests:<br>
>> -----------------<br>
>> All tests passed<br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Infra mailing list<br>
> <a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/infra</a><br>
><br>
</blockquote></div><br></div></div>