- Infra - oVirt List Archives

[CQ]: 97032, 8 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 Aug '19

14 Aug '19

Change 97032,8 (ovirt-engine-ui-extensions) 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/97032/8 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1840/

1 0

[CQ]: 97032, 8 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests
by oVirt Jenkins 14 Aug '19

14 Aug '19

Change 97032,8 (ovirt-engine-ui-extensions) 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/97032/8 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15401/

1 0

[JIRA] (OVIRT-2776) 51 jobs in the queue, all workers are idle
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #835
by jenkins＠jenkins.phx.ovirt.org 14 Aug '19

14 Aug '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace /home/jenkins/workspace/system-sync_mirrors-fedora-updates-fc29-x86_64 No credentials specified > 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 03d6b67f33d57527ef7d0f83470408546ec1fcf8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 03d6b67f33d57527ef7d0f83470408546ec1fcf8 Commit message: "ovirt-log-collector: drop 4.2 jobs" > git rev-list --no-walk 03d6b67f33d57527ef7d0f83470408546ec1fcf8 # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins5036711870660329167.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc29 yum + local repo_name=fedora-updates-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc29 /var/www/html/repos/yum/fedora-updates-fc29/base + check_yum_sync_needed fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc29/base --norepopath --newest-only --urls --quiet FATAL: command execution failed java.io.IOException at hudson.remoting.Channel.close(Channel.java:1449) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:844) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:811) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:89) at jenkins.model.Jenkins.access$2100(Jenkins.java:309) at jenkins.model.Jenkins$19.run(Jenkins.java:3425) at hudson.model.Queue._withLock(Queue.java:1379) at hudson.model.Queue.withLock(Queue.java:1256) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3419) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3297) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:379) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:965) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:566) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:942) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:376) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1503) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1467) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1009) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:288) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:149) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:170) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:461) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:310) at winstone.ShutdownHook.run(ShutdownHook.java:25) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on mirrors.phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:950) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) at com.sun.proxy.$Proxy113.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1150) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1142) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) FATAL: Unable to delete script file /tmp/jenkins5036711870660329167.sh java.io.IOException at hudson.remoting.Channel.close(Channel.java:1449) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:844) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:811) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:89) at jenkins.model.Jenkins.access$2100(Jenkins.java:309) at jenkins.model.Jenkins$19.run(Jenkins.java:3425) at hudson.model.Queue._withLock(Queue.java:1379) at hudson.model.Queue.withLock(Queue.java:1256) at jenkins.model.Jenkins._cleanUpDisconnectComputers(Jenkins.java:3419) at jenkins.model.Jenkins.cleanUp(Jenkins.java:3297) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:379) at org.eclipse.jetty.server.handler.ContextHandler.callContextDestroyed(ContextHandler.java:965) at org.eclipse.jetty.servlet.ServletContextHandler.callContextDestroyed(ServletContextHandler.java:566) at org.eclipse.jetty.server.handler.ContextHandler.stopContext(ContextHandler.java:942) at org.eclipse.jetty.servlet.ServletContextHandler.stopContext(ServletContextHandler.java:376) at org.eclipse.jetty.webapp.WebAppContext.stopWebapp(WebAppContext.java:1503) at org.eclipse.jetty.webapp.WebAppContext.stopContext(WebAppContext.java:1467) at org.eclipse.jetty.server.handler.ContextHandler.doStop(ContextHandler.java:1009) at org.eclipse.jetty.servlet.ServletContextHandler.doStop(ServletContextHandler.java:288) at org.eclipse.jetty.webapp.WebAppContext.doStop(WebAppContext.java:569) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:149) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:170) at org.eclipse.jetty.server.handler.AbstractHandler.doStop(AbstractHandler.java:124) at org.eclipse.jetty.server.Server.doStop(Server.java:461) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) at winstone.Launcher.shutdown(Launcher.java:310) at winstone.ShutdownHook.run(ShutdownHook.java:25) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on mirrors.phx.ovirt.org failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:950) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.delete(FilePath.java:1540) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute shell' marked build as failure

1 0

[JIRA] (OVIRT-2776) 51 jobs in the queue, all workers are idle
by Nir Soffer (oVirt JIRA) 14 Aug '19

