- Infra - oVirt List Archives

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org
by danken (oVirt JIRA) 08 Nov '17

08 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.… ] danken commented on OVIRT-1748: ------------------------------- [~bkorren(a)redhat.com] excuse me if I forgot a former chat about this. ovirt users would not see Fedora + ovirt-guest-agent as somehow "tainted". If they are pulling an image from ovirt glance, they expect to get ovirt-tweaked images. I understand it can be a big burden to generate the image (it should happen 2-3 times a year, when the base operating system is respinned). I don't know which tools should be used to do this (`virt-customize --install ovirt-guest-agent` maybe? should I play with in-guest soflinks to enable it?) So it is fair to block my request due to capacity. I could be biased, but for me the benefit of shipping ovirt-guest-agent with ovirt guest images is self-evident. > include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org > ---------------------------------------------------------------------------------- > > Key: OVIRT-1748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. > By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org
by Tomáš Golembiovský (oVirt JIRA) 08 Nov '17

08 Nov '17

This is a multi-part message in MIME format... ------------=_1510154872-24426-108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D35= 310#comment-35310 ]=20 Tom=C3=A1=C5=A1 Golembiovsk=C3=BD commented on OVIRT-1748: ------------------------------------------- bq. Maybe you can convince the upstreams to include the agent in their imag= es. But frankly, I think the agent's existence is a bug and not a feature, = given that qemu-guest-agent exists and is pre-installed in most images. At this moment qemu-guest-agent is barely usable. We are slowly working on = improving it and integrating it with oVirt. But it's slow process and it wi= ll take some time before we can replace ovirt-guest-agent. I have no objections to including it. My only concern would be if and how w= ill we handle updates of old images when ovirt-guest-agent is updated. I as= sume we will not, we use what's available at installation time and that's i= t. > include ovirt-guest-agent in Fedora and CentOS images provided on glance.= ovirt.org > -------------------------------------------------------------------------= --------- > > Key: OVIRT-1748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > ovirt-guest-agent is an important part of the ovirt experience. So is gla= nce.ovirt.org. > By shipping images pre-installed with our guest agent, we would provide a= better product for our users. Also, doing so would make it simpler to add = tests the verify the state of the guest (e.g how many interfaces does it ha= ve, and what are its IP addresses). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510154872-24426-108 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-1748?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D35310#comment-35310 ]</pre> <h3>Tom=C3=A1=C5=A1 Golembiovsk=C3=BD commented on OVIRT-1748:</h3> bq. Maybe you can convince the upstreams to include the agent in their i= mages. But frankly, I think the agent's existence is a bug and not a featur= e, given that qemu-guest-agent exists and is pre-installed in most images.<= /p> At this moment qemu-guest-agent is barely usable. We are slowly working = on improving it and integrating it with oVirt. But it's slow process and it= will take some time before we can replace ovirt-guest-agent. I have no objections to including it. My only concern would be if and ho= w will we handle updates of old images when ovirt-guest-agent is updated. I= assume we will not, we use what's available at installation time and that'= s it. <blockquote><h3>include ovirt-guest-agent in Fedora and CentOS images provi= ded on glance.ovirt.org</h3> <pre> Key: OVIRT-1748 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra</pre> ovirt-guest-agent is an important part of the ovirt experience. So is gl= ance.ovirt.org. By shipping images pre-installed with our guest agent, we w= ould provide a better product for our users. Also, doing so would make it s= impler to add tests the verify the state of the guest (e.g how many interfa= ces does it have, and what are its IP addresses).</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#1000= 70) <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BCmpYLyzYS3r1Q939T2sgz1mLooV-2B69-2Bu8pbEvqQj94Y2GIR7aMkToSmIXRCtv5Go= YOfqcWiuhvcl4Mmqc9IwUi-2BH6lwzSNn0uXD5lUCSLQqSykqzUF8-2FNn1RpGMbVlyfC8rAiXg= bWrj9XgJsmeSoJQ3sqhs6tHdeQ3BMSh3iny3jCwYuX-2Fh3Y8XpGsi5v7uzCopoj-2F9ZPlZylG= X2GbP5Gc-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> ------------=_1510154872-24426-108--

1 0

[oVirt Jenkins] standard-enqueue - Build #6569 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Nov '17

08 Nov '17

------=_Part_122_1966477339.1510154282181 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6569/ Build Name: #6569 Build Description: Gerrit: 83782 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83782 - title: Revert ovirt-engine-3.6.13 version bumps - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Tal Nisan <tnisan(a)redhat.com> ------=_Part_122_1966477339.1510154282181--

1 0

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org
by Barak Korren (oVirt JIRA) 08 Nov '17

08 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1748: ------------------------------------- Although I am pleased someone finally sees glance.ovit.org as an important part of the UX... > include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org > ---------------------------------------------------------------------------------- > > Key: OVIRT-1748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. > By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org
by Barak Korren (oVirt JIRA) 08 Nov '17

08 Nov '17

This is a multi-part message in MIME format... ------------=_1510151223-23007-114 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1748: ------------------------------------- [~danken(a)redhat.com] we talked about this before. We provide only clean, unchanged upstream images in Glance, and we intend to continue to do so. This is very important for user trust IMO. Maybe you can convince the upstreams to include the agent in their images. But frankly, I think the agent's existence is a bug and not a feature, given that qemu-guest-agent exists and is pre-installed in most images. > include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org > ---------------------------------------------------------------------------------- > > Key: OVIRT-1748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. > By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510151223-23007-114 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1748:</h3> [~danken(a)redhat.com] we talked about this before. We provide only clean, unchanged upstream images in Glance, and we intend to continue to do so. This is very important for user trust IMO. Maybe you can convince the upstreams to include the agent in their images. But frankly, I think the agent's existence is a bug and not a feature, given that qemu-guest-agent exists and is pre-installed in most images. <blockquote><h3>include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org</h3> <pre> Key: OVIRT-1748 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra</pre> ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses).</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510151223-23007-114--

1 0

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org
by danken (oVirt JIRA) 08 Nov '17

08 Nov '17

This is a multi-part message in MIME format... ------------=_1510151069-16956-112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.… ] danken commented on OVIRT-1748: ------------------------------- I hope [~tgolembi(a)redhat.com] and [~mskrivanek] agree, as doing so would increase the usage of the guest agent (and guest-agent-affected flows) by the community. > include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org > ---------------------------------------------------------------------------------- > > Key: OVIRT-1748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. > By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510151069-16956-112 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1748?page=com.atlassian.jira.… ]</pre> <h3>danken commented on OVIRT-1748:</h3> I hope [~tgolembi(a)redhat.com] and [~mskrivanek] agree, as doing so would increase the usage of the guest agent (and guest-agent-affected flows) by the community. <blockquote><h3>include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org</h3> <pre> Key: OVIRT-1748 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra</pre> ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses).</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510151069-16956-112--

1 0

[JIRA] (OVIRT-1748) include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org
by danken (oVirt JIRA) 08 Nov '17

08 Nov '17

danken created OVIRT-1748: ----------------------------- Summary: include ovirt-guest-agent in Fedora and CentOS images provided on glance.ovirt.org Key: OVIRT-1748 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1748 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra ovirt-guest-agent is an important part of the ovirt experience. So is glance.ovirt.org. By shipping images pre-installed with our guest agent, we would provide a better product for our users. Also, doing so would make it simpler to add tests the verify the state of the guest (e.g how many interfaces does it have, and what are its IP addresses). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[oVirt Jenkins] standard-enqueue - Build #6555 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Nov '17

08 Nov '17

------=_Part_118_425787237.1510148255461 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6555/ Build Name: #6555 Build Description: Gerrit: 83754 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83754 - title: build: post ovirt-engine-3.6.13 - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Lev Veyde <lveyde(a)redhat.com> ------=_Part_118_425787237.1510148255461--

1 0

[ OST Failure Report ] [ oVirt master ] [ 07-11-2017 ] [ 004_basic_sanity.disk_operations ]
by Dafna Ron 08 Nov '17

08 Nov '17

