August 2017 - Infra - oVirt List Archives

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #717
by jenkins＠jenkins.phx.ovirt.org 24 Aug '17

24 Aug '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) Commit message: "Exclude big packages from mirrors" > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1449295596924030481.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 912, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1584) Create Branch and User fields in ansible_suite job
by eyal edri (oVirt JIRA) 24 Aug '17

24 Aug '17

This is a multi-part message in MIME format... ------------=_1503566337-11829-305 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1584?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1584: ---------------------------------- [~omachace(a)redhat.com] [~mwperina] can you verify you can run the ansible suite using the manual job? > Create Branch and User fields in ansible_suite job > -------------------------------------------------- > > Key: OVIRT-1584 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1584 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST, oVirt CI > Reporter: Ondra Machacek > Assignee: infra > > I would like to have following fields in ansible job[1]. > - branch (default: devel) > - username (default: ansible) > So in OST[2], we can define which branch+ from which git repo, should be fetched, > with this we can test PRs. > [1] http://jenkins.ovirt.org/job/system-tests_ansible-suite-master/ > [2] https://github.com/oVirt/ovirt-system-tests/blob/master/run_suite.sh#L212 > [~lbednar] -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1503566337-11829-305 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1584?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1584:</h3> [~omachace(a)redhat.com] [~mwperina] can you verify you can run the ansible suite using the manual job? <blockquote><h3>Create Branch and User fields in ansible_suite job</h3> <pre> Key: OVIRT-1584 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1584 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST, oVirt CI Reporter: Ondra Machacek Assignee: infra</pre> I would like to have following fields in ansible job[1]. <pre>- branch (default: devel) - username (default: ansible)</pre> So in OST[2], we can define which branch+ from which git repo, should be fetched, with this we can test PRs. [1] <a href="http://jenkins.ovirt.org/job/system-tests_ansible-suite-master/">http://jenkins.ovirt.org/job/system-tests_ansible-suite-master/</a> [2] <a href="https://github.com/oVirt/ovirt-system-tests/blob/master/run_suite.sh#L212">https://github.com/oVirt/ovirt-system-tests/blob/master/run_suite.sh#L212</a> [~lbednar]</blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1503566337-11829-305--

1 0

[JIRA] (OVIRT-1605) Add the "your user to mock group" as a prerequisite in STD-CI docs
by eyal edri (oVirt JIRA) 24 Aug '17

24 Aug '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1605?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1605: -------------------------------- Assignee: eyal edri (was: infra) > Add the "your user to mock group" as a prerequisite in STD-CI docs > ------------------------------------------------------------------ > > Key: OVIRT-1605 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1605 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: eyal edri > > Currently, STD-CI documentation points you to a link of mock help. Users might ignore this link as all they are trying to do is to make mock_runner.sh run on their machine. > The command: *usermod -a -G mock [User name]* should be added to the document. -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)

1 0

