July 2019 - Infra - Ovirt List Archives

Jenkins build fails to clone gerrit repo

by Vojtech Juranek

Hi, lots of Jenkin jobs fail as they cannot fetch git repo from gerrit: 17:35:32 Fetching upstream changes from https://gerrit.ovirt.org/vdsm 17:35:32 > git --version # timeout=10 17:35:32 > git fetch --tags --progress https://gerrit.ovirt.org/vdsm +refs/heads/*:refs/remotes/origin/* 17:36:38 ERROR: Error cloning remote repo 'origin' 17:36:38 hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/vdsm +refs/heads/*:refs/remotes/origin/*" returned status code 128: 17:36:38 stdout: 17:36:38 stderr: error: RPC failed; result=22, HTTP code = 502 17:36:38 fatal: The remote end hung up unexpectedly see e.g. [1, 2, 3] for more details, to name couple of examples. Can someone take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8277/console [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8285/console [3] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8291/console

5 years, 4 months

2
1
0 / 0

oVirt infra daily report - unstable production jobs - 892

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

5 years, 4 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 891

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

5 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2757) Re: Jenkins Developer group

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2757?page=com.atlassian.jir... ] Anton Marchukov updated OVIRT-2757: ----------------------------------- Status: In Progress (was: To Do) > Re: Jenkins Developer group > --------------------------- > > Key: OVIRT-2757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2757 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > Adding infra-support to generate a ticket. > > On 16 Jul 2019, at 13:34, Andrej Cernek <acernek(a)redhat.com> wrote: > > > > Hi, > > I am intern in the oVirt networking team, but I am missing the Gerrit/ManualTrigger permission. Could you add me to the Developer group? My user ID is acernek. > > Thank you > > _______________________________________________ > > 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/O4RERPUWYX2... > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

5 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2757) Re: Jenkins Developer group

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2757?page=com.atlassian.jir... ] Anton Marchukov updated OVIRT-2757: ----------------------------------- Issue Type: Task (was: By-EMAIL) > Re: Jenkins Developer group > --------------------------- > > Key: OVIRT-2757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2757 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > Adding infra-support to generate a ticket. > > On 16 Jul 2019, at 13:34, Andrej Cernek <acernek(a)redhat.com> wrote: > > > > Hi, > > I am intern in the oVirt networking team, but I am missing the Gerrit/ManualTrigger permission. Could you add me to the Developer group? My user ID is acernek. > > Thank you > > _______________________________________________ > > 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/O4RERPUWYX2... > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

5 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2757) Re: Jenkins Developer group

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2757?page=com.atlassian.jir... ] Anton Marchukov reassigned OVIRT-2757: -------------------------------------- Assignee: Anton Marchukov (was: infra) > Re: Jenkins Developer group > --------------------------- > > Key: OVIRT-2757 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2757 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > Adding infra-support to generate a ticket. > > On 16 Jul 2019, at 13:34, Andrej Cernek <acernek(a)redhat.com> wrote: > > > > Hi, > > I am intern in the oVirt networking team, but I am missing the Gerrit/ManualTrigger permission. Could you add me to the Developer group? My user ID is acernek. > > Thank you > > _______________________________________________ > > 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/O4RERPUWYX2... > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

5 years, 4 months

1
0
0 / 0

Jenkins Developer group

by Andrej Cernek

Hi, I am intern in the oVirt networking team, but I am missing the Gerrit/ManualTrigger permission. Could you add me to the Developer group? My user ID is acernek. Thank you

5 years, 4 months

2
2
0 / 0

[ovirt-devel] [Ovirt] [CQ weekly status] [19-07-2019]

by Dusan Fodor

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 (#1) Last failure was on 02-07 for ovirt-provider-ovm due to failed test: 098_ovirt_provider_ovn.use_ovn_provide. This was a code regression and which was fixed. *CQ-4.3*: GREEN (#1) Last failure was on 12-07 for ovirt-provider-ovm due to failed build-artifacts which was caused due to a mirror issue. *CQ-Master:* GREEN (#1) Last failure was on 16-07 for ovirt-engine due failure in build-artifacts, which was caused by gerrit issue, which is under investigation by Evgheni. 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-... [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change... [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan... Happy 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/YCNCKRK3G4E...

5 years, 4 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 890

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

5 years, 4 months

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #2884

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...> ------------------------------------------ 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_6...> 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 9b5f5fcdb80b40f2e5c7dfdb384c54ff533eeb29 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9b5f5fcdb80b40f2e5c7dfdb384c54ff533eeb29 Commit message: "gate: Make tests list visible in BlueOcean" > git rev-list --no-walk 9b5f5fcdb80b40f2e5c7dfdb384c54ff533eeb29 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1188969467314769647.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 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 centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-el7 + 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 centos-updates-el7 yum + local repo_name=centos-updates-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-updates-el7 /var/www/html/repos/yum/centos-updates-el7/base + check_yum_sync_needed centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-updates-el7 + 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/centos-updates-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-updates-el7 ++ 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=centos-updates-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-updates-el7/base --norepopath --newest-only --urls --quiet 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 1482, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1259, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1042, in _getFile raise e yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from mock-copr-fc30: [Errno 256] No more mirrors to try. https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" https://copr-be.cloud.fedoraproject.org/results/@mock/mock/fedora-30-x86_...: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" + reposync_out= Build step 'Execute shell' marked build as failure

5 years, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2019