8:28 a.m.
This is a multi-part message in MIME format...
------------=_1504013319-10702-217
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jir...
]
eyal edri reassigned OVIRT-1613:
--------------------------------
Assignee: Ondra Machacek (was: infra)
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
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nadav Goldin
Assignee: Ondra Machacek
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(a)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(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)
------------=_1504013319-10702-217
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jir...
]</pre>
<h3>eyal edri reassigned OVIRT-1613:</h3>
<pre>Assignee: Ondra Machacek (was: infra)</pre>
<blockquote><h3>Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master
– Build # 7 – Still Failing!</h3>
<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: Ondra Machacek</pre>
<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
Maybe something changed recently in the Ansible roles?</p>
<ol><li><p>There is a bug in the suite, that when the ansible deploy
fails,</p></li></ol>
<p>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).</p>
<ol><li><p>I recommend adding ‘-vvv’ to the ansible
command. Might get more</p></li></ol>
<p>verbose logs, but easier to debug next time. Thanks, Nadav. On Thu, Aug 24, 2017
at 9:49 AM, Martin Perina &lt;mperina(a)redhat.com&gt; wrote:</p>
<blockquote><p>Hi,</p>
<p>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:</p>
<ol><li><p>boot.log looks good, I see that WildFly 11 is
starting</p></li>
<li><p>server.log also looks good, I see engine was deployed, but it seems to
me</p></li></ol>
<p>that it's not complete (like WildFly was killed during engine
deployment)</p>
<ol><li><p>engine.log is completely empty – that's very
strange, but it's probably</p></li></ol>
<p>related to my suspicion above</p>
<p>In lago logs I can see that ovirt-engine service is being started, but no info
about being killed/stop.</p>
<p>Any idea what could have happened?</p>
<p>Thanks a lot</p>
<p>Martin</p>
<p>On Thu, Aug 24, 2017 at 4:50 AM, &lt;jenkins(a)jenkins.phx.ovirt.org&gt;
wrote:</p>
<blockquote><pre>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</pre>
<pre>-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #5
[Eyal Shenitzky] basic-suite-master: add cold_storage_migration test</pre>
<pre>[Barak Korren] Adapting OST manual job to macro changes</pre>
<pre>[Daniel Belenky] Add support for secrets and credentials to STD CI</pre>
<pre>Changes for Build #6
No changes</pre>
<pre>Changes for Build #7
[Your Name] Use a long name with special chars as a network name</pre>
<pre>[Barak Korren] Fix small bug in slave repo setup</pre>
<pre>[Daniel Belenky] mock_runner fix empty mrmap bug</pre>
<pre>-----------------
Failed Tests:
-----------------
All tests passed</pre></blockquote>
<p><em>____________________________________________</em>_ Infra mailing
list Infra(a)ovirt.org <a
href="http://lists.ovirt.org/mailman/listinfo/infra">http://...
<p>— This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)</p>
<img
src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpS...
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>
------------=_1504013319-10702-217--