[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64
by eyal edri (oVirt JIRA) 24 Aug '17

24 Aug '17

This is a multi-part message in MIME format... ------------=_1503565565-16457-139 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D34= 778#comment-34778 ]=20 eyal edri commented on OVIRT-1607: ---------------------------------- [~amarchuk] is this still happening, [~ederevea] do we know if there was a = DNS outage? > Failed ovirt-system-tests_master_check-patch-el7-x86_64 > ------------------------------------------------------- > > Key: OVIRT-1607 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > I want to verify [1]. It (expectedly) failed in the past, needed [2]. > [2] was merged yesterday and [1] still fails. I retriggered it several > times, and it failed due to different reasons. Last was [3]: > 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f > '(' -iname 'nose*.xml' -o -iname '*.junit.xml' ')' -exec mv '{}' > exported-artifacts/ ';' > 08:11:38 find: =EF=BF=BD=EF=BF=BD=EF=BF=BD/dev/shm/ost/deployment-image-n= g-suite-master=EF=BF=BD=EF=BF=BD=EF=BF=BD: No > such file or directory > Please have a look. Thanks, > [1] https://gerrit.ovirt.org/80820 > [2] https://gerrit.ovirt.org/79345 > [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el= 7-x86_64/1467/ > --=20 > Didi -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1503565565-16457-139 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-1607?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D34778#comment-34778 ]</pre> <h3>eyal edri commented on OVIRT-1607:</h3> [~amarchuk] is this still happening, [~ederevea] do we know if there was= a DNS outage? <blockquote><h3>Failed ovirt-system-tests_master_check-patch-el7-x86_64</h3> <pre> Key: OVIRT-1607 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> I want to verify [1]. It (expectedly) failed in the past, needed [2]. [2= ] was merged yesterday and [1] still fails. I retriggered it several times,= and it failed due to different reasons. Last was [3]: 08:11:38 + find /dev= /shm/ost/deployment-image-ng-suite-master -type f ‘(’ -iname &l= squo;nose*.xml’ -o -iname ‘*.junit.xml’ ‘)’ -= exec mv ‘{}’ exported-artifacts/ ‘;’ 08:11:38 find:= =EF=BF=BD=EF=BF=BD=EF=BF=BD/dev/shm/ost/deployment-image-ng-suite-master= =EF=BF=BD=EF=BF=BD=EF=BF=BD: No such file or directory Please have a look. = Thanks, [1] <a href=3D"https://gerrit.ovirt.org/80820">https://gerrit.ovirt= .org/80820</a> [2] <a href=3D"https://gerrit.ovirt.org/79345">https://gerri= t.ovirt.org/79345</a> [3] <a href=3D"http://jenkins.ovirt.org/job/ovirt-sys= tem-tests_master_check-patch-el7-x86_64/1467/">http://jenkins.ovirt.org/job= /ovirt-system-tests_master_check-patch-el7-x86_64/1467/</a> — Didi</p= ></blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#1000= 59) <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BCmpYLyzYS3r1Q939T2sgz3O6CQdgfgsF9DpxZu9RiIeF64eywr4rLl717YUQt-2Fc1F1= e0xNrAARrRG4wOAxXuK-2FU3AXkwNloaSWn0-2BDLD4U7fwnN8ykaArsMWGvAnEnFRpTLcbURUr= A5PFhdENSTOHzX9i5yNcvBOjtude7ng-2F75efdzDANLu4CpYLwzDav8wWS5ztmq39-2FyJE3Yr= C3Kj5c-3D" alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"height:1= px !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-r= ight:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1503565565-16457-139--

1 0

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
by Martin Perina (oVirt JIRA) 24 Aug '17

24 Aug '17

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> On Thu, Aug 24, 2017 at 9:01 AM, Nadav Goldin <ngoldin(a)redhat.com>= wrote: <blockquote>Adding @infra-support to open a ticket. <ol><li>From the console logs the error seems to be:</li></ol> 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: 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 Maybe something changed recently in the Ansible roles?</blockquote> =E2=80=8BAhh, somehow it didn't come to my mind that in console might be= more than in artifacts :-( I will post a= fix for that. =E2=80=8B <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> =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 <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> =E2=80=8BThanks a lot! Martin =E2=80=8B <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, <jenkins(a)jenkins.phx.ovirt.org>= 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 <mperina(a)redhat.com> 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, <jenkins(a)jenkins.phx.ovirt.org>= 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> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#1000= 59) <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--

1 0

Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
by Martin Perina 24 Aug '17

24 Aug '17

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

3 3

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
by Nadav Goldin (oVirt JIRA) 24 Aug '17

24 Aug '17

This is a multi-part message in MIME format... ------------=_1503560308-24632-159 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jira.… ] Nadav Goldin commented on OVIRT-1613: ------------------------------------- Right, adding something like https://github.com/lago-project/lago/blob/master/tests/functional-sdk/test_… in the suite's control.sh: {code} export ANSIBLE_LOG_PATH=$PWD/exported-artifacts/ansible.log {code} > 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> 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) ------------=_1503560308-24632-159 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.jira.… ]</pre> <h3>Nadav Goldin commented on OVIRT-1613:</h3> Right, adding something like <a href="https://github.com/lago-project/lago/blob/master/tests/functional-sdk/test_…">https://github.com/lago-project/lago/blob/master/tests/functional-sdk/test_…</a> in the suite's control.sh: {code} export ANSIBLE_LOG_PATH=$PWD/exported-artifacts/ansible.log {code} <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: infra</pre> Adding @infra-support to open a ticket. <ol><li>From the console logs the error seems to be:</li></ol> 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? <ol><li>There is a bug in the suite, that when the ansible deploy fails,</li></ol> 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). <ol><li>I recommend adding ‘-vvv’ to the ansible command. Might get more</li></ol> 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: <blockquote>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: <ol><li>boot.log looks good, I see that WildFly 11 is starting</li> <li>server.log also looks good, I see engine was deployed, but it seems to me</li></ol> that it's not complete (like WildFly was killed during engine deployment) <ol><li>engine.log is completely empty – that's very strange, but it's probably</li></ol> 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: <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> _____________________________________________ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a></blockquote></blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1503560308-24632-159--

1 0

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
by Barak Korren (oVirt JIRA) 24 Aug '17

24 Aug '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1613: ------------------------------------- On 24 August 2017 at 10:01, Nadav Goldin <ngoldin(a)redhat.com> wrote: > > 3. I recommend adding '-vvv' to the ansible command. Might get more > verbose logs, but easier to debug next time. > > We might also want to save Ansible logs to somewhere other then STDOUT for easier grepping... -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > 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> 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)

1 0

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
by Nadav Goldin (oVirt JIRA) 24 Aug '17

24 Aug '17

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> 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) ------------=_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> Adding @infra-support to open a ticket. <ol><li>From the console logs the error seems to be:</li></ol> 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? <ol><li>There is a bug in the suite, that when the ansible deploy fails,</li></ol> 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). <ol><li>I recommend adding ‘-vvv’ to the ansible command. Might get more</li></ol> 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: <blockquote>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: <ol><li>boot.log looks good, I see that WildFly 11 is starting</li> <li>server.log also looks good, I see engine was deployed, but it seems to me</li></ol> that it's not complete (like WildFly was killed during engine deployment) <ol><li>engine.log is completely empty – that's very strange, but it's probably</li></ol> 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: <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> _____________________________________________ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a></blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1503558206-11919-153--

1 0

[JIRA] (OVIRT-1612) could someone post this patch for me?
by Barak Korren (oVirt JIRA) 24 Aug '17

24 Aug '17

This is a multi-part message in MIME format... ------------=_1503556930-21279-301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1612?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-1612: ----------------------------------- Assignee: rgolan(a)redhat.com (was: infra) > could someone post this patch for me? > ------------------------------------- > > Key: OVIRT-1612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: gshereme(a)redhat.com > Assignee: rgolan(a)redhat.com > Attachments: 0001-remove-gshereme-from-default-frontend-reviews.p= atch > > > Can you post/merge this for me? De-spamming a little. > greg@dauntless:/home/greg/projects/ovirt-engine(:5995af1c03|=E2=80=A6) % = git push > gerrit.ovirt.org:ovirt-engine HEAD:refs/meta/config > Counting objects: 3, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (3/3), done. > Writing objects: 100% (3/3), 377 bytes | 0 bytes/s, done. > Total 3 (delta 2), reused 0 (delta 0) > remote: Resolving deltas: 100% (2/2) > remote: Branch refs/meta/config: > remote: You are not allowed to perform this operation. > remote: Configuration changes can only be pushed by project owners > remote: who also have 'Push' rights on refs/meta/config > remote: User: gsheremeta > remote: Please read the documentation and contact an administrator > remote: if you feel the configuration is incorrect > remote: Processing changes: refs: 1, done > To gerrit.ovirt.org:ovirt-engine > ! [remote rejected] HEAD -> refs/meta/config (prohibited by Gerrit) > error: failed to push some refs to 'gerrit.ovirt.org:ovirt-engine' > --=20 > Greg Sheremeta, MBA > Sr. Software Engineer > Red Hat, Inc. > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1503556930-21279-301 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-1612?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre> <h3>Barak Korren reassigned OVIRT-1612:</h3> <pre>Assignee: rgolan(a)redhat.com (was: infra)</pre> <blockquote><h3>could someone post this patch for me?</h3> <pre> Key: OVIRT-1612 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1612 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: gshereme(a)redhat.com Assignee: rgolan(a)redhat.com Attachments: 0001-remove-gshereme-from-default-frontend-reviews.pat= ch</pre> Can you post/merge this for me? De-spamming a little. greg@dauntless:/ho= me/greg/projects/ovirt-engine(:5995af1c03|=E2=80=A6) % git push gerrit.ovir= t.org:ovirt-engine HEAD:refs/meta/config Counting objects: 3, done. Delta c= ompression using up to 4 threads. Compressing objects: 100% (3/3), done. Wr= iting objects: 100% (3/3), 377 bytes | 0 bytes/s, done. Total 3 (delta 2), = reused 0 (delta 0) remote: Resolving deltas: 100% (2/2) remote: Branch refs= /meta/config: remote: You are not allowed to perform this operation. remote= : Configuration changes can only be pushed by project owners remote: who al= so have ‘Push’ rights on refs/meta/config remote: User: gsherem= eta remote: Please read the documentation and contact an administrator remo= te: if you feel the configuration is incorrect remote: Processing changes: = refs: 1, done To gerrit.ovirt.org:ovirt-engine <pre>! [remote rejected] HEAD -> refs/meta/config (prohibited by G= errit)</pre> error: failed to push some refs to ‘gerrit.ovirt.org:ovirt-engine&= rsquo; — Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshe= reme(a)redhat.com</blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#1000= 59) <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BCmpYLyzYS3r1Q939T2sgz2nNjkCBOfORIozVAX38Aivkj7gG6hTlhTZAFSxmDuUt3nE7= mXuUMLG7yQlqCoyz-2B6u6LoKpixuPSMaVtw8DFOmxl1Ht6KixmndgT-2BIYqCXnEqPERwYhxRU= cBG7beF11YTDns6Oa-2BtyDY68p9VSuUGsX37dkqeJc3hBroRkGHSMy6Q0gsmRrIh8t9e-2FmI6= NkXA-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 !im= portant;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 = !important;padding-top:0 !important;padding-bottom:0 !important;padding-rig= ht:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1503556930-21279-301--

1 0