September 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Barak Korren (oVirt JIRA) 18 Sep '18

18 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2504: -------------------------------- Epic Link: OVIRT-2339 > standard CI fails in project_setup phase > ---------------------------------------- > > Key: OVIRT-2504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: docker_cleanup.py > Reporter: Petr Kotas > Assignee: infra > Priority: Highest > > Hi, > the standard CI is failing in project_setup phase. Can you please debug > that? > The issue is somehow related to docker clean up phase. > Example of failing CI is : > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > Unfortunately, the logs are the only thing I can see. From our side, there > is nothing special. > Just normal test run. We did not tune anything. > Thank you, > Best, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Barak Korren (oVirt JIRA) 18 Sep '18

18 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2504: -------------------------------- Priority: Highest (was: Medium) > standard CI fails in project_setup phase > ---------------------------------------- > > Key: OVIRT-2504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: docker_cleanup.py > Reporter: Petr Kotas > Assignee: infra > Priority: Highest > > Hi, > the standard CI is failing in project_setup phase. Can you please debug > that? > The issue is somehow related to docker clean up phase. > Example of failing CI is : > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > Unfortunately, the logs are the only thing I can see. From our side, there > is nothing special. > Just normal test run. We did not tune anything. > Thank you, > Best, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Barak Korren (oVirt JIRA) 18 Sep '18

18 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2504: -------------------------------- Issue Type: Bug (was: By-EMAIL) > standard CI fails in project_setup phase > ---------------------------------------- > > Key: OVIRT-2504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: docker_cleanup.py > Reporter: Petr Kotas > Assignee: infra > > Hi, > the standard CI is failing in project_setup phase. Can you please debug > that? > The issue is somehow related to docker clean up phase. > Example of failing CI is : > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > Unfortunately, the logs are the only thing I can see. From our side, there > is nothing special. > Just normal test run. We did not tune anything. > Thank you, > Best, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Barak Korren (oVirt JIRA) 18 Sep '18

18 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2504: -------------------------------- Component/s: docker_cleanup.py > standard CI fails in project_setup phase > ---------------------------------------- > > Key: OVIRT-2504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: docker_cleanup.py > Reporter: Petr Kotas > Assignee: infra > > Hi, > the standard CI is failing in project_setup phase. Can you please debug > that? > The issue is somehow related to docker clean up phase. > Example of failing CI is : > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > Unfortunately, the logs are the only thing I can see. From our side, there > is nothing special. > Just normal test run. We did not tune anything. > Thank you, > Best, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Barak Korren (oVirt JIRA) 18 Sep '18

18 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2504?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2504: ------------------------------------- [~dbelenky(a)redhat.com] docker-cleanup seems to be timing out talking to Dockerd. Can you have a look? Lets see if we can have a quick and dirty work around in place before we all go on a long PTO > standard CI fails in project_setup phase > ---------------------------------------- > > Key: OVIRT-2504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > the standard CI is failing in project_setup phase. Can you please debug > that? > The issue is somehow related to docker clean up phase. > Example of failing CI is : > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > Unfortunately, the logs are the only thing I can see. From our side, there > is nothing special. > Just normal test run. We did not tune anything. > Thank you, > Best, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[JIRA] (OVIRT-2504) standard CI fails in project_setup phase
by Barak Korren (oVirt JIRA) 18 Sep '18

18 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2504?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2504: ------------------------------------- [~dbelenky(a)redhat.com] docker-cleanup seems to be timing out talking to Dockerd. Can you have a look? Lets see if we can have a quick and dirty work around in place before we all go on a long PTO > standard CI fails in project_setup phase > ---------------------------------------- > > Key: OVIRT-2504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2504 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Kotas > Assignee: infra > > Hi, > the standard CI is failing in project_setup phase. Can you please debug > that? > The issue is somehow related to docker clean up phase. > Example of failing CI is : > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/kubevirt_kubevirt_stan… > Unfortunately, the logs are the only thing I can see. From our side, there > is nothing special. > Just normal test run. We did not tune anything. > Thank you, > Best, > Petr Kotas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0

[CQ]: 6993caa (ovirt-ansible-manageiq) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Sep '18

18 Sep '18

Change 6993caa (ovirt-ansible-manageiq) 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-manageiq/commit/6993caa02dc761e0f874… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3136/

1 0

oVirt infra daily report - unstable production jobs - 586
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

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

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc28-x86_64 #417
by jenkins＠jenkins.phx.ovirt.org 17 Sep '18

17 Sep '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc28-x86_64/41…> ------------------------------------------ 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-fedora-base-fc28-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 f9508e32027645ea57bcfec09dafe628fbb06677 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f9508e32027645ea57bcfec09dafe628fbb06677 Commit message: "standard_pipelines: add nmstate project" > git rev-list --no-walk f9508e32027645ea57bcfec09dafe628fbb06677 # timeout=10 [system-sync_mirrors-fedora-base-fc28-x86_64] $ /bin/bash -xe /tmp/jenkins5577468338365067102.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc28 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/fedora-base-fc28 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/fedora-base-fc28' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2463) http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
by Dafna Ron (oVirt JIRA) 17 Sep '18

17 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2463?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2463: ---------------------------------- [~eyonasi(a)redhat.com] [~ybardavi] can we close this? > http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2463 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2463 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures > > Project name: > ovirt-ansible-engine-setup > Branch: > master > Failed Suite: > upgrade-from-release-suite.el7.x86_64 > Failed test/failed phase: > 001_upgrade_engine.test_initialize_engine > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/ > Link to first reported failed patch: > ??? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

1 0