<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34776#comment-34776 ]</pre>
<h3>Martin Perina commented on OVIRT-1613:</h3>
<p>On Thu, Aug 24, 2017 at 9:01 AM, Nadav Goldin <ngoldin@redhat.com> wrote:</p>
<blockquote><p>Adding @infra-support to open a ticket.</p>
<ol><li><p>From the console logs the error seems to be:</p></li></ol>
<p>02:50:07 TASK [ovirt-deploy : Import template from glance] <strong>***************************</strong>* 02:50:12 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: ‘TemplatesModule’ object has no attribute ‘wait_for_import’ 02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! => {"changed": false, “failed”: true, “msg”: “'TemplatesModule' object has no attribute 'wait_for_import'”} 02:50:12 to retry, use: --limit @/home/jenkins/workspace/ovirt-system-tests_ansible- suite-master/ovirt-system-tests/ansible-suite-master/engine.retry</p>
<p>Maybe something changed recently in the Ansible roles?</p></blockquote>
<p>Ahh, somehow it didn't come to my mind that in console might be more than in artifacts <span class="smiley-sad">:-(</span> I will post a fix for that. </p>
<blockquote><pre>2. There is a bug in the suite, that when the ansible deploy fails,
the logs are not collected. That is why you see no logs(the logs you
see are right after 'initialize_engine', and not after the ansible
failure).</pre></blockquote>
<p>Hmm, I will take a look to other suites what's the difference around collecting logs and post a fix for that </p>
<blockquote><pre>3. I recommend adding '-vvv' to the ansible command. Might get more
verbose logs, but easier to debug next time.</pre>
<pre>Thanks,</pre>
<pre>Nadav.</pre></blockquote>
<p>Thanks a lot!</p>
<p>Martin </p>
<blockquote><pre>On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <mperina@redhat.com> wrote:
> 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.log also looks good, I see engine was deployed, but it seems
to me
> that it's not complete (like WildFly was killed during engine deployment)
> 3. engine.log is completely empty - that's very strange, but it's
probably
> related to my suspicion above
>
> In lago logs I can see that ovirt-engine service is being started, but no
> info about being killed/stop.
>
> Any idea what could have happened?
>
> Thanks a lot
>
> Martin
>
>
> On Thu, Aug 24, 2017 at 4:50 AM, <jenkins@jenkins.phx.ovirt.org> wrote:
>>
>> Project:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/
>> Build:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/
>> Build Number: 7
>> Build Status: Still Failing
>> Triggered By: Started by timer
>>
>> -------------------------------------
>> Changes Since Last Success:
>> -------------------------------------
>> Changes for Build #5
>> [Eyal Shenitzky] 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
>> No changes
>>
>> Changes for Build #7
>> [Your Name] Use a long name with special chars as a network name
>>
>> [Barak Korren] Fix small bug in slave repo setup
>>
>> [Daniel Belenky] mock_runner fix empty mrmap bug
>>
>>
>>
>>
>> -----------------
>> Failed Tests:
>> -----------------
>> All tests passed
>
>
>
> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
></pre>
<pre>Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
----------------------------------------------------------------------------------------</pre>
<pre> Key: OVIRT-1613
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1613
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nadav Goldin
Assignee: infra</pre>
<pre>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: AttributeError: 'TemplatesModule'
object has no attribute 'wait_for_import'
02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! =>
{"changed": false, "failed": true, "msg": "'TemplatesModule' object
has no attribute 'wait_for_import'"}
02:50:12 to retry, use: --limit
@/home/jenkins/workspace/ovirt-system-tests_ansible-suite-master/ovirt-system-tests/ansible-suite-master/engine.retry
Maybe something changed recently in the Ansible roles?
2. There is a bug in the suite, that when the ansible deploy fails,
the logs are not collected. That is why you see no logs(the logs you
see are right after 'initialize_engine', and not after the ansible
failure).
3. I recommend adding '-vvv' to the ansible command. Might get more
verbose logs, but easier to debug next time.
Thanks,
Nadav.
On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <mperina@redhat.com> wrote:
> 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.log also looks good, I see engine was deployed, but it seems to me
> that it's not complete (like WildFly was killed during engine deployment)
> 3. engine.log is completely empty - that's very strange, but it's probably
> related to my suspicion above
>
> In lago logs I can see that ovirt-engine service is being started, but no
> info about being killed/stop.
>
> Any idea what could have happened?
>
> Thanks a lot
>
> Martin
>
>
> On Thu, Aug 24, 2017 at 4:50 AM, <jenkins@jenkins.phx.ovirt.org> wrote:
>>
>> Project:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/
>> Build:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/
>> Build Number: 7
>> Build Status: Still Failing
>> Triggered By: Started by timer
>>
>> -------------------------------------
>> Changes Since Last Success:
>> -------------------------------------
>> Changes for Build #5
>> [Eyal Shenitzky] 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
>> No changes
>>
>> Changes for Build #7
>> [Your Name] Use a long name with special chars as a network name
>>
>> [Barak Korren] Fix small bug in slave repo setup
>>
>> [Daniel Belenky] mock_runner fix empty mrmap bug
>>
>>
>>
>>
>> -----------------
>> Failed Tests:
>> -----------------
>> All tests passed
>
>
>
> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
></pre></blockquote>
<p>— This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzYS3r1Q939T2sgz00sI6zvNxnwm27FgDR2ZAx4QicEDXu44U1O-2BKkh3gIJe46ueY-2B1u2Ygloo51Rs5tOkq-2B0XvAfAz8llUVUImRKNYp3FlXolOIL1vYUzUTm5OSINysEHQR-2Be3YY3bG6q6wwO5r5eV-2F8yEiF67yHSiEx53PW9yi8wUNoa99QNdFIwzINKigls9fjLOT-2BOUnqqoT0-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>