This is a multi-part message in MIME format. --------------106EB129C1BC1AEAACE8C19F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, We have a failure in test 004_basic_sanity.disk_operations. >From the log I can see that vdsm has a KeyError: 'diskReplicate' and than reports the drive not found. Can you please check the issue? ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/83641/* * Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653 Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact/ engine log: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact… vdsm log: ** http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact… (Relevant) error snippet from the log: <error> >From engine log: * 2017-11-07 09:20:42,396-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Failed in 'VmReplicateDiskFinishVDS' method 2017-11-07 09:20:42,399-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM lago-basic-suite-mas ter-host-0 command VmReplicateDiskFinishVDS failed: Drive image file could not be found 2017-11-07 09:20:42,399-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDisk FinishVDSCommand' return value 'StatusOnlyReturn [status=Status [code=13, message=Drive image file could not be found]]' 2017-11-07 09:20:42,399-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] HostName = lago-basic-suite-master-host-0 2017-11-07 09:20:42,399-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Command 'VmReplicateDiskFinishVDSCommand(HostName = lago-basic-sui te-master-host-0, VmReplicateDiskParameters:{hostId='038b0c9a-f64c-4aa7-8e36-72e435771dab', vmId='61d328bc-c920-4691-997f-09bbecb5de10', storagePoolId='b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', srcStorageDomainId='4a088fb2-5497-4b4d-adec-4c9 1d998c56e', targetStorageDomainId='4a088fb2-5497-4b4d-adec-4c91d998c56e', imageGroupId='36837a9b-6396-4d65-a354-df97ce808f01', imageId='8a1660d7-f153-4aca-9f25-c1184c10841a'})' execution failed: VDSGenericException: VDSErrorException: Fai led to VmReplicateDiskFinishVDS, error = Drive image file could not be found, code = 13 2017-11-07 09:20:42,399-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorExcep tion: VDSGenericException: VDSErrorException: Failed to VmReplicateDiskFinishVDS, error = Drive image file could not be found, code = 13 at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createDefaultConcreteException(VdsBrokerCommand.java:81) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.createException(BrokerCommandBase.java:223) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:193) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand.executeVdsBrokerCommand(VmReplicateDiskFinishVDSCommand.java:15) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:112) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:387) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor244.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.replicateDiskFinish(LiveMigrateDiskCommand.java:374) [bll.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.handleDestDisk(LiveMigrateDiskCommand.java:681) [bll.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.endWithFailure(LiveMigrateDiskCommand.java:337) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.internalEndWithFailure(CommandBase.java:783) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.endActionInTransactionScope(CommandBase.java:712) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1989) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.endAction(CommandBase.java:574) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.endAction(ChildCommandsCallbackBase.java:125) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.onFailed(ChildCommandsCallbackBase.java:156) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.endCallback(CommandCallbacksPoller.java:65) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:141) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:106) [bll.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_151] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_151] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151] : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:78) 2017-11-07 09:20:42,400-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] FINISH, VmReplicateDiskFinishVDSCommand, log id: 32c5a56e 2017-11-07 09:20:42,400-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] method: runVdsCommand, params: [VmReplicateDiskFinish, VmReplicateDiskParameters:{hostId='038b0c9a-f64c-4aa7-8e36-72e435771dab', vmId='61d328bc-c920-4691-997f-09bbecb5de10', storagePoolId='b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', srcStorageDomainId='4a088fb2-5497-4b4d-adec-4c91d998c56e', targetStorageDomainId='4a088fb2-5497-4b4d-adec-4c91d998c56e', imageGroupId='36837a9b-6396-4d65-a354-df97ce808f01', imageId='8a1660d7-f153-4aca-9f25-c1184c10841a'}], timeElapsed: 12ms 2017-11-07 09:20:42,400-05 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Replication end of disk '36837a9b-6396-4d65-a354-df97ce808f01' in vm '61d328bc-c920-4691-997f-09bbecb5de10' back to the source failed, skipping deletion of the target disk 2017-11-07 09:20:42,408-05 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Trying to release exclusive lock which does not exist, lock key: '61d328bc-c920-4691-997f-09bbecb5de10LIVE_STORAGE_MIGRATION' 2017-11-07 09:20:42,408-05 INFO [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Lock freed to object 'EngineLock:{exclusiveLocks='[61d328bc-c920-4691-997f-09bbecb5de10=LIVE_STORAGE_MIGRATION]', sharedLocks=''}' 2017-11-07 09:20:42,428-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] method: get, params: [038b0c9a-f64c-4aa7-8e36-72e435771dab], timeElapsed: 2ms 2017-11-07 09:20:42,430-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] EVENT_ID: USER_MOVED_DISK_FINISHED_FAILURE(2,011), User admin@internal-authz have failed to move disk vm0_disk0 to domain iscsi.** ** * * * * vdsm log: 2017-11-07 09:20:41,178-0500 INFO (jsonrpc/6) [vdsm.api] FINISH getVolumeSize return={'truesize': '2415919104', 'apparentsize': '2415919104'} from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e, task_id=042481eb-74ac-42a8-9d1e-8fb1c84db234 (api:52) 2017-11-07 09:20:41,193-0500 ERROR (jsonrpc/6) [api] FINISH diskReplicateFinish error='diskReplicate' (api:127) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 117, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 558, in diskReplicateFinish return self.vm.diskReplicateFinish(srcDisk, dstDisk) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 4477, in diskReplicateFinish self._delDiskReplica(drive) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 4528, in _delDiskReplica del dev['diskReplicate'] KeyError: 'diskReplicate' 2017-11-07 09:20:41,195-0500 INFO (jsonrpc/6) [api.virt] FINISH diskReplicateFinish return={'status': {'message': 'General Exception: ("\'diskReplicate\'",)', 'code': 100}} from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e (api:52) 2017-11-07 09:20:41,195-0500 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call VM.diskReplicateFinish failed (error 100) in 0.79 seconds (__init__:630) 2017-11-07 09:20:41,253-0500 INFO (jsonrpc/2) [vdsm.api] START finalizeMerge(spUUID=u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', subchainInfo={u'img_id': u'8401cd0f-419c-417c-8da3-52da285fa47c', u'sd_id': u'4a088fb2-5497-4b4d-adec-4c91d998c5 6e', u'top_id': u'7a295270-fdf5-4561-b688-033c5d312d1a', u'base_id': u'e77f8714-9e0f-4f39-8437-e75a3fa44c74'}) from=::ffff:192.168.204.4,49380, flow_id=56c9f051-c091-49cd-9fd5-cc98e92ef05f, task_id=9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (ap i:46) 2017-11-07 09:20:41,267-0500 INFO (jsonrpc/2) [vdsm.api] FINISH finalizeMerge return=None from=::ffff:192.168.204.4,49380, flow_id=56c9f051-c091-49cd-9fd5-cc98e92ef05f, task_id=9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (api:52) 2017-11-07 09:20:41,285-0500 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call StoragePool.finalizeMerge succeeded in 0.03 seconds (__init__:630) 2017-11-07 09:20:41,285-0500 INFO (tasks/8) [storage.ThreadPool.WorkerThread] START task 9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (cmd=<bound method Task.commit of <vdsm.storage.task.Task instance at 0x2f0a560>>, args=None) (threadPool:208) 2017-11-07 09:20:41,295-0500 INFO (tasks/8) [storage.merge] Finalizing subchain after merge: <SubchainInfo sd_id=4a088fb2-5497-4b4d-adec-4c91d998c56e, img_id=8401cd0f-419c-417c-8da3-52da285fa47c, top_id=7a295270-fdf5-4561-b688-033c5d312d 1a, base_id=e77f8714-9e0f-4f39-8437-e75a3fa44c74 base_generation=None at 0x30a7990> (merge:254) 2017-11-07 09:20:41,332-0500 INFO (tasks/8) [storage.SANLock] Acquiring Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/images/8401cd0 f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) for host id 1 (clusterlock:377) 2017-11-07 09:20:41,345-0500 INFO (tasks/8) [storage.SANLock] Successfully acquired Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/im ages/8401cd0f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) for host id 1 (clusterlock:415) 2017-11-07 09:20:41,372-0500 INFO (tasks/8) [storage.VolumeManifest] Volume: preparing volume 4a088fb2-5497-4b4d-adec-4c91d998c56e/e77f8714-9e0f-4f39-8437-e75a3fa44c74 (volume:558) 2017-11-07 09:20:41,377-0500 INFO (tasks/8) [storage.VolumeManifest] Volume: preparing volume 4a088fb2-5497-4b4d-adec-4c91d998c56e/7a295270-fdf5-4561-b688-033c5d312d1a (volume:558) 2017-11-07 09:20:41,395-0500 INFO (tasks/8) [storage.VolumeManifest] Volume: preparing volume 4a088fb2-5497-4b4d-adec-4c91d998c56e/a6cb7a60-e500-4a75-9da8-9e7cce3e21ac (volume:558) 2017-11-07 09:20:41,399-0500 INFO (tasks/8) [storage.VolumeManifest] sdUUID=4a088fb2-5497-4b4d-adec-4c91d998c56e imgUUID=8401cd0f-419c-417c-8da3-52da285fa47c volUUID = 7a295270-fdf5-4561-b688-033c5d312d1a legality = ILLEGAL (volume:399) 2017-11-07 09:20:41,667-0500 INFO (tasks/8) [storage.merge] Updating Vdsm metadata, syncing new chain: ['e77f8714-9e0f-4f39-8437-e75a3fa44c74', u'a6cb7a60-e500-4a75-9da8-9e7cce3e21ac'] (merge:311) 2017-11-07 09:20:41,690-0500 INFO (tasks/8) [storage.Image] Current chain=e77f8714-9e0f-4f39-8437-e75a3fa44c74 < 7a295270-fdf5-4561-b688-033c5d312d1a < a6cb7a60-e500-4a75-9da8-9e7cce3e21ac (top) (image:1162) 2017-11-07 09:20:41,690-0500 INFO (tasks/8) [storage.Image] Unlinking subchain: ['7a295270-fdf5-4561-b688-033c5d312d1a'] (image:1172) 2017-11-07 09:20:41,709-0500 INFO (tasks/8) [storage.Image] Setting parent of volume a6cb7a60-e500-4a75-9da8-9e7cce3e21ac to e77f8714-9e0f-4f39-8437-e75a3fa44c74 (image:1185) 2017-11-07 09:20:41,824-0500 INFO (tasks/8) [storage.SANLock] Releasing Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/images/8401cd0 f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) (clusterlock:435) 2017-11-07 09:20:41,828-0500 INFO (tasks/8) [storage.SANLock] Successfully released Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/im ages/8401cd0f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) (clusterlock:444) 2017-11-07 09:20:41,842-0500 INFO (tasks/8) [storage.ThreadPool.WorkerThread] FINISH task 9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (threadPool:210) 2017-11-07 09:20:42,388-0500 INFO (jsonrpc/4) [api.virt] START diskReplicateFinish(srcDisk={u'device': u'disk', u'poolID': u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', u'volumeID': u'8a1660d7-f153-4aca-9f25-c1184c10841a', u'domainID': u'4a08 8fb2-5497-4b4d-adec-4c91d998c56e', u'imageID': u'36837a9b-6396-4d65-a354-df97ce808f01'}, dstDisk={u'device': u'disk', u'poolID': u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', u'volumeID': u'8a1660d7-f153-4aca-9f25-c1184c10841a', u'domainID': u '4a088fb2-5497-4b4d-adec-4c91d998c56e', u'imageID': u'36837a9b-6396-4d65-a354-df97ce808f01'}) from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e (api:46) 2017-11-07 09:20:42,388-0500 ERROR (jsonrpc/4) [virt.vm] (vmId='61d328bc-c920-4691-997f-09bbecb5de10') Drive not found (srcDisk: {u'device': u'disk', u'poolID': u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', u'volumeID': u'8a1660d7-f153-4aca-9f 25-c1184c10841a', u'domainID': u'4a088fb2-5497-4b4d-adec-4c91d998c56e', u'imageID': u'36837a9b-6396-4d65-a354-df97ce808f01'}) (vm:4386) 2017-11-07 09:20:42,389-0500 INFO (jsonrpc/4) [api.virt] FINISH diskReplicateFinish return={'status': {'message': 'Drive image file could not be found', 'code': 13}} from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e (api:52) 2017-11-07 09:20:42,389-0500 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call VM.diskReplicateFinish failed (error 13) in 0.01 seconds (__init__:630)** : * * *</error>* ** --------------106EB129C1BC1AEAACE8C19F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, We have a failure in test 004_basic_sanity.disk_operations. From the log I can see that vdsm has a KeyError: 'diskReplicate' and than reports the drive not found. Can you please check the issue? <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to suspected patches: <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/83641/">https://gerrit.ovirt.org/#/c/83641/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to Job: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to all logs: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">engine log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact…">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact…</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">vdsm log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact…">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/artifact…</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">(Relevant) error snippet from the log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><error> From engine log: 2017-11-07 09:20:42,396-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Failed in 'VmReplicateDiskFinishVDS' method 2017-11-07 09:20:42,399-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM lago-basic-suite-mas ter-host-0 command VmReplicateDiskFinishVDS failed: Drive image file could not be found 2017-11-07 09:20:42,399-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDisk FinishVDSCommand' return value 'StatusOnlyReturn [status=Status [code=13, message=Drive image file could not be found]]' 2017-11-07 09:20:42,399-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] HostName = lago-basic-suite-master-host-0 2017-11-07 09:20:42,399-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Command 'VmReplicateDiskFinishVDSCommand(HostName = lago-basic-sui te-master-host-0, VmReplicateDiskParameters:{hostId='038b0c9a-f64c-4aa7-8e36-72e435771dab', vmId='61d328bc-c920-4691-997f-09bbecb5de10', storagePoolId='b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', srcStorageDomainId='4a088fb2-5497-4b4d-adec-4c9 1d998c56e', targetStorageDomainId='4a088fb2-5497-4b4d-adec-4c91d998c56e', imageGroupId='36837a9b-6396-4d65-a354-df97ce808f01', imageId='8a1660d7-f153-4aca-9f25-c1184c10841a'})' execution failed: VDSGenericException: VDSErrorException: Fai led to VmReplicateDiskFinishVDS, error = Drive image file could not be found, code = 13 2017-11-07 09:20:42,399-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorExcep tion: VDSGenericException: VDSErrorException: Failed to VmReplicateDiskFinishVDS, error = Drive image file could not be found, code = 13 at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createDefaultConcreteException(VdsBrokerCommand.java:81) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.createException(BrokerCommandBase.java:223) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:193) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand.executeVdsBrokerCommand(VmReplicateDiskFinishVDSCommand.java:15) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:112) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:387) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor244.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.replicateDiskFinish(LiveMigrateDiskCommand.java:374) [bll.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.handleDestDisk(LiveMigrateDiskCommand.java:681) [bll.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.endWithFailure(LiveMigrateDiskCommand.java:337) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.internalEndWithFailure(CommandBase.java:783) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.endActionInTransactionScope(CommandBase.java:712) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1989) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.endAction(CommandBase.java:574) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.endAction(ChildCommandsCallbackBase.java:125) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.onFailed(ChildCommandsCallbackBase.java:156) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.endCallback(CommandCallbacksPoller.java:65) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:141) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:106) [bll.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_151] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_151] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151] : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:78) 2017-11-07 09:20:42,400-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskFinishVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] FINISH, VmReplicateDiskFinishVDSCommand, log id: 32c5a56e 2017-11-07 09:20:42,400-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] method: runVdsCommand, params: [VmReplicateDiskFinish, VmReplicateDiskParameters:{hostId='038b0c9a-f64c-4aa7-8e36-72e435771dab', vmId='61d328bc-c920-4691-997f-09bbecb5de10', storagePoolId='b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', srcStorageDomainId='4a088fb2-5497-4b4d-adec-4c91d998c56e', targetStorageDomainId='4a088fb2-5497-4b4d-adec-4c91d998c56e', imageGroupId='36837a9b-6396-4d65-a354-df97ce808f01', imageId='8a1660d7-f153-4aca-9f25-c1184c10841a'}], timeElapsed: 12ms 2017-11-07 09:20:42,400-05 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Replication end of disk '36837a9b-6396-4d65-a354-df97ce808f01' in vm '61d328bc-c920-4691-997f-09bbecb5de10' back to the source failed, skipping deletion of the target disk 2017-11-07 09:20:42,408-05 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Trying to release exclusive lock which does not exist, lock key: '61d328bc-c920-4691-997f-09bbecb5de10LIVE_STORAGE_MIGRATION' 2017-11-07 09:20:42,408-05 INFO [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] Lock freed to object 'EngineLock:{exclusiveLocks='[61d328bc-c920-4691-997f-09bbecb5de10=LIVE_STORAGE_MIGRATION]', sharedLocks=''}' 2017-11-07 09:20:42,428-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] method: get, params: [038b0c9a-f64c-4aa7-8e36-72e435771dab], timeElapsed: 2ms 2017-11-07 09:20:42,430-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-72) [4bcdd94e] EVENT_ID: USER_MOVED_DISK_FINISHED_FAILURE(2,011), User admin@internal-authz have failed to move disk vm0_disk0 to domain iscsi. vdsm log: 2017-11-07 09:20:41,178-0500 INFO (jsonrpc/6) [vdsm.api] FINISH getVolumeSize return={'truesize': '2415919104', 'apparentsize': '2415919104'} from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e, task_id=042481eb-74ac-42a8-9d1e-8fb1c84db234 (api:52) 2017-11-07 09:20:41,193-0500 ERROR (jsonrpc/6) [api] FINISH diskReplicateFinish error='diskReplicate' (api:127) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 117, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 558, in diskReplicateFinish return self.vm.diskReplicateFinish(srcDisk, dstDisk) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 4477, in diskReplicateFinish self._delDiskReplica(drive) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 4528, in _delDiskReplica del dev['diskReplicate'] KeyError: 'diskReplicate' 2017-11-07 09:20:41,195-0500 INFO (jsonrpc/6) [api.virt] FINISH diskReplicateFinish return={'status': {'message': 'General Exception: ("\'diskReplicate\'",)', 'code': 100}} from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e (api:52) 2017-11-07 09:20:41,195-0500 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call VM.diskReplicateFinish failed (error 100) in 0.79 seconds (__init__:630) 2017-11-07 09:20:41,253-0500 INFO (jsonrpc/2) [vdsm.api] START finalizeMerge(spUUID=u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', subchainInfo={u'img_id': u'8401cd0f-419c-417c-8da3-52da285fa47c', u'sd_id': u'4a088fb2-5497-4b4d-adec-4c91d998c5 6e', u'top_id': u'7a295270-fdf5-4561-b688-033c5d312d1a', u'base_id': u'e77f8714-9e0f-4f39-8437-e75a3fa44c74'}) from=::ffff:192.168.204.4,49380, flow_id=56c9f051-c091-49cd-9fd5-cc98e92ef05f, task_id=9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (ap i:46) 2017-11-07 09:20:41,267-0500 INFO (jsonrpc/2) [vdsm.api] FINISH finalizeMerge return=None from=::ffff:192.168.204.4,49380, flow_id=56c9f051-c091-49cd-9fd5-cc98e92ef05f, task_id=9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (api:52) 2017-11-07 09:20:41,285-0500 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call StoragePool.finalizeMerge succeeded in 0.03 seconds (__init__:630) 2017-11-07 09:20:41,285-0500 INFO (tasks/8) [storage.ThreadPool.WorkerThread] START task 9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (cmd=<bound method Task.commit of <vdsm.storage.task.Task instance at 0x2f0a560>>, args=None) (threadPool:208) 2017-11-07 09:20:41,295-0500 INFO (tasks/8) [storage.merge] Finalizing subchain after merge: <SubchainInfo sd_id=4a088fb2-5497-4b4d-adec-4c91d998c56e, img_id=8401cd0f-419c-417c-8da3-52da285fa47c, top_id=7a295270-fdf5-4561-b688-033c5d312d 1a, base_id=e77f8714-9e0f-4f39-8437-e75a3fa44c74 base_generation=None at 0x30a7990> (merge:254) 2017-11-07 09:20:41,332-0500 INFO (tasks/8) [storage.SANLock] Acquiring Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/images/8401cd0 f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) for host id 1 (clusterlock:377) 2017-11-07 09:20:41,345-0500 INFO (tasks/8) [storage.SANLock] Successfully acquired Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/im ages/8401cd0f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) for host id 1 (clusterlock:415) 2017-11-07 09:20:41,372-0500 INFO (tasks/8) [storage.VolumeManifest] Volume: preparing volume 4a088fb2-5497-4b4d-adec-4c91d998c56e/e77f8714-9e0f-4f39-8437-e75a3fa44c74 (volume:558) 2017-11-07 09:20:41,377-0500 INFO (tasks/8) [storage.VolumeManifest] Volume: preparing volume 4a088fb2-5497-4b4d-adec-4c91d998c56e/7a295270-fdf5-4561-b688-033c5d312d1a (volume:558) 2017-11-07 09:20:41,395-0500 INFO (tasks/8) [storage.VolumeManifest] Volume: preparing volume 4a088fb2-5497-4b4d-adec-4c91d998c56e/a6cb7a60-e500-4a75-9da8-9e7cce3e21ac (volume:558) 2017-11-07 09:20:41,399-0500 INFO (tasks/8) [storage.VolumeManifest] sdUUID=4a088fb2-5497-4b4d-adec-4c91d998c56e imgUUID=8401cd0f-419c-417c-8da3-52da285fa47c volUUID = 7a295270-fdf5-4561-b688-033c5d312d1a legality = ILLEGAL (volume:399) 2017-11-07 09:20:41,667-0500 INFO (tasks/8) [storage.merge] Updating Vdsm metadata, syncing new chain: ['e77f8714-9e0f-4f39-8437-e75a3fa44c74', u'a6cb7a60-e500-4a75-9da8-9e7cce3e21ac'] (merge:311) 2017-11-07 09:20:41,690-0500 INFO (tasks/8) [storage.Image] Current chain=e77f8714-9e0f-4f39-8437-e75a3fa44c74 < 7a295270-fdf5-4561-b688-033c5d312d1a < a6cb7a60-e500-4a75-9da8-9e7cce3e21ac (top) (image:1162) 2017-11-07 09:20:41,690-0500 INFO (tasks/8) [storage.Image] Unlinking subchain: ['7a295270-fdf5-4561-b688-033c5d312d1a'] (image:1172) 2017-11-07 09:20:41,709-0500 INFO (tasks/8) [storage.Image] Setting parent of volume a6cb7a60-e500-4a75-9da8-9e7cce3e21ac to e77f8714-9e0f-4f39-8437-e75a3fa44c74 (image:1185) 2017-11-07 09:20:41,824-0500 INFO (tasks/8) [storage.SANLock] Releasing Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/images/8401cd0 f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) (clusterlock:435) 2017-11-07 09:20:41,828-0500 INFO (tasks/8) [storage.SANLock] Successfully released Lease(name='e77f8714-9e0f-4f39-8437-e75a3fa44c74', path=u'/rhev/data-center/mnt/192.168.204.4:_exports_nfs_share1/4a088fb2-5497-4b4d-adec-4c91d998c56e/im ages/8401cd0f-419c-417c-8da3-52da285fa47c/e77f8714-9e0f-4f39-8437-e75a3fa44c74.lease', offset=0) (clusterlock:444) 2017-11-07 09:20:41,842-0500 INFO (tasks/8) [storage.ThreadPool.WorkerThread] FINISH task 9ce348bc-e3fb-4f4e-aea0-f8c79e7ae204 (threadPool:210) 2017-11-07 09:20:42,388-0500 INFO (jsonrpc/4) [api.virt] START diskReplicateFinish(srcDisk={u'device': u'disk', u'poolID': u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', u'volumeID': u'8a1660d7-f153-4aca-9f25-c1184c10841a', u'domainID': u'4a08 8fb2-5497-4b4d-adec-4c91d998c56e', u'imageID': u'36837a9b-6396-4d65-a354-df97ce808f01'}, dstDisk={u'device': u'disk', u'poolID': u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', u'volumeID': u'8a1660d7-f153-4aca-9f25-c1184c10841a', u'domainID': u '4a088fb2-5497-4b4d-adec-4c91d998c56e', u'imageID': u'36837a9b-6396-4d65-a354-df97ce808f01'}) from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e (api:46) 2017-11-07 09:20:42,388-0500 ERROR (jsonrpc/4) [virt.vm] (vmId='61d328bc-c920-4691-997f-09bbecb5de10') Drive not found (srcDisk: {u'device': u'disk', u'poolID': u'b20f0eb7-6bea-4994-b87b-e1080c4fd9e5', u'volumeID': u'8a1660d7-f153-4aca-9f 25-c1184c10841a', u'domainID': u'4a088fb2-5497-4b4d-adec-4c91d998c56e', u'imageID': u'36837a9b-6396-4d65-a354-df97ce808f01'}) (vm:4386) 2017-11-07 09:20:42,389-0500 INFO (jsonrpc/4) [api.virt] FINISH diskReplicateFinish return={'status': {'message': 'Drive image file could not be found', 'code': 13}} from=::ffff:192.168.204.4,49358, flow_id=4bcdd94e (api:52) 2017-11-07 09:20:42,389-0500 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call VM.diskReplicateFinish failed (error 13) in 0.01 seconds (__init__:630) : <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></error> </body> </html> --------------106EB129C1BC1AEAACE8C19F--

2 2

[oVirt Jenkins] standard-enqueue - Build #6545 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Nov '17

08 Nov '17

------=_Part_116_725892865.1510145605581 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6545/ Build Name: #6545 Build Description: Gerrit: 83751 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83751 - title: build: ovirt-engine-3.6.13 - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Lev Veyde <lveyde(a)redhat.com> ------=_Part_116_725892865.1510145605581--

1 0

[oVirt Jenkins] standard-enqueue - Build #6543 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Nov '17

08 Nov '17

------=_Part_114_1515823510.1510143283153 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6543/ Build Name: #6543 Build Description: Gerrit: 83646 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/83646 - title: packaging: Add engine-host-update w/ support for oVirt Node - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Lev Veyde <lveyde(a)redhat.com> ------=_Part_114_1515823510.1510143283153--

1 0

[CQ]: 83756,3 (ovirt-engine-metrics) failed "ovirt-4.1" system tests
by oVirt Jenkins 08 Nov '17

08 Nov '17

Change 83756,3 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.1" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83756/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1286/

1 0

[JIRA] (OVIRT-1744) Revisit build artifact storage and retenesion
by Evgheni Dereveanchin (oVirt JIRA) 08 Nov '17

08 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1744: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Revisit build artifact storage and retenesion > --------------------------------------------- > > Key: OVIRT-1744 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: Highest > Labels: artifacts, repositories > > We need to revisit how we store and manage build artifacts in our environment. > We need to do this to reach several goals: > # Stop having to frequently deal with running out of space on the Jenkins server > # Stop having to frequently deal with running out of space on the Resources server > # Make Jenkins load faster > # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) > # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: > #* Knowing the build URL in Jenkins > #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. > #* Asking for STDCI stage/project/branch/distro/arch/latest artifact > We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[CQ]: 83745, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 Nov '17

08 Nov '17

Change 83745,1 (ovirt-engine-api-model) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83745/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/37/

1 0

[CQ]: 83647,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 08 Nov '17

08 Nov '17

Change 83647,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83647/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3666/

1 0

[JIRA] (OVIRT-1747) Make ost failures comment on the gerrit patch
by Barak Korren (oVirt JIRA) 08 Nov '17

08 Nov '17

This is a multi-part message in MIME format... ------------=_1510126466-30619-641 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1747?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1747: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) > Make ost failures comment on the gerrit patch > --------------------------------------------- > > Key: OVIRT-1747 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1747 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > It might be useful if Change Queue failure reports, and perhaps also > successes, be added as comments to the relevant gerrit patches. > Perhaps even mark -1 on failures, for visibility, even though they are > already merged and it does not mean much. > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510126466-30619-641 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1747?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1747:</h3> <pre>Resolution: Duplicate Status: Done (was: To Do)</pre> <blockquote><h3>Make ost failures comment on the gerrit patch</h3> <pre> Key: OVIRT-1747 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1747 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> It might be useful if Change Queue failure reports, and perhaps also successes, be added as comments to the relevant gerrit patches. Perhaps even mark -1 on failures, for visibility, even though they are already merged and it does not mean much. — Didi</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510126466-30619-641--

1 0

[JIRA] (OVIRT-1747) Make ost failures comment on the gerrit patch
by Barak Korren (oVirt JIRA) 08 Nov '17

08 Nov '17

This is a multi-part message in MIME format... ------------=_1510126390-13869-337 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1747?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1747: ------------------------------------- This is a duplicate of OVIRT-1447. It was planned to make CQ report to Gerrit all along. We're just not enabling that until we decide that the infra/race condition failure rate is low enough that developers will not start ignoring it. See list of blockers on OVIRT-1447. > Make ost failures comment on the gerrit patch > --------------------------------------------- > > Key: OVIRT-1747 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1747 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > It might be useful if Change Queue failure reports, and perhaps also > successes, be added as comments to the relevant gerrit patches. > Perhaps even mark -1 on failures, for visibility, even though they are > already merged and it does not mean much. > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510126390-13869-337 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1747?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1747:</h3> This is a duplicate of OVIRT-1447. It was planned to make CQ report to Gerrit all along. We're just not enabling that until we decide that the infra/race condition failure rate is low enough that developers will not start ignoring it. See list of blockers on OVIRT-1447. <blockquote><h3>Make ost failures comment on the gerrit patch</h3> <pre> Key: OVIRT-1747 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1747 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> It might be useful if Change Queue failure reports, and perhaps also successes, be added as comments to the relevant gerrit patches. Perhaps even mark -1 on failures, for visibility, even though they are already merged and it does not mean much. — Didi</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510126390-13869-337--

1 0

[JIRA] (OVIRT-1747) Make ost failures comment on the gerrit patch
by Yedidyah Bar David (oVirt JIRA) 08 Nov '17

08 Nov '17

Yedidyah Bar David created OVIRT-1747: ----------------------------------------- Summary: Make ost failures comment on the gerrit patch Key: OVIRT-1747 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1747 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra It might be useful if Change Queue failure reports, and perhaps also successes, be added as comments to the relevant gerrit patches. Perhaps even mark -1 on failures, for visibility, even though they are already merged and it does not mean much. -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

oVirt infra daily report - unstable production jobs - 498
by jenkins＠jenkins.phx.ovirt.org 07 Nov '17

07 Nov '17

------=_Part_104_2137352947.1510095602449 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/498//artifact/exported-a… Cheers, Jenkins ------=_Part_104_2137352947.1510095602449 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 07/11/2017 </th></tr><tr><th colspan=2 class=sub> <a href="http://jenkins.ovirt.org/">00 Unstable Critical</a> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/">ovirt-system-tests_ansible-suite-master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/">system-sync_mirrors-centos-extras-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_104_2137352947.1510095602449--

1 0

[CQ]: 83709, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 07 Nov '17

07 Nov '17

Change 83709,1 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83709/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3661/

1 0

[CQ]: 83549,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 07 Nov '17

07 Nov '17

Change 83549,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83549/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3654/

1 0

[CQ]: 83641,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 07 Nov '17

07 Nov '17

Change 83641,5 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83641/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3653/

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- {quote} If OST was cheap and quick, it would be lovely to run on any patch. It can also be run after a +2 from a maintainer, or after a workflow+1, providing a verified +0.5 to a patch. I don't know if that's what you're aiming at. {quote} OST is probably not going to ever be cheap and quick enough. I'm aiming at leveraging the same group-testing+bisection tech we use for post-merge OST runs. It was initially designed for pre-merge testing (a.k.a. gating) anyway, we just decided to deliver something that is useful and works before implementing everything we set out to. > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[ OST Failure Report ] [ oVirt Master ] [ 06-11-2017 ] [ 002_bootstrap.verify_add_hosts ]
by Dafna Ron 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format. --------------88DD9FCD3B3DDEA34D4EAEF4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, We failed test 002_bootstrap.verify_add_hosts I can see we only tried to install one of the hosts (host-0) and failed. the second host has no log which means we did not try to deploy it. The error suggests that we ovirt-imageio-daemon failed to start. However, there is another message that I think should be addressed about conflicting vdsm and libvirt configurations. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/83612/* * Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/artifact/ http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/artifact… * * *(Relevant) error snippet from the log: * * <error> \* 2017-11-06 02:56:46,526-0500 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.packages plugin.execute:921 execute-output: ('/usr/bin/vdsm-tool', 'configure', '--force') stdout: Checking configuration status... abrt is not configured for vdsm WARNING: LVM local configuration: /etc/lvm/lvmlocal.conf is not based on vdsm configuration lvm requires configuration libvirt is not configured for vdsm yet FAILED: conflicting vdsm and libvirt-qemu tls configuration. vdsm.conf with ssl=True requires the following changes: libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1 qemu.conf: spice_tls=1. multipath requires configuration 2017-11-06 02:56:47,551-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'ovirt-imageio-daemon.service') stderr: Job for ovirt-imageio-daemon.service failed because the control process exited with error code. See "systemctl status ovirt-imageio-daemon.service" and "journalctl -xe" for details. 2017-11-06 02:56:47,552-0500 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-R4R8gZhaQI/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-R4R8gZhaQI/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 179, in _start self.services.state('ovirt-imageio-daemon', True) File "/tmp/ovirt-R4R8gZhaQI/otopi-plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'ovirt-imageio-daemon' 2017-11-06 02:56:47,553-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio-daemon' ** *</error>* * * --------------88DD9FCD3B3DDEA34D4EAEF4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, We failed test 002_bootstrap.verify_add_hosts I can see we only tried to install one of the hosts (host-0) and failed. the second host has no log which means we did not try to deploy it. The error suggests that we ovirt-imageio-daemon failed to start. However, there is another message that I think should be addressed about conflicting vdsm and libvirt configurations. <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to suspected patches: <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/83612/">https://gerrit.ovirt.org/#/c/83612/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to Job: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to all logs: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/artifact/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/artifact/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/artifact…">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/artifact…</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">(Relevant) error snippet from the log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><error> \ <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">2017-11-06 02:56:46,526-0500 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.packages plugin.execute:921 execute-output: ('/usr/bin/vdsm-tool', 'configure', '--force') stdout: Checking configuration status... abrt is not configured for vdsm WARNING: LVM local configuration: /etc/lvm/lvmlocal.conf is not based on vdsm configuration lvm requires configuration libvirt is not configured for vdsm yet FAILED: conflicting vdsm and libvirt-qemu tls configuration. vdsm.conf with ssl=True requires the following changes: libvirtd.conf: listen_tcp=0, auth_tcp="sasl", listen_tls=1 qemu.conf: spice_tls=1. multipath requires configuration </pre> <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">2017-11-06 02:56:47,551-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'ovirt-imageio-daemon.service') stderr: Job for ovirt-imageio-daemon.service failed because the control process exited with error code. See "systemctl status ovirt-imageio-daemon.service" and "journalctl -xe" for details. 2017-11-06 02:56:47,552-0500 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-R4R8gZhaQI/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-R4R8gZhaQI/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 179, in _start self.services.state('ovirt-imageio-daemon', True) File "/tmp/ovirt-R4R8gZhaQI/otopi-plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'ovirt-imageio-daemon' 2017-11-06 02:56:47,553-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio-daemon'</pre> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></error> </body> </html> --------------88DD9FCD3B3DDEA34D4EAEF4--

5 7

[JIRA] (OVIRT-1743) ci please build and send to OST
by danken (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] danken commented on OVIRT-1743: ------------------------------- If OST was cheap and quick, it would be lovely to run on any patch. It can also be run after a +2 from a maintainer, or after a workflow+1, providing a verified +0.5 to a patch. I don't know if that's what you're aiming at. > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1746) Make stand-alone upstream source collection and updating tool
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510046714-26505-534 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1746?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1746: ----------------------------------- Assignee: Barak Korren (was: infra) > Make stand-alone upstream source collection and updating tool > ------------------------------------------------------------- > > Key: OVIRT-1746 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1746 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection code is currently built included in two different files - "{{upstream-source-collector.py}}" and "{{poll-upstream-sources.py}}". The files reside in "{{jobs/confs/python-scripts}}" which in turn mean they are mean for embedding into jobs by JJB. > This situation causes several issues: > # It is not easy for users to use these scripts locally, and hence its difficult to build or test repos that include upstream source dependencies locally > # There is code duplication between the two python scripts > # Adding certain features is harder because it requires one of the scripts to have access to code that resides in the other script (See OVIRT-1641 for example) > # It is impossible to use the code from pipelines (See OVIRT-1745) > # It is not east to add tests for the code > It is desirable to have the upstream source handling code be concentrated into a single tool that resides in the '{{scripts}}' directory. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510046714-26505-534 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1746?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1746:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Make stand-alone upstream source collection and updating tool</h3> <pre> Key: OVIRT-1746 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1746 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: Barak Korren Labels: poll-upstream-sources, upstream-source-collector</pre> The upstream source collection code is currently built included in two different files – “{{upstream-source-collector.py}}” and “{{poll-upstream-sources.py}}”. The files reside in “{{jobs/confs/python-scripts}}” which in turn mean they are mean for embedding into jobs by JJB. This situation causes several issues: # It is not easy for users to use these scripts locally, and hence its difficult to build or test repos that include upstream source dependencies locally # There is code duplication between the two python scripts # Adding certain features is harder because it requires one of the scripts to have access to code that resides in the other script (See OVIRT-1641 for example) # It is impossible to use the code from pipelines (See OVIRT-1745) # It is not east to add tests for the code It is desirable to have the upstream source handling code be concentrated into a single tool that resides in the ‘{{scripts}}’ directory.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510046714-26505-534--

1 0

[JIRA] (OVIRT-1746) Make stand-alone upstream source collection and updating tool
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

Barak Korren created OVIRT-1746: ----------------------------------- Summary: Make stand-alone upstream source collection and updating tool Key: OVIRT-1746 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1746 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra The upstream source collection code is currently built included in two different files - "{{upstream-source-collector.py}}" and "{{poll-upstream-sources.py}}". The files reside in "{{jobs/confs/python-scripts}}" which in turn mean they are mean for embedding into jobs by JJB. This situation causes several issues: # It is not easy for users to use these scripts locally, and hence its difficult to build or test repos that include upstream source dependencies locally # There is code duplication between the two python scripts # Adding certain features is harder because it requires one of the scripts to have access to code that resides in the other script (See OVIRT-1641 for example) # It is impossible to use the code from pipelines (See OVIRT-1745) # It is not east to add tests for the code It is desirable to have the upstream source handling code be concentrated into a single tool that resides in the '{{scripts}}' directory. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1746) Make stand-alone upstream source collection and updating tool
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1746?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1746: -------------------------------- Epic Link: OVIRT-400 > Make stand-alone upstream source collection and updating tool > ------------------------------------------------------------- > > Key: OVIRT-1746 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1746 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection code is currently built included in two different files - "{{upstream-source-collector.py}}" and "{{poll-upstream-sources.py}}". The files reside in "{{jobs/confs/python-scripts}}" which in turn mean they are mean for embedding into jobs by JJB. > This situation causes several issues: > # It is not easy for users to use these scripts locally, and hence its difficult to build or test repos that include upstream source dependencies locally > # There is code duplication between the two python scripts > # Adding certain features is harder because it requires one of the scripts to have access to code that resides in the other script (See OVIRT-1641 for example) > # It is impossible to use the code from pipelines (See OVIRT-1745) > # It is not east to add tests for the code > It is desirable to have the upstream source handling code be concentrated into a single tool that resides in the '{{scripts}}' directory. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1680) Adapt STDCI pipelines for use in Gerrit projects
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510045336-25494-507 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1680?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1680: ------------------------------------- Adding OVIRT-1745 as a blocker because we need the upstream source collection code to support pipelines before we can migrate everything to pipelines. > Adapt STDCI pipelines for use in Gerrit projects > ------------------------------------------------ > > Key: OVIRT-1680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1680 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, standard-ci > > So far work on OVIRT-1522 focused on GitHub, and it is now feature-complete. > Now its time to make this work also available for Gerrit projects. > OVIRT-1629 is a blocker for this ticket because the '{{automation.yaml}}' implementation in the current STDCI pipelines does not yet support everything that the existing JJB YAML does. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510045336-25494-507 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1680?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1680:</h3> Adding OVIRT-1745 as a blocker because we need the upstream source collection code to support pipelines before we can migrate everything to pipelines. <blockquote><h3>Adapt STDCI pipelines for use in Gerrit projects</h3> <pre> Key: OVIRT-1680 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1680 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: gerrit, standard-ci</pre> So far work on OVIRT-1522 focused on GitHub, and it is now feature-complete. Now its time to make this work also available for Gerrit projects. OVIRT-1629 is a blocker for this ticket because the ‘{{automation.yaml}}’ implementation in the current STDCI pipelines does not yet support everything that the existing JJB YAML does.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510045336-25494-507--

1 0

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510045269-22278-509 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1745: -------------------------------- Epic Link: OVIRT-400 > Make upstream source collection and polling code usable for pipelines > --------------------------------------------------------------------- > > Key: OVIRT-1745 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: > # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org > # This creates a situation where in order to get the STDCI code we need to run the upstream sources code > # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code > # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script. > # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510045269-22278-509 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1745:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Make upstream source collection and polling code usable for pipelines</h3> <pre> Key: OVIRT-1745 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: poll-upstream-sources, upstream-source-collector</pre> The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: # We support having ‘jenkins’ repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main ‘jenkins’ repo in gerrit.ovirt.org # This creates a situation where in order to get the STDCI code we need to run the upstream sources code # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code # To solve this issue we simply embedded the upstream sources code into the job code by using ‘{{#include}}’ in JJB rather then running it as a stand-alone script. # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510045269-22278-509--

1 0

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

Barak Korren created OVIRT-1745: ----------------------------------- Summary: Make upstream source collection and polling code usable for pipelines Key: OVIRT-1745 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org # This creates a situation where in order to get the STDCI code we need to run the upstream sources code # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script. # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 330 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Nov '17

07 Nov '17

------=_Part_38_1635750858.1509807911637 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build Number: 330 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #330 [Yuval Turgeman] automation: view install log in console ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_38_1635750858.1509807911637--

1 3

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #958
by jenkins＠jenkins.phx.ovirt.org 07 Nov '17

07 Nov '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/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 2d0aecce46cfa1b3a1770ab846c983bf95f82328 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2d0aecce46cfa1b3a1770ab846c983bf95f82328 Commit message: "Make mirror_mgr.sh drop yum MD cache before sync" > git rev-list 2d0aecce46cfa1b3a1770ab846c983bf95f82328 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3001790901476836819.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 Error setting up repositories: centos-updates-el7: Check uncompressed DB failed Build step 'Execute shell' marked build as failure

1 4

[JIRA] (OVIRT-1680) Adapt STDCI pipelines for use in Gerrit projects
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1680?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1680: ------------------------------------- Adding OVIRT-1657 as a blocker, because we common white-list handling code in order to use the same pipeline code for both Gerrit and GitHub > Adapt STDCI pipelines for use in Gerrit projects > ------------------------------------------------ > > Key: OVIRT-1680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1680 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, standard-ci > > So far work on OVIRT-1522 focused on GitHub, and it is now feature-complete. > Now its time to make this work also available for Gerrit projects. > OVIRT-1629 is a blocker for this ticket because the '{{automation.yaml}}' implementation in the current STDCI pipelines does not yet support everything that the existing JJB YAML does. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1680) Adapt STDCI pipelines for use in Gerrit projects
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1680?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1680: ------------------------------------- Adding OVIRT-1744 as a blocker because moving existing jobs to pipelines will mean the stand-alone 'build-artifacts' jobs will cease to exists, which in turn means we need a new, stable, place that users can rely on to get the letest pre-tested artifacts. > Adapt STDCI pipelines for use in Gerrit projects > ------------------------------------------------ > > Key: OVIRT-1680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1680 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, standard-ci > > So far work on OVIRT-1522 focused on GitHub, and it is now feature-complete. > Now its time to make this work also available for Gerrit projects. > OVIRT-1629 is a blocker for this ticket because the '{{automation.yaml}}' implementation in the current STDCI pipelines does not yet support everything that the existing JJB YAML does. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[ OST Failure Report ] [ oVirt master ] [ 06-11-2017] [ 002_bootstrap.add_hosts ]
by Dafna Ron 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format. --------------F7FAC86DB10D28BA8B32AB1D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, We have a failure in test 002_bootstrap.add_hosts I can see that the hosts are added but there are errors in engine.log that suggest there is a problem with crypto. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/83367/* * Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/artifact/ ** http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/artifact… (Relevant) error snippet from the log: <error> * 2017-11-06 10:29:55,367-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.DbFacadeUtils] (default task-7) [d5f76e37-ef60-4195-a735-400c1ed293be] Failed to decrypt password: javax.crypto.BadPaddingException: Decryption error at sun.security.rsa.RSAPadding.unpadV15(RSAPadding.java:380) [rt.jar:1.8.0_151] at sun.security.rsa.RSAPadding.unpad(RSAPadding.java:291) [rt.jar:1.8.0_151] at com.sun.crypto.provider.RSACipher.doFinal(RSACipher.java:363) [sunjce_provider.jar:1.8.0_151] at com.sun.crypto.provider.RSACipher.engineDoFinal(RSACipher.java:389) [sunjce_provider.jar:1.8.0_151] at javax.crypto.Cipher.doFinal(Cipher.java:2165) [jce.jar:1.8.0_151] at org.ovirt.engine.core.utils.crypt.EngineEncryptionUtils.decrypt(EngineEncryptionUtils.java:179) [utils.jar:] at org.ovirt.engine.core.dal.dbbroker.DbFacadeUtils.decryptPassword(DbFacadeUtils.java:35) [dal.jar:] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper.mapRow(ProviderDaoImpl.java:137) [dal.jar:] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper.mapRow(ProviderDaoImpl.java:119) [dal.jar:] at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:93) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:60) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:463) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:408) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:474) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:484) [spring-jdbc.jar:4.3.9.RELEASE] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl.getAllWithQuery(ProviderDaoImpl.java:189) [dal.jar:] at org.ovirt.engine.core.bll.SearchQuery.genericSearch(SearchQuery.java:337) [bll.jar:] at org.ovirt.engine.core.bll.SearchQuery.searchProviders(SearchQuery.java:408) [bll.jar:] at org.ovirt.engine.core.bll.SearchQuery.executeQueryCommand(SearchQuery.java:215) [bll.jar:] at org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:106) [bll.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendQueryExecutor.execute(DefaultBackendQueryExecutor.java:14) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:579) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:548) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_151] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:92) [wildfly-weld-ejb-11.0.0.Final.jar:11.0.0.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.interceptorChainCompleted(WeldInvocationContext.java:98) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:117) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.invokeNext(WeldInvocationContext.java:83) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:115) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:108) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:82) [wildfly-weld-ejb-11.0.0.Final.jar:11.0.0.Final] at org.jboss.as.weld.interceptors.EjbComponentInterceptorSupport.delegateInterception(EjbComponentInterceptorSupport.java:60) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:76) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:88) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.ovirt.engine.core.bll.interceptors.CorrelationIdTrackerInterceptor.aroundInvoke(CorrelationIdTrackerInterceptor.java:13) [bll.jar:] at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:264) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:379) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:244) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at org.ovirt.engine.core.common.interfaces.BackendLocal$$$view3.runQuery(Unknown Source) [common.jar:] at org.ovirt.engine.api.restapi.resource.BackendResource.runQuery(BackendResource.java:82) at org.ovirt.engine.api.restapi.resource.BackendResource.getBackendCollection(BackendResource.java:152) at org.ovirt.engine.api.restapi.resource.AbstractBackendCollectionResource.getBackendCollection(AbstractBackendCollectionResource.java:48) at org.ovirt.engine.api.restapi.resource.openstack.BackendOpenStackNetworkProvidersResource.getBackendCollection(BackendOpenStackNetworkProvidersResource.java:70) at org.ovirt.engine.api.restapi.resource.openstack.BackendOpenStackNetworkProvidersResource.list(BackendOpenStackNetworkProvidersResource.java:50) at org.ovirt.engine.api.resource.openstack.OpenstackNetworkProvidersResource.doList(OpenstackNetworkProvidersResource.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_151] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:138) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:101) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:406) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:213) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:228) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:81) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:274) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:209) at io.undertow.servlet.spec.RequestDispatcherImpl.forwardImpl(RequestDispatcherImpl.java:221) at io.undertow.servlet.spec.RequestDispatcherImpl.forwardImplSetup(RequestDispatcherImpl.java:147) at io.undertow.servlet.spec.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:111) at org.ovirt.engine.api.restapi.invocation.VersionFilter.doFilter(VersionFilter.java:180) at org.ovirt.engine.api.restapi.invocation.VersionFilter.doFilter(VersionFilter.java:98) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.api.restapi.invocation.CurrentFilter.doFilter(CurrentFilter.java:117) at org.ovirt.engine.api.restapi.invocation.CurrentFilter.doFilter(CurrentFilter.java:72) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.RestApiSessionMgmtFilter.doFilter(RestApiSessionMgmtFilter.java:78) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.EnforceAuthFilter.doFilter(EnforceAuthFilter.java:42) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter.doFilter(SsoRestApiNegotiationFilter.java:84) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter.doFilter(SsoRestApiAuthFilter.java:47) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.SessionValidationFilter.doFilter(SessionValidationFilter.java:59) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.RestApiSessionValidationFilter.doFilter(RestApiSessionValidationFilter.java:35) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.api.restapi.security.CSRFProtectionFilter.doFilter(CSRFProtectionFilter.java:111) at org.ovirt.engine.api.restapi.security.CSRFProtectionFilter.doFilter(CSRFProtectionFilter.java:102) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.utils.servlet.CORSSupportFilter.doFilter(CORSSupportFilter.java:284) [utils.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151] 2017-11-06 10:29:55,378-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-7) [d5f76e37-ef60-4195-a735-400c1ed293be] method: runQuery, params: [Search, SearchParameters:{refresh='false', filtered='false', searchType='Provider', searchPattern='Providers: type=EXTERNAL_NETWORK', caseSensitive='false', from='0', max='2147483647'}], timeElapsed: 49ms 2017-11-06 10:29:55,384-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] Entered SsoRestApiAuthFilter 2017-11-06 10:29:55,384-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] SsoRestApiAuthFilter authenticating with sso 2017-11-06 10:29:55,384-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] SsoRestApiAuthFilter authenticating using BEARER header 2017-11-06 10:29:55,387-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] SsoRestApiAuthFilter successfully authenticated using BEARER header 2017-11-06 10:29:55,387-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-8) [] Entered SsoRestApiNegotiationFilter 2017-11-06 10:29:55,389-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-8) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth ** *</error>* * * --------------F7FAC86DB10D28BA8B32AB1D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, We have a failure in test 002_bootstrap.add_hosts I can see that the hosts are added but there are errors in engine.log that suggest there is a problem with crypto. <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to suspected patches: <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/83367/">https://gerrit.ovirt.org/#/c/83367/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to Job: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to all logs: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/artifact/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/artifact/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/artifact…">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/artifact…</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">(Relevant) error snippet from the log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><error> <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">2017-11-06 10:29:55,367-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.DbFacadeUtils] (default task-7) [d5f76e37-ef60-4195-a735-400c1ed293be] Failed to decrypt password: javax.crypto.BadPaddingException: Decryption error at sun.security.rsa.RSAPadding.unpadV15(RSAPadding.java:380) [rt.jar:1.8.0_151] at sun.security.rsa.RSAPadding.unpad(RSAPadding.java:291) [rt.jar:1.8.0_151] at com.sun.crypto.provider.RSACipher.doFinal(RSACipher.java:363) [sunjce_provider.jar:1.8.0_151] at com.sun.crypto.provider.RSACipher.engineDoFinal(RSACipher.java:389) [sunjce_provider.jar:1.8.0_151] at javax.crypto.Cipher.doFinal(Cipher.java:2165) [jce.jar:1.8.0_151] at org.ovirt.engine.core.utils.crypt.EngineEncryptionUtils.decrypt(EngineEncryptionUtils.java:179) [utils.jar:] at org.ovirt.engine.core.dal.dbbroker.DbFacadeUtils.decryptPassword(DbFacadeUtils.java:35) [dal.jar:] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper.mapRow(ProviderDaoImpl.java:137) [dal.jar:] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper.mapRow(ProviderDaoImpl.java:119) [dal.jar:] at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:93) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:60) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:463) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:408) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:474) [spring-jdbc.jar:4.3.9.RELEASE] at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:484) [spring-jdbc.jar:4.3.9.RELEASE] at org.ovirt.engine.core.dao.provider.ProviderDaoImpl.getAllWithQuery(ProviderDaoImpl.java:189) [dal.jar:] at org.ovirt.engine.core.bll.SearchQuery.genericSearch(SearchQuery.java:337) [bll.jar:] at org.ovirt.engine.core.bll.SearchQuery.searchProviders(SearchQuery.java:408) [bll.jar:] at org.ovirt.engine.core.bll.SearchQuery.executeQueryCommand(SearchQuery.java:215) [bll.jar:] at org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:106) [bll.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.bll.executor.DefaultBackendQueryExecutor.execute(DefaultBackendQueryExecutor.java:14) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:579) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:548) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_151] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:92) [wildfly-weld-ejb-11.0.0.Final.jar:11.0.0.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.interceptorChainCompleted(WeldInvocationContext.java:98) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:117) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.invokeNext(WeldInvocationContext.java:83) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.WeldInvocationContext.proceed(WeldInvocationContext.java:115) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:108) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:82) [wildfly-weld-ejb-11.0.0.Final.jar:11.0.0.Final] at org.jboss.as.weld.interceptors.EjbComponentInterceptorSupport.delegateInterception(EjbComponentInterceptorSupport.java:60) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:76) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:88) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.ovirt.engine.core.bll.interceptors.CorrelationIdTrackerInterceptor.aroundInvoke(CorrelationIdTrackerInterceptor.java:13) [bll.jar:] at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:264) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:379) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:244) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-11.0.0.Final.jar:11.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at org.ovirt.engine.core.common.interfaces.BackendLocal$$$view3.runQuery(Unknown Source) [common.jar:] at org.ovirt.engine.api.restapi.resource.BackendResource.runQuery(BackendResource.java:82) at org.ovirt.engine.api.restapi.resource.BackendResource.getBackendCollection(BackendResource.java:152) at org.ovirt.engine.api.restapi.resource.AbstractBackendCollectionResource.getBackendCollection(AbstractBackendCollectionResource.java:48) at org.ovirt.engine.api.restapi.resource.openstack.BackendOpenStackNetworkProvidersResource.getBackendCollection(BackendOpenStackNetworkProvidersResource.java:70) at org.ovirt.engine.api.restapi.resource.openstack.BackendOpenStackNetworkProvidersResource.list(BackendOpenStackNetworkProvidersResource.java:50) at org.ovirt.engine.api.resource.openstack.OpenstackNetworkProvidersResource.doList(OpenstackNetworkProvidersResource.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_151] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:138) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:101) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:406) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:213) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:228) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.24.Final.jar:3.0.24.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:81) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:274) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchToPath(ServletInitialHandler.java:209) at io.undertow.servlet.spec.RequestDispatcherImpl.forwardImpl(RequestDispatcherImpl.java:221) at io.undertow.servlet.spec.RequestDispatcherImpl.forwardImplSetup(RequestDispatcherImpl.java:147) at io.undertow.servlet.spec.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:111) at org.ovirt.engine.api.restapi.invocation.VersionFilter.doFilter(VersionFilter.java:180) at org.ovirt.engine.api.restapi.invocation.VersionFilter.doFilter(VersionFilter.java:98) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.api.restapi.invocation.CurrentFilter.doFilter(CurrentFilter.java:117) at org.ovirt.engine.api.restapi.invocation.CurrentFilter.doFilter(CurrentFilter.java:72) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.RestApiSessionMgmtFilter.doFilter(RestApiSessionMgmtFilter.java:78) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.EnforceAuthFilter.doFilter(EnforceAuthFilter.java:42) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter.doFilter(SsoRestApiNegotiationFilter.java:84) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter.doFilter(SsoRestApiAuthFilter.java:47) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.SessionValidationFilter.doFilter(SessionValidationFilter.java:59) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.aaa.filters.RestApiSessionValidationFilter.doFilter(RestApiSessionValidationFilter.java:35) [aaa.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.api.restapi.security.CSRFProtectionFilter.doFilter(CSRFProtectionFilter.java:111) at org.ovirt.engine.api.restapi.security.CSRFProtectionFilter.doFilter(CSRFProtectionFilter.java:102) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at org.ovirt.engine.core.utils.servlet.CORSSupportFilter.doFilter(CORSSupportFilter.java:284) [utils.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151] 2017-11-06 10:29:55,378-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-7) [d5f76e37-ef60-4195-a735-400c1ed293be] method: runQuery, params: [Search, SearchParameters:{refresh='false', filtered='false', searchType='Provider', searchPattern='Providers: type=EXTERNAL_NETWORK', caseSensitive='false', from='0', max='2147483647'}], timeElapsed: 49ms 2017-11-06 10:29:55,384-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] Entered SsoRestApiAuthFilter 2017-11-06 10:29:55,384-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] SsoRestApiAuthFilter authenticating with sso 2017-11-06 10:29:55,384-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] SsoRestApiAuthFilter authenticating using BEARER header 2017-11-06 10:29:55,387-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiAuthFilter] (default task-8) [] SsoRestApiAuthFilter successfully authenticated using BEARER header 2017-11-06 10:29:55,387-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-8) [] Entered SsoRestApiNegotiationFilter 2017-11-06 10:29:55,389-05 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-8) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth</pre> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></error> </body> </html> --------------F7FAC86DB10D28BA8B32AB1D--

3 2

[CQ]: 83434, 11 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 07 Nov '17

07 Nov '17

Change 83434,11 (ovirt-engine-api-model) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83434/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3646/

1 0

[JIRA] (OVIRT-1744) Revisit build artifact storage and retenesion
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510042656-11287-520 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1744: -------------------------------- Summary: Revisit build artifact storage and retenesion (was: Revisit build artifact storage and retnesion) > Revisit build artifact storage and retenesion > --------------------------------------------- > > Key: OVIRT-1744 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: artifacts, repositories > > We need to revisit how we store and manage build artifacts in our environment. > We need to do this to reach several goals: > # Stop having to frequently deal with running out of space on the Jenkins server > # Stop having to frequently deal with running out of space on the Resources server > # Make Jenkins load faster > # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) > # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: > #* Knowing the build URL in Jenkins > #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. > #* Asking for STDCI stage/project/branch/distro/arch/latest artifact > We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510042656-11287-520 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1744:</h3> <pre>Summary: Revisit build artifact storage and retenesion (was: Revisit build artifact storage and retnesion)</pre> <blockquote><h3>Revisit build artifact storage and retenesion</h3> <pre> Key: OVIRT-1744 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Highest Labels: artifacts, repositories</pre> We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510042656-11287-520--

1 0

[JIRA] (OVIRT-1744) Revisit build artifact storage and retnesion
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510042642-11328-477 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1744: ------------------------------------- [~ederevea] We talked about this before, but AFAIK did not open a ticket. We need to start working on this. IMO, barring prevention of looming outage scenarios, this should be our top priority. I think we need to look at block-level de-duplication solutions. I think Red Hat recently bought a company that provides a block-level de-duplication software solution. This solution might be available in CentOS by now. Given that we store build results, I expect the actual data difference between different builds of the same package to be small. Additionally, the big packages like 'node' and 'appliance' are essentially collections of other packages, so they share data with them. All this makes me estimate that block-level de-duplication might provide very good results for us as far as storage efficiency goes. I also suspect that storing data on less disk blocks can make processes like `createrepo`, which is by far the biggest time consumer when publishing to 'tested', run faster. Another block-level de-duplication solution is [casync|http://0pointer.net/blog/casync-a-tool-for-distributing-file-system-…] which is a de-duplicating rsync-style tool. The main shortcoming here is that I'm not sure we can make using it transparent. Another direction to look at is [pulp|http://docs.pulpproject.org/index.html] I think it can at least help when it comes to making publish performance better and to efficiently making data available in multiple ways. Maybe we can even somhow combine it with a de-duplicating backend storage. > Revisit build artifact storage and retnesion > -------------------------------------------- > > Key: OVIRT-1744 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: artifacts, repositories > > We need to revisit how we store and manage build artifacts in our environment. > We need to do this to reach several goals: > # Stop having to frequently deal with running out of space on the Jenkins server > # Stop having to frequently deal with running out of space on the Resources server > # Make Jenkins load faster > # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) > # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: > #* Knowing the build URL in Jenkins > #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. > #* Asking for STDCI stage/project/branch/distro/arch/latest artifact > We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510042642-11328-477 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1744:</h3> [~ederevea] We talked about this before, but AFAIK did not open a ticket. We need to start working on this. IMO, barring prevention of looming outage scenarios, this should be our top priority. I think we need to look at block-level de-duplication solutions. I think Red Hat recently bought a company that provides a block-level de-duplication software solution. This solution might be available in CentOS by now. Given that we store build results, I expect the actual data difference between different builds of the same package to be small. Additionally, the big packages like ‘node’ and ‘appliance’ are essentially collections of other packages, so they share data with them. All this makes me estimate that block-level de-duplication might provide very good results for us as far as storage efficiency goes. I also suspect that storing data on less disk blocks can make processes like `createrepo`, which is by far the biggest time consumer when publishing to ‘tested’, run faster. Another block-level de-duplication solution is [casync|<a href="http://0pointer.net/blog/casync-a-tool-for-distributing-file-system-images.…">http://0pointer.net/blog/casync-a-tool-for-distributing-file-system-images.…</a>], which is a de-duplicating rsync-style tool. The main shortcoming here is that I'm not sure we can make using it transparent. Another direction to look at is [pulp|<a href="http://docs.pulpproject.org/index.html">http://docs.pulpproject.org/index.html</a>]. I think it can at least help when it comes to making publish performance better and to efficiently making data available in multiple ways. Maybe we can even somhow combine it with a de-duplicating backend storage. <blockquote><h3>Revisit build artifact storage and retnesion</h3> <pre> Key: OVIRT-1744 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Highest Labels: artifacts, repositories</pre> We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510042642-11328-477--

1 0

[JIRA] (OVIRT-1744) Revisit build artifact storage and retnesion
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510041765-21211-504 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1744: -------------------------------- Description: We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. was: We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them is possible. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. > Revisit build artifact storage and retnesion > -------------------------------------------- > > Key: OVIRT-1744 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: artifacts, repositories > > We need to revisit how we store and manage build artifacts in our environment. > We need to do this to reach several goals: > # Stop having to frequently deal with running out of space on the Jenkins server > # Stop having to frequently deal with running out of space on the Resources server > # Make Jenkins load faster > # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) > # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: > #* Knowing the build URL in Jenkins > #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. > #* Asking for STDCI stage/project/branch/distro/arch/latest artifact > We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510041765-21211-504 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1744:</h3> <pre>Description:</pre> We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. <pre>was:</pre> We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them is possible. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. <blockquote><h3>Revisit build artifact storage and retnesion</h3> <pre> Key: OVIRT-1744 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Highest Labels: artifacts, repositories</pre> We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510041765-21211-504--

1 0

[JIRA] (OVIRT-1744) Revisit build artifact storage and retnesion
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

This is a multi-part message in MIME format... ------------=_1510041088-29267-458 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1744: ----------------------------------- Summary: Revisit build artifact storage and retnesion Key: OVIRT-1744 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Highest We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them is possible. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510041088-29267-458 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1744:</h3> <pre> Summary: Revisit build artifact storage and retnesion Key: OVIRT-1744 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Highest</pre> We need to revisit how we store and manage build artifacts in our environment. We need to do this to reach several goals: # Stop having to frequently deal with running out of space on the Jenkins server # Stop having to frequently deal with running out of space on the Resources server # Make Jenkins load faster # Make publishing of artifacts faster (If can take up to 20m to publish to ‘tested’ ATM) # Make it so that finding artifacts is possible without knowing the exact details of the job that made them is possible. We would like to be able to find artifacts by at least: #* Knowing the build URL in Jenkins #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. #* Asking for STDCI stage/project/branch/distro/arch/latest artifact We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510041088-29267-458--

1 0

[JIRA] (OVIRT-1744) Revisit build artifact storage and retnesion
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1744?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1744: -------------------------------- Epic Link: OVIRT-403 > Revisit build artifact storage and retnesion > -------------------------------------------- > > Key: OVIRT-1744 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1744 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: artifacts, repositories > > We need to revisit how we store and manage build artifacts in our environment. > We need to do this to reach several goals: > # Stop having to frequently deal with running out of space on the Jenkins server > # Stop having to frequently deal with running out of space on the Resources server > # Make Jenkins load faster > # Make publishing of artifacts faster (If can take up to 20m to publish to 'tested' ATM) > # Make it so that finding artifacts is possible without knowing the exact details of the job that made them is possible. We would like to be able to find artifacts by at least: > #* Knowing the build URL in Jenkins > #* Knowing the STDCI stage/project/branch/distro/arch/git hash combination. > #* Asking for STDCI stage/project/branch/distro/arch/latest artifact > We need to achieve the above without significantly harming the UX we provide. For example, users should still be able to find artifacts by navigating from links posted to Gerrit/GitHub to the Jenkins job result pages. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 07 Nov '17

07 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- {quote} I suppose this is not a joke, so I'll answer it seriously. Yes. Vdsm and Engine are too big and complex. {quote} Are there low-hanging fruits there? Could we improve the per-patch checking infrastructure in one way or another to reduce the need to run full OST? Will separate checking "threads" that respond asynchronously help? {quote} Regardless, commit/fail/revert/fix is a frustrating development model. post/test/fix/commit is so much better. {quote} Perhaps we can make efforts to structure patches so that commit/fail/fix can be more common then commit/fail/revert/fix? Will one or both of the following things help? # Lower latency of CQ/OST results # Posting CQ/OST results back directly to Gerrit > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 83 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Nov '17

07 Nov '17

------=_Part_60_1711266159.1509937589124 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1= /=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/8= 3/ Build Number: 83 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #83 [Yaniv Kaul] Install multiple hosts faster - in the perf. suite. ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 404 reason: Not Found detail: Entity not found: null -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function <lambda> a= t 0x37455f0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_sanity.py", line = 203, in <lambda> (len(api.vms.get(VM0_NAME).snapshots.list()) =3D=3D 2) and File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 34602, in list headers=3D{"All-Content":all_content} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 46, in get return self.request(method=3D'GET', url=3Durl, headers=3Dheaders, cls= =3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) RequestError:=20 status: 404 reason: Not Found detail: Entity not found: null --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in= wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_sanity.py", line = 202, in snapshot_merge lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 267, i= n assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 251, i= n assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=3Dallowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_sanity.py", line = 203, in <lambda> (len(api.vms.get(VM0_NAME).snapshots.list()) =3D=3D 2) and File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 34602, in list headers=3D{"All-Content":all_content} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 46, in get return self.request(method=3D'GET', url=3Durl, headers=3Dheaders, cls= =3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) '\r\nstatus: 404\r\nreason: Not Found\r\ndetail: Entity not found: null\n--= ------------------ >> begin captured logging << --------------------\novirt= lago.testlib: ERROR: * Unhandled exception in <function <lambda> at 0x3= 7455f0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/sit= e-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n re= s =3D func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-s= uite-4.1/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_san= ity.py", line 203, in <lambda>\n (len(api.vms.get(VM0_NAME).snapshots.li= st()) =3D=3D 2) and\n File "/usr/lib/python2.7/site-packages/ovirtsdk/infr= astructure/brokers.py", line 34602, in list\n headers=3D{"All-Content":a= ll_content}\n File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructu= re/proxy.py", line 46, in get\n return self.request(method=3D\'GET\', ur= l=3Durl, headers=3Dheaders, cls=3Dcls)\n File "/usr/lib/python2.7/site-pac= kages/ovirtsdk/infrastructure/proxy.py", line 122, in request\n persiste= nt_auth=3Dself.__persistent_auth\n File "/usr/lib/python2.7/site-packages/= ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request\n pe= rsistent_auth)\n File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastru= cture/connectionspool.py", line 162, in __do_request\n raise errors.Requ= estError(response_code, response_reason, response_body)\nRequestError: \r\n= status: 404\r\nreason: Not Found\r\ndetail: Entity not found: null\n-------= -------------- >> end captured logging << ---------------------' ------=_Part_60_1711266159.1509937589124--

1 1

oVirt infra daily report - unstable production jobs - 497
by jenkins＠jenkins.phx.ovirt.org 06 Nov '17

06 Nov '17

------=_Part_80_963123067.1510009202987 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/497//artifact/exported-a… Cheers, Jenkins ------=_Part_80_963123067.1510009202987 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 06/11/2017 </th></tr><tr><th colspan=2 class=sub> <a href="http://jenkins.ovirt.org/">00 Unstable Critical</a> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/">ovirt-system-tests_ansible-suite-master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/">ovirt-system-tests_hc-basic-suite-4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/">system-sync_mirrors-centos-extras-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_80_963123067.1510009202987--

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by danken (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1510006351-29159-205 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] danken commented on OVIRT-1743: ------------------------------- > Could it be that the project contains too much independent stuff in it? I suppose this is not a joke, so I'll answer it seriously. Yes. Vdsm and Engine are too big and complex. Regardless, commit/fail/revert/fix is a frustrating development model. post/test/fix/commit is so much better. > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510006351-29159-205 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ]</pre> <h3>danken commented on OVIRT-1743:</h3> <blockquote>Could it be that the project contains too much independent stuff in it?</blockquote> I suppose this is not a joke, so I'll answer it seriously. Yes. Vdsm and Engine are too big and complex. Regardless, commit/fail/revert/fix is a frustrating development model. post/test/fix/commit is so much better. <blockquote><h3>ci please build and send to OST</h3> <pre> Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra Labels: change-queue</pre> Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to <ul><li>“ci please build”</li> <li>copy el7 url</li> <li>wait for el7 build to finish</li> <li>copy artifacts url to ovirt--system-test-manual, start it</li> <li>copy the ost run URL to the gerrit patch, so I have it for reference of failure/success.</li></ul></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1510006351-29159-205--

1 0

[CQ]: 83367,13 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 06 Nov '17

06 Nov '17

Change 83367,13 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83367/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Labels: change-queue (was: ) > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509983544-29358-142 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Component/s: oVirt CI > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509983544-29358-142 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1743:</h3> <pre>Component/s: oVirt CI</pre> <blockquote><h3>ci please build and send to OST</h3> <pre> Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra</pre> Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to <ul><li>“ci please build”</li> <li>copy el7 url</li> <li>wait for el7 build to finish</li> <li>copy artifacts url to ovirt--system-test-manual, start it</li> <li>copy the ost run URL to the gerrit patch, so I have it for reference of failure/success.</li></ul></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <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> ------------=_1509983544-29358-142--

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- BTW I wonder why you need to run OST manually so often. We have change gating, so when merging a breaking change, you're only breaking the particular project you merged a change into. Other, unrelated projects can keep being tested against the last known working version... Could it be that the project contains too much independent stuff in it? > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0