14 Aug '19

1 0

[JIRA] (OVIRT-2774) system_update_puppet job does not work properly
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2774?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2774: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > system_update_puppet job does not work properly > ----------------------------------------------- > > Key: OVIRT-2774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Highest > > The job performs incorrect updates to the puppet repo. This seems to just have caused a Jenkins restart and downgraded its version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[CQ]: 102517,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Aug '19

14 Aug '19

Change 102517,3 (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/102517/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15398/

1 0

[CQ]: 102506,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Aug '19

14 Aug '19

Change 102506,5 (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/102506/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15397/

1 0

[CQ]: 102570,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 14 Aug '19

14 Aug '19

Change 102570,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/102570/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15395/

1 0

[JIRA] (OVIRT-2774) system_update_puppet job does not work properly
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2774?page=com.atlassian.jira.… ] Evgheni Dereveanchin edited comment on OVIRT-2774 at 8/14/19 12:12 PM: ----------------------------------------------------------------------- Looking at the foreman: grep jenkins_ver /etc/puppet/environments/production/hieradata/common.yaml ovirt_jenkins::jenkins_ver: 2.164.2-1.1 ls -l /etc/puppet/environments/production/hieradata/common.yaml rw-rw-r-. 1 puppet-repos puppet-repos 10586 Aug 1 15:05 /etc/puppet/environments/production/hieradata/common.yaml At the same time from the logs of the last job all looks fine: [https://jenkins.ovirt.org/job/system_update_puppet/176/console|https://jenk…] Looking into {{/var/lib/data/jenkins/jobs/system_update_puppet/workspace}} on the master the hieradata file is correct and contains Jenkins version 2.176.1 as needed. [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] do you know how exactly system_update_puppet invokes r10k? The job config only lists “ssh“ as the build step and on the foreman the shell of the puppet-repos user is plain bash so it doesn’t seem to run any hardcoded commands upon login. This stops me from understanding where the changes are lost. was (Author: ederevea): Looking at the foreman: {{# grep jenkins_ver /etc/puppet/environments/production/hieradata/common.yaml }} {{ovirt_jenkins::jenkins_ver: 2.164.2-1.1}} {{# ls -l /etc/puppet/environments/production/hieradata/common.yaml }} {{-rw-rw-r--. 1 puppet-repos puppet-repos 10586 Aug 1 15:05 /etc/puppet/environments/production/hieradata/common.yaml}} At the same time from the logs of the last job all looks fine: [https://jenkins.ovirt.org/job/system_update_puppet/176/console|https://jenk…] Looking into {{/var/lib/data/jenkins/jobs/system_update_puppet/workspace}} on the master the hieradata file is correct and contains Jenkins version 2.176.1 as needed. [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] do you know how exactly system_update_puppet invokes r10k? The job config only lists “ssh“ as the build step and on the foreman the shell of the puppet-repos user is plain bash so it doesn’t seem to run any hardcoded commands upon login. This stops me from understanding where the changes are lost. > system_update_puppet job does not work properly > ----------------------------------------------- > > Key: OVIRT-2774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Highest > > The job performs incorrect updates to the puppet repo. This seems to just have caused a Jenkins restart and downgraded its version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[JIRA] (OVIRT-2774) system_update_puppet job does not work properly
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2774?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2774: --------------------------------------------- Looking at the foreman: {{# grep jenkins_ver /etc/puppet/environments/production/hieradata/common.yaml }} {{ovirt_jenkins::jenkins_ver: 2.164.2-1.1}} {{# ls -l /etc/puppet/environments/production/hieradata/common.yaml }} {{-rw-rw-r--. 1 puppet-repos puppet-repos 10586 Aug 1 15:05 /etc/puppet/environments/production/hieradata/common.yaml}} At the same time from the logs of the last job all looks fine: [https://jenkins.ovirt.org/job/system_update_puppet/176/console|https://jenk…] Looking into {{/var/lib/data/jenkins/jobs/system_update_puppet/workspace}} on the master the hieradata file is correct and contains Jenkins version 2.176.1 as needed. [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] do you know how exactly system_update_puppet invokes r10k? The job config only lists “ssh“ as the build step and on the foreman the shell of the puppet-repos user is plain bash so it doesn’t seem to run any hardcoded commands upon login. This stops me from understanding where the changes are lost. > system_update_puppet job does not work properly > ----------------------------------------------- > > Key: OVIRT-2774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Highest > > The job performs incorrect updates to the puppet repo. This seems to just have caused a Jenkins restart and downgraded its version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[JIRA] (OVIRT-2775) Jenkins unexpected restart 2019.08.14
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2775?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2775: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins unexpected restart 2019.08.14 > ------------------------------------- > > Key: OVIRT-2775 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2775 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins restarted, looks like it was caused by puppet that also downgraded versions: > /Stage[main]/Jenkins::Package/Package[jenkins]/ensure ensure changed '2.176.1-1.1' to '2.164.2-1.1' > Logged OVIRT-2774 to see why the puppet issue happened but for now we need to upgrade Jenkins back and put it into operation -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[JIRA] (OVIRT-2775) Jenkins unexpected restart 2019.08.14
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

Evgheni Dereveanchin created OVIRT-2775: ------------------------------------------- Summary: Jenkins unexpected restart 2019.08.14 Key: OVIRT-2775 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2775 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra Jenkins restarted, looks like it was caused by puppet that also downgraded versions: /Stage[main]/Jenkins::Package/Package[jenkins]/ensure ensure changed '2.176.1-1.1' to '2.164.2-1.1' Logged OVIRT-2774 to see why the puppet issue happened but for now we need to upgrade Jenkins back and put it into operation -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[JIRA] (OVIRT-2774) system_update_puppet job does not work properly
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2774?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2774: --------------------------------------------- I’ve merged [https://gerrit.ovirt.org/#/c/100422/|https://gerrit.ovirt.org/#/c/100422/] that only changed resources-related configs and noted that Jenkins restarted. In Foreman reports I see the following: |/Stage\[main]/Jenkins::Package/Package\[jenkins]/ensure|ensure changed '2.176.1-1.1' to '2.164.2-1.1'| Meaning that some older version got pushed to foreman and package versions got downgraded > system_update_puppet job does not work properly > ----------------------------------------------- > > Key: OVIRT-2774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Highest > > The job performs incorrect updates to the puppet repo. This seems to just have caused a Jenkins restart and downgraded its version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[JIRA] (OVIRT-2774) system_update_puppet job does not work properly
by Evgheni Dereveanchin (oVirt JIRA) 14 Aug '19

14 Aug '19

Evgheni Dereveanchin created OVIRT-2774: ------------------------------------------- Summary: system_update_puppet job does not work properly Key: OVIRT-2774 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2774 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: Highest The job performs incorrect updates to the puppet repo. This seems to just have caused a Jenkins restart and downgraded its version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[CQ]: 102600,2 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 Aug '19

14 Aug '19

Change 102600,2 (ovirt-engine) 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/102600/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1837/

1 0

oVirt infra daily report - unstable production jobs - 916
by jenkins＠jenkins.phx.ovirt.org 14 Aug '19

14 Aug '19

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/916//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99031,13 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 13 Aug '19

13 Aug '19

Change 99031,13 (cockpit-ovirt) 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/99031/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15381/

1 0

[CQ]: 102596, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Aug '19

13 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102596,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95157,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95157,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102596/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95157/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15375/

1 0

[JIRA] (OVIRT-2772) on-ghpush jobs not triggered for wix-toolset-binaries
by Anton Marchukov (oVirt JIRA) 13 Aug '19

13 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2772?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2772: -------------------------------------- Assignee: Daniel Belenky (was: infra) > on-ghpush jobs not triggered for wix-toolset-binaries > ----------------------------------------------------- > > Key: OVIRT-2772 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2772 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: Daniel Belenky > > PRs merged in https://github.com/oVirt/wix-toolset-binaries are not > triggering > https://jenkins.ovirt.org/job/oVirt_wix-toolset-binaries_standard-on-ghpush/ > can you please check what's missing? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[CQ]: 101392,33 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 13 Aug '19

13 Aug '19

Change 101392,33 (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/101392/33 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15374/

1 0

oVirt infra daily report - unstable production jobs - 915
by jenkins＠jenkins.phx.ovirt.org 13 Aug '19

13 Aug '19

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/915//artifact/exported-a… Cheers, Jenkins

1 0

[ovirt-devel] [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import]
by Dusan Fodor 12 Aug '19

12 Aug '19

Hi, we have failures in test verify glance import appearing in both 4.3 and master. Api call to get the disk status times out. Example of failed job can be seen here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… Can you please take a look?

3 3

[CQ]: 102537, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Aug '19

12 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102537,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95157,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95157,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102537/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95157/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15366/

1 0

[CQ]: 102575, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Aug '19

12 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102575,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95157,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95157,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102575/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95157/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15365/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2737
by jenkins＠jenkins.phx.ovirt.org 12 Aug '19

12 Aug '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/59/95959/1:test --prune > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins7477368550401470113.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1468, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 777, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 760, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 738, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 715, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/fedora-base-fc29/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/fedora-base-fc29/gen' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 102473, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Aug '19

12 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102473,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95157,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95157,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102473/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95157/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15362/

1 0

oVirt infra daily report - unstable production jobs - 914
by jenkins＠jenkins.phx.ovirt.org 12 Aug '19

12 Aug '19

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/914//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 102098,29 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 102098,29 (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/102098/29 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15360/

1 0

[JIRA] (OVIRT-2773) verify_glance_import test failing in both 4.3 and master suites
by Eyal Edri (oVirt JIRA) 11 Aug '19

11 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2773?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2773: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] looked into it today and its most likely an error to download a large image of 800MB over the bad network we have outside PHX, now affecting also our connecting with OSAS and not just with AWS. For now, we’ll revert to use the old Glance which is in PHX until we’ll fix the networking problem. > verify_glance_import test failing in both 4.3 and master suites > --------------------------------------------------------------- > > Key: OVIRT-2773 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2773 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > > Example of failed job can be found here: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… > Thread [ovirt-devel] [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] was opened for investigation -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[ovirt-devel] [Ovirt] [CQ weekly status] [10-08-2019]
by Dusan Fodor 11 Aug '19

11 Aug '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#3) No failure during this week. *CQ-4.3*: RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] *CQ-Master:* RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt .org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

2 1

[CQ]: 101095, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Aug '19

11 Aug '19

A system test invoked by the "ovirt-master" change queue including change 101095,10 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95157,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95157,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101095/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95157/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15357/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #1 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/1/ Build Name: #1 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 2

[CQ]: 88eb306 (ovirt-ansible-disaster-recovery) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 88eb306 (ovirt-ansible-disaster-recovery) 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://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/88eb3068759… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1810/

1 0

[CQ]: 88eb306 (ovirt-ansible-disaster-recovery) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 88eb306 (ovirt-ansible-disaster-recovery) 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-disaster-recovery/commit/88eb3068759… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4700/

1 0

[CQ]: 88eb306 (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 88eb306 (ovirt-ansible-disaster-recovery) 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://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/88eb3068759… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15354/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 157 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/157/ Build Number: 157 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #157 [Galit Rosenthal] Remove ansible exclude ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.verify_glance_import_43 Error Message: False != True after 600 seconds Stack Trace: Traceback (most recent call last): 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 runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 69, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 1130, in verify_glance_import lambda: api.disks.get(disk_name).status.state == 'ok', File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 600 seconds

1 2

oVirt infra daily report - unstable production jobs - 913
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '19

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/913//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2773) verify_glance_import test failing in both 4.3 and master suites
by Dusan Fodor (oVirt JIRA) 10 Aug '19

10 Aug '19

Dusan Fodor created OVIRT-2773: ---------------------------------- Summary: verify_glance_import test failing in both 4.3 and master suites Key: OVIRT-2773 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2773 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dusan Fodor Assignee: infra Example of failed job can be found here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… Thread [ovirt-devel] [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] was opened for investigation -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[CQ]: 5191b28 (ovirt-ansible-image-template) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Aug '19

10 Aug '19

A system test invoked by the "ovirt-master" change queue including change 5191b28 (ovirt-ansible-image-template) failed. However, this change seems not to be the root cause for this failure. Change e5d0b24 (ovirt-ansible-image- template) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change e5d0b24 (ovirt-ansible-image- template) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-ansible-image-template/commit/5191b28583c183… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-image-template/commit/e5d0b2427fd0b8… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15352/

1 0

[CQ]: 5191b28 (ovirt-ansible-image-template) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 Aug '19

10 Aug '19

Change 5191b28 (ovirt-ansible-image-template) 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://github.com/oVirt/ovirt-ansible-image-template/commit/5191b28583c183… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1808/

1 0

oVirt infra daily report - unstable production jobs - 912
by jenkins＠jenkins.phx.ovirt.org 10 Aug '19

10 Aug '19

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/912//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 102474, 2 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Aug '19

09 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102474,2 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 101396,1 (ovirt-host) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101396,1 (ovirt-host) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102474/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101396/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15349/

1 0

[CQ]: 102523,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 09 Aug '19

09 Aug '19

Change 102523,3 (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/102523/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15347/

1 0

Re: [ovirt-devel] CI: vdsm-standard-check-patch fails
by Eyal Edri 09 Aug '19

09 Aug '19

This was reported already and AFAIK its a network issue between AWS and PHX which is still being investigated. Evgheni, any insights or update on the issue? should we involve debugging from amazon side? On Sun, Aug 4, 2019 at 4:46 PM Amit Bawer <abawer(a)redhat.com> wrote: > Hi, > CI seems to fail constantly for unavailable remote gerrit repository. > Example can be seen here: > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/9415/console > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/AHPHUZAABAQNW… > -- Eyal edri He / Him / His MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)

6 19

[CQ]: 102419, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Aug '19

09 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102419,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95157,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95157,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102419/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95157/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15343/

1 0

[CQ]: 102205, 4 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Aug '19

09 Aug '19

A system test invoked by the "ovirt-master" change queue including change 102205,4 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 102200,6 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102200,6 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102205/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102200/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15339/

1 0

[JIRA] (OVIRT-2586) Memory leak in Jenkins SSE Gateway plugin
by Evgheni Dereveanchin (oVirt JIRA) 09 Aug '19

09 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2586: ---------------------------------------- Resolution: Fixed Status: Done (was: Blocked) SSE Gateway plugin upgraded to a version that is reported to fix the mem leak. Marking the ticket as resolved. > Memory leak in Jenkins SSE Gateway plugin > ----------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Sandro Bonazzola > Assignee: Evgheni Dereveanchin > Attachments: usedMemory_year.png > > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[JIRA] (OVIRT-2636) Tests failed because global_setup.sh failed
by Evgheni Dereveanchin (oVirt JIRA) 09 Aug '19

09 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2636?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2636: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Tests failed because global_setup.sh failed > ------------------------------------------- > > Key: OVIRT-2636 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2636 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > Not sure why global setup failed: > + [[ ! -O /home/jenkins/.ssh ]] > + [[ ! -G /home/jenkins/.ssh ]] > + verify_set_permissions 700 /home/jenkins/.ssh > + local target_permissions=700 > + local path_to_set=/home/jenkins/.ssh > ++ stat -c %a /home/jenkins/.ssh > + local access=700 > + [[ 700 != \7\0\0 ]] > + return 0 > + [[ -f /home/jenkins/.ssh/known_hosts ]] > + verify_set_ownership /home/jenkins/.ssh/known_hosts > + local path_to_set=/home/jenkins/.ssh/known_hosts > ++ id -un > + local owner=jenkins > ++ id -gn > + local group=jenkins > + [[ ! -O /home/jenkins/.ssh/known_hosts ]] > + [[ ! -G /home/jenkins/.ssh/known_hosts ]] > + verify_set_permissions 644 /home/jenkins/.ssh/known_hosts > + local target_permissions=644 > + local path_to_set=/home/jenkins/.ssh/known_hosts > ++ stat -c %a /home/jenkins/.ssh/known_hosts > + local access=644 > + [[ 644 != \6\4\4 ]] > + return 0 > + return 0 > + true > + log ERROR Aborting. > Build: > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[CQ]: 102504, 1 (ovirt-engine-metrics) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 Aug '19

09 Aug '19

Change 102504,1 (ovirt-engine-metrics) 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/102504/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1804/

1 0