May 2016 - Infra - Ovirt List Archives

vdsm_master_check-patch-el7 job is failing

by Amit Aviram

Hi. For the last day I am getting this error over and over again from jenkins: Start: yum install*07:23:55* ERROR: Command failed. See logs for output.*07:23:55* # /usr/bin/yum-deprecated --installroot /var/lib/mock/epel-7-x86_64-cc6e9a99555654260f7f229c124a6940-31053/root/ --releasever 7 install @buildsys-build --setopt=tsflags=nocontexts*07:23:55* WARNING: unable to delete selinux filesystems (/tmp/mock-selinux-plugin.3tk4zgr4): [Errno 1] Operation not permitted: '/tmp/mock-selinux-plugin.3tk4zgr4'*07:23:55* Init took 3 seconds (see http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/2026/) This fails the job, so I get -1 from Jenkins CI for my patch. I am pretty sure it is not related to the patch. also fc23 job passes. Any idea what's the problem? Thanks

8 years, 6 months

3
3
0 / 0

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.6_el6_merged - Build # 33 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_371_444287649.1464084504194 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged... Build Number: 33 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57804 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #33 [Sandro Bonazzola] ovirt-engine: switch from 3.6.6 to 3.6.7 [Jakub Niedermertl] frontend: Import VM dialog - architecture ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_371_444287649.1464084504194--

8 years, 6 months

1
0
0 / 0

Jenkins build became unstable: ovirt_master_system-tests #58

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/58/changes>

8 years, 6 months

1
1
0 / 0

[JIRA] (OVIRT-515) Re: Cannot clone bugs with more than 2^16 characters in the comments

by Gil Shinar (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-515?page=com.atlassian.jira... ] Gil Shinar commented on OVIRT-515: ---------------------------------- Something is really strange here. It let's you write a comment with more then 2^16 chars but don't let you clone it? It looks more like a Bugzilla bug than a Bugzilla limitation > Re: Cannot clone bugs with more than 2^16 characters in the comments > -------------------------------------------------------------------- > > Key: OVIRT-515 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-515 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: dcaro > Assignee: infra > Attachments: signature.asc, signature.asc > > > Looks like a restriction of the api itself, probably triggered by us adding the > 'comment from ...' header to the comments while clonning. > Opening a bug on it to keep track > On 05/02 12:36, Tal Nisan wrote: > > I've encountered this in this job: > > http://jenkins-ci.eng.lab.tlv.redhat.com/job/system_bugzilla_clone_zstrea... > > > > For this bug: > > https://bugzilla.redhat.com/1301083 > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > -- > David Caro > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > Tel.: +420 532 294 605 > Email: dcaro(a)redhat.com > IRC: dcaro|dcaroest@{freenode|oftc|redhat} > Web: www.redhat.com > RHT Global #: 82-62605 -- This message was sent by Atlassian JIRA (v1000.5.2#72002)

8 years, 6 months

1
0
0 / 0

oVirt 3.6.7 RC1 build starting

by Sandro Bonazzola

Fyi oVirt products maintainers, An oVirt build for an official release is going to start in 20 minutes. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

8 years, 6 months

1
0
0 / 0

[oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.5_el6_merged - Build # 30 - Failure!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_365_1930631744.1464017992792 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/ Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged... Build Number: 30 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/57848 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #30 [David Caro] Using lazy umount everywhere [Liron Aravot] core: RunVm - do not pass compensation context ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_365_1930631744.1464017992792--

8 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-515) Re: Cannot clone bugs with more than 2^16 characters in the comments

by David Caro Estevez (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-515?page=com.atlassian.jira... ] David Caro Estevez updated OVIRT-515: ------------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Re: Cannot clone bugs with more than 2^16 characters in the comments > -------------------------------------------------------------------- > > Key: OVIRT-515 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-515 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: dcaro > Assignee: infra > Attachments: signature.asc, signature.asc > > > Looks like a restriction of the api itself, probably triggered by us adding the > 'comment from ...' header to the comments while clonning. > Opening a bug on it to keep track > On 05/02 12:36, Tal Nisan wrote: > > I've encountered this in this job: > > http://jenkins-ci.eng.lab.tlv.redhat.com/job/system_bugzilla_clone_zstrea... > > > > For this bug: > > https://bugzilla.redhat.com/1301083 > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > -- > David Caro > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > Tel.: +420 532 294 605 > Email: dcaro(a)redhat.com > IRC: dcaro|dcaroest@{freenode|oftc|redhat} > Web: www.redhat.com > RHT Global #: 82-62605 -- This message was sent by Atlassian JIRA (v1000.5.2#72002)

