March 2019 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2699) proxy01.phx.ovirt.org:3128 can't be reached from Jenkins slaves

by sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-2699: ------------------------------- Summary: proxy01.phx.ovirt.org:3128 can't be reached from Jenkins slaves Key: OVIRT-2699 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2699 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Jenkins jobs are issuing warning like: Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config Example: https://jenkins.ovirt.org/job/ovirt-lldp-labeler_standard-check-patch/18/... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

5 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-2697) error before starting tests

by Ahmad Khiet (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jir... ] Ahmad Khiet commented on OVIRT-2697: ------------------------------------ tried, I'm still getting errors: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4278/console > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

5 years, 8 months

1
0
0 / 0

[CQ]: 98351,1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 98351,1 (vdsm-jsonrpc-java) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/98351/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/189/

5 years, 8 months

2
1
0 / 0

[CQ]: 9fbdbc1 (ovirt-ansible-vm-infra) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 9fbdbc1 (ovirt-ansible-vm-infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/9fbdbc1add5c0c194b... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4029/

5 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-2697) error before starting tests

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2697: ---------------------------------- we had missing packages last week due to a missing repo. please try to re-run the job > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

5 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-2696) verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status'

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2696: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status' > ---------------------------------------------------------------------------------- > > Key: OVIRT-2696 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Priority: High > Labels: ost_failures > > [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > Project name - ovirt-engine > Branch - ovirt-master > Failed Suite - basic suite > Failed test/failed phase > Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ > Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

5 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-2696) verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status'

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2696: ---------------------------------- this was already resolved: https://gerrit.ovirt.org/#/c/98317/ > verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status' > ---------------------------------------------------------------------------------- > > Key: OVIRT-2696 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Priority: High > Labels: ost_failures > > [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > Project name - ovirt-engine > Branch - ovirt-master > Failed Suite - basic suite > Failed test/failed phase > Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ > Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

5 years, 8 months

1
0
0 / 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 08-03-2019 ] [ 002_bootstrap.verify_add_hosts ]

by Dafna Ron

Hi, We are failing vdsm project on master branch with test 002_bootstrap.verify_add_hosts CQ identified this patch as the root cause: https://gerrit.ovirt.org/#/c/97381/ - virt: In FIPS mode, use SASL auth instead of qemu passwords Can you please take a look? build logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13317/arti... <error> host: 2019-03-07 17:37:38,839-0500 ERROR (MainThread) [vds] Exception raised (vdsmd:159) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 157, in run serve_clients(log) File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 103, in serve_clients from vdsm.clientIF import clientIF # must import after config is read File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 64, in <module> from vdsm.virt import vm File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 81, in <module> from vdsm.virt import saslpasswd2 ImportError: cannot import name saslpasswd2 2019-03-07 17:37:38,841-0500 INFO (MainThread) [vds] Stopping threads (vdsmd:161) 2019-03-07 17:37:38,841-0500 INFO (MainThread) [vds] Stopping <MonitorObserver(mpathlistener, started daemon 139815311881984)> (vdsmd:164) engine: 2019-03-07 17:37:47,780-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [] Command 'G etCapabilitiesAsyncVDSCommand(HostName = lago-basic-suite-master-host-1, VdsIdAndVdsVDSCommandParametersBase:{hostId='5d685bce-ada7-4730-975c-45d30afc0a8b', vds='Host[lago-b asic-suite-master-host-1,5d685bce-ada7-4730-975c-45d30afc0a8b]'})' execution failed: java.net.ConnectException: Connection refused 2019-03-07 17:37:47,780-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: java.net.ConnectException: Connection refused at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:172) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:135) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [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:396) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source) [:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.5.Final. jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) [:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.5.Final.jar:3 .0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-3.0. 5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-3.0. 5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:779) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refreshCapabilities(HostMonitoring.java:189) [vdsbroker.jar:] </error>

5 years, 8 months

2
8
0 / 0

otopi: release branches and change queues

by Yedidyah Bar David

Hi all, I branched yesterday otopi-1.8 to be used for ovirt-4.3, and forgot to patch stdci accordingly. Now pushed the patch [1] (to both master and otopi-1.8 - I realize I do not need it in master, but hopefully this will help me remember patching it in 4.4). What can/should I do to include the otopi-1.8.1 build [2] in the 4.3 change queue? And, related to this, some ideas about how to make stdci more useful for mere developers: 1. Make the change-queue post comments in gerrit patches once it has a result (patch passed change queue X, failed, something else?). I (as always) prefer a bit more information (e.g. a few more comments that might not be that interesting) than not enough (current). We can always refine later. IIRC this was already discussed in the past - any update? 2. Make the current comment "This change was successfully submitted to the change queue(s) for system testing." more informative - include names of change queues and links to relevant pages (builds? not sure, I do not know enough CI). 3. As a side note, I realize that the option names were made case-insensitive and ignore whitespace/dashes/underscores in order to not impose a certain style on the many different projects/maintainers and let them use what they find best for their project. I personally think this was a mistake. If you have to make a choice when naming something, and have a feeling that your opinion might cause noise/objections/etc. in the future, make a quick poll asking what people prefer, and then pick a single name. Having several (many) different names for things makes it much harder later on to _find_ them. It might be too late now to change, because people might already picked different names in practice and we do not want to break their stuff, and that's a pity. But next time, be opinionated, or ask beforehand - not keep the choice. Most computer languages and libraries have single unique names for things, for a reason. [1] https://gerrit.ovirt.org/#/q/I794426ec9212e0a023c3e5f158d0a88fc8e6842c [2] https://gerrit.ovirt.org/98408 -- Didi

5 years, 8 months

2
2
0 / 0

oVirt infra daily report - unstable production jobs - 760

by jenkins＠jenkins.phx.ovirt.org

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/760//artifact/exported... Cheers, Jenkins

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra March 2019