[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
2:57 a.m.
This is a multi-part message in MIME format...
------------=_1503561447-24633-181
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D34=
776#comment-34776 ]=20
Martin Perina commented on OVIRT-1613:
--------------------------------------
On Thu, Aug 24, 2017 at 9:01 AM, Nadav Goldin <ngoldin(a)redhat.com> 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. 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! =3D>
{"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?
=E2=80=8BAhh, somehow it didn't come to my mind that in console might be mo=
re than
in artifacts :-(
I will post a fix for that.
=E2=80=8B
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).
=E2=80=8BHmm, I will take a look to other suites what's the difference arou=
nd
collecting logs and post a fix for that
=E2=80=8B
3. I recommend adding '-vvv' to the ansible command. Might get more
verbose logs, but easier to debug next time.=E2=80=8B
Thanks,
Nadav.
=E2=80=8BThanks a lot!
Martin
=E2=80=8B
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 deploymen=
t)
> 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
>
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! =3D>
{"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-sy=
stem-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 faili=
ng 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 deploymen=
t)
> 3. engine.log is completely empty - that's very strange, but
it's proba=
bly
> 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)
------------=_1503561447-24633-181
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D34776#comment-34776 ]</pre>
<h3>Martin Perina commented on OVIRT-1613:</h3>
<p>On Thu, Aug 24, 2017 at 9:01 AM, Nadav Goldin
&lt;ngoldin(a)redhat.com&gt;=
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: AttributeEr=
ror: ‘TemplatesModule’ object has no attribute ‘wait_for_=
import’ 02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! =
=3D> {"changed": false, “failed”: true,
“msg=
”: “'TemplatesModule' object has no attribute
'wait_for_import'=
”} 02:50:12 to retry, use: --limit @/home/jenkins/workspace/ovirt-sys=
tem-tests_ansible- suite-master/ovirt-system-tests/ansible-suite-master/eng=
ine.retry</p>
<p>Maybe something changed recently in the Ansible
roles?</p></blockquote>
<p>=E2=80=8BAhh, somehow it didn't come to my mind that in console might be=
more than in artifacts <span class=3D"smiley-sad">:-(</span> I will
post a=
fix for that. =E2=80=8B</p>
<blockquote><pre>2. There is a bug in the suite, that when the ansible depl=
oy 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>=E2=80=8BHmm, I will take a look to other suites what's the difference a=
round collecting logs and post a fix for that =E2=80=8B</p>
<blockquote><pre>3. I recommend adding '-vvv' to the ansible command.
Might=
get more
verbose logs, but easier to debug next time.=E2=80=8B</pre>
<pre>Thanks,</pre>
<pre>Nadav.</pre></blockquote>
<p>=E2=80=8BThanks a lot!</p>
<p>Martin =E2=80=8B</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 engin=
e:
>
> 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 deployme=
nt)
> 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, &lt;jenkins(a)jenkins.phx.ovirt.org&gt;=
wrote:
>>
>> Project:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-mast=
er/
>> Build:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-mast=
er/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 te=
st
>>
>> [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
></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! =3D>
{"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-syst=
em-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 &lt;mperina(a)redhat.com&gt; w=
rote:
> Hi,
>
> Ansible test suite is failing for a few days, Lago says that it's fail=
ing 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 engin=
e:
>
> 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 deployme=
nt)
> 3. engine.log is completely empty - that's very strange, but it's prob=
ably
> 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, &lt;jenkins(a)jenkins.phx.ovirt.org&gt;=
wrote:
>>
>> Project:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-mast=
er/
>> Build:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-mast=
er/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 te=
st
>>
>> [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
></pre></blockquote>
<p>— This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#1000=
59)</p>
<img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ=
pSp2-2BCmpYLyzYS3r1Q939T2sgz00sI6zvNxnwm27FgDR2ZAx4QicEDXu44U1O-2BKkh3gIJe4=
6ueY-2B1u2Ygloo51Rs5tOkq-2B0XvAfAz8llUVUImRKNYp3FlXolOIL1vYUzUTm5OSINysEHQR=
-2Be3YY3bG6q6wwO5r5eV-2F8yEiF67yHSiEx53PW9yi8wUNoa99QNdFIwzINKigls9fjLOT-2B=
OUnqqoT0-3D" alt=3D"" width=3D"1" height=3D"1"
border=3D"0" style=3D"height=
:1px !important;width:1px !important;border-width:0 !important;margin-top:0=
!important;margin-bottom:0 !important;margin-right:0 !important;margin-lef=
t:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding=
-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1503561447-24633-181--
2651
days inactive
2651
days old
0 comments
1 participants
participants (1)
-
Martin Perina (oVirt JIRA)