8 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-515) Re: Cannot clone bugs with more than 2^16 characters in the comments

by David Caro Estevez (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-515?page=com.atlassian.jira... ] David Caro Estevez commented on OVIRT-515: ------------------------------------------ >From Tal Nisan (on an email): I can't comment in Jira since I don't have a user there but I've investigated a bit and it seems to be a Bugzilla limitation, when I tried to clone manually it gave me the same error till I cut the comment. I guess the comment field there is limited to 2^16 which makes sense. In light of this this issue can be closed. > Re: Cannot clone bugs with more than 2^16 characters in the comments > -------------------------------------------------------------------- > > Key: OVIRT-515 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-515 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: dcaro > Assignee: infra > Attachments: signature.asc, signature.asc > > > Looks like a restriction of the api itself, probably triggered by us adding the > 'comment from ...' header to the comments while clonning. > Opening a bug on it to keep track > On 05/02 12:36, Tal Nisan wrote: > > I've encountered this in this job: > > http://jenkins-ci.eng.lab.tlv.redhat.com/job/system_bugzilla_clone_zstrea... > > > > For this bug: > > https://bugzilla.redhat.com/1301083 > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > -- > David Caro > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > Tel.: +420 532 294 605 > Email: dcaro(a)redhat.com > IRC: dcaro|dcaroest@{freenode|oftc|redhat} > Web: www.redhat.com > RHT Global #: 82-62605 -- This message was sent by Atlassian JIRA (v1000.5.2#72002)

8 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-515) Re: Cannot clone bugs with more than 2^16 characters in the comments

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-515?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-515: ------------------------------------------------- [~gshinar] did you saw something like this in the code? anywhere we can test / fix it or to verify if its a bugzilla api limitation? > Re: Cannot clone bugs with more than 2^16 characters in the comments > -------------------------------------------------------------------- > > Key: OVIRT-515 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-515 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: dcaro > Assignee: infra > Attachments: signature.asc, signature.asc > > > Looks like a restriction of the api itself, probably triggered by us adding the > 'comment from ...' header to the comments while clonning. > Opening a bug on it to keep track > On 05/02 12:36, Tal Nisan wrote: > > I've encountered this in this job: > > http://jenkins-ci.eng.lab.tlv.redhat.com/job/system_bugzilla_clone_zstrea... > > > > For this bug: > > https://bugzilla.redhat.com/1301083 > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > -- > David Caro > Red Hat S.L. > Continuous Integration Engineer - EMEA ENG Virtualization R&D > Tel.: +420 532 294 605 > Email: dcaro(a)redhat.com > IRC: dcaro|dcaroest@{freenode|oftc|redhat} > Web: www.redhat.com > RHT Global #: 82-62605 -- This message was sent by Atlassian JIRA (v1000.5.2#72002)

8 years, 6 months

1
0
0 / 0

Build failed in Jenkins: ovirt_master_system-tests #56

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/56/> ------------------------------------------ Failed to access build log java.io.IOException: remote file operation failed: /home/jenkins/workspace/ovirt_master_system-tests at hudson.remoting.Channel@18c52764:ovirt-srv25.phx.ovirt.org: hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:986) at hudson.FilePath.act(FilePath.java:968) at hudson.FilePath.toURI(FilePath.java:1113) at hudson.tasks.MailSender.createFailureMail(MailSender.java:282) at hudson.tasks.MailSender.getMail(MailSender.java:157) at hudson.tasks.MailSender.execute(MailSender.java:102) at hudson.tasks.Mailer.perform(Mailer.java:138) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:780) at hudson.FilePath.act(FilePath.java:979) ... 15 more Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:1163) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:118) at hudson.remoting.PingThread.ping(PingThread.java:126) at hudson.remoting.PingThread.run(PingThread.java:85) Caused by: java.util.concurrent.TimeoutException: Ping started at 1463969944240 hasn't completed by 1463970184247 ... 2 more

8 years, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2016