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

Thursday, 24 August 2017

This is a multi-part message in MIME format...

------------=_1503558206-11919-153
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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
             Project: oVirt - virtualization made easy
          Issue Type: By-EMAIL
            Reporter: Nadav Goldin
            Assignee: infra

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&gt; 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&gt; 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)

------------=_1503558206-11919-153
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<h3>Nadav Goldin created OVIRT-1613:</h3>
<pre>   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
   Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
  Reporter: Nadav Goldin
  Assignee: infra</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:
&lsquo;TemplatesModule&rsquo; object has no attribute
&lsquo;wait_for_import&rsquo; 02:50:12 fatal: [lago-ansible-suite-master-engine]:
FAILED! =&gt; {&quot;changed&quot;: false, &ldquo;failed&rdquo;: true,
&ldquo;msg&rdquo;: &ldquo;'TemplatesModule' object has no attribute
'wait_for_import'&rdquo;} 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>
<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 &lsquo;initialize_engine&rsquo;, and not after the ansible
failure).</p>
<ol><li><p>I recommend adding &lsquo;-vvv&rsquo; to the ansible
command. Might get more</p></li></ol>
<p>verbose logs, but easier to debug next time.</p>
<p>Thanks,</p>
<p>Nadav.</p>
<p>On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina &amp;lt;mperina(a)redhat.com&amp;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 &ndash; 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, &amp;lt;jenkins(a)jenkins.phx.ovirt.org&amp;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>&mdash; This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)</p>

------------=_1503558206-11919-153--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

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