Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #2074
by jenkins@jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/2074/dis...>
------------------------------------------
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-epel-el6-x86_64/ws/>
> 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 31f05cf869f635237eda123c071e91ba51a2a3e6 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 31f05cf869f635237eda123c071e91ba51a2a3e6
Commit message: "Drop mzamazal from basic-suite-master compatibility testing"
> git rev-list --no-walk 31f05cf869f635237eda123c071e91ba51a2a3e6 # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins4448743819578125948.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML
local = self.cachedir + '/repomd.xml'
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda>
cachedir = property(lambda self: self._dirGetAttr('cachedir'))
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr
self.dirSetup()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup
self._dirSetupMkdir_p(dir)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p
raise Errors.RepoError, msg
yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7'
Build step 'Execute shell' marked build as failure
6 years, 4 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#2596 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-pd6rd.
6 years, 4 months
[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by Anton Marchukov (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jir... ]
Anton Marchukov commented on OVIRT-2586:
----------------------------------------
Hello All.
I have restarted the jenkins. I guess we need to investigate what to
do as we are quite a large jenkins shop and there is certainly a limit
on how well it can scale.
Since infra-support is added, the ticket is already created.
Anton.
On 23 November 2018 at 10:09:29, Sandro Bonazzola (sbonazzo(a)redhat.com) wrote:
> 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
>
> sbonazzo(a)redhat.com
>
> _______________________________________________
> Infra mailing list -- infra(a)ovirt.org
> To unsubscribe send an email to infra-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/infra@ovirt.org/message/25QXLHAYU4X...
>
> Jenkins terribly slow and unresponsive
> --------------------------------------
>
> Key: OVIRT-2586
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: sbonazzo
> Assignee: infra
>
> 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#100095)
6 years, 4 months
Jenkins terribly slow and unresponsive
by Sandro Bonazzola
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>
6 years, 4 months
[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-2586:
-------------------------------
Summary: Jenkins terribly slow and unresponsive
Key: OVIRT-2586
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra
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#100095)
6 years, 4 months
[ OST Failure Report ] [ oVirt Master (ovirt-engone) ] [ 21-11-2018 ]
[ check_update_host ]
by Dafna Ron
Hi,
We have a failure in ovirt-master in basic suite for test
check_update_host.
Link and headline of suspected patches:
ansible: Remove duplication of vnc_tls option -
https://gerrit.ovirt.org/#/c/95169/
Link to Job:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267
Link to all logs:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267/arti...
(Relevant) error snippet from the log:
<error>
[dron@dron post-002_bootstrap.py]$ egrep
89d99b74-fa6c-4d1d-a261-fb7ca7fcada2
lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
2018-11-21 13:41:34,209-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get,
params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 9ms
2018-11-21 13:41:34,224-05 INFO
[org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckCommand] (default
task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command:
HostUpgradeCheckCommand internal: false. Entities affected : ID:
ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDSAction group
EDIT_HOST_CONFIGURATION with role type ADMIN
2018-11-21 13:41:34,259-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params:
[ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 13ms
2018-11-21 13:41:34,273-05 INFO
[org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckInternalCommand]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command:
HostUpgradeCheckInternalCommand internal: true. Entities affected : ID:
ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDS
2018-11-21 13:41:34,277-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params:
[ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 4ms
2018-11-21 13:41:34,281-05 DEBUG
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Inventory hosts:
[lago-basic-suite-master-host-0]
2018-11-21 13:41:34,282-05 INFO
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Executing Ansible command:
ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook,
--ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check,
--private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
--inventory=/tmp/ansible-inventory2326258642232337463,
/usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null]
2018-11-21 13:41:37,610-05 INFO
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Ansible playbook command has exited
with value: 2
2018-11-21 13:41:37,611-05 ERROR
[org.ovirt.engine.core.bll.host.HostUpgradeManager]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to run check-update of host
'lago-basic-suite-master-host-0'.
2018-11-21 13:41:37,611-05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to check if updates are
available for host 'lago-basic-suite-master-host-0' with error message
'Failed to run check-update of host 'lago-basic-suite-master-host-0'.'
2018-11-21 13:41:37,616-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] EVENT_ID:
HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates
on host lago-basic-suite-master-host-0 with message 'Failed to run
check-update of host 'lago-basic-suite-master-host-0'.'.
[dron@dron post-002_bootstrap.py]$
</error>
6 years, 4 months