- Infra - oVirt List Archives

[JIRA] (OVIRT-2601) replace FC27 CI slaves with FC29
by Evgheni Dereveanchin (oVirt JIRA) 28 Nov '18

28 Nov '18

Evgheni Dereveanchin created OVIRT-2601: ------------------------------------------- Summary: replace FC27 CI slaves with FC29 Key: OVIRT-2601 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2601 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Fedora 27 is EOL plus currently deployed systems have a UID bug so they're offline. This ticket is to track their removal and replacement by Fedora 29 systems similarly spawned from Glance templates. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2600) add monitoring to OpenShift
by Evgheni Dereveanchin (oVirt JIRA) 28 Nov '18

28 Nov '18

Evgheni Dereveanchin created OVIRT-2600: ------------------------------------------- Summary: add monitoring to OpenShift Key: OVIRT-2600 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2600 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra We use OpenShift for CI so we need to monitor health of the masters along with node availability and other parameters if possible to get alerted if something starts failing. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2599) Investigate sync between JIRA cloud to JIRA server
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

Eyal Edri created OVIRT-2599: -------------------------------- Summary: Investigate sync between JIRA cloud to JIRA server Key: OVIRT-2599 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2599 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Eyal Edri Assignee: infra We would like to converge on using a single JIRA board to show all our issues. There are some solution available, more info the following links; https://community.atlassian.com/t5/Jira-questions/Sync-between-JIRA-Cloud-a… from that blog: https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira… https://confluence.atlassian.com/jiracoreserver073/linking-issues-861257339… https://confluence.atlassian.com/applinks/application-links-documentation-1… https://www.connectall.com/ https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira… There are other options, shown up on a quick search. Once we find a reasonable plugin, we can ask PnT to purchase and install it on the d/s instance. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2188) Investigate Sync of GitHub issues into JIRA
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2188?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2188: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Investigate Sync of GitHub issues into JIRA > ------------------------------------------- > > Key: OVIRT-2188 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2188 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Lago > Reporter: Eyal Edri > Assignee: infra > > As a Lago maintainer and part of the oVirt infra team, I would like to track all my GitHub issues together > with my other tasks for OST in one place, which is the oVirt JIRA. > There are a few options to check for this purpose: > 1. https://www.pagure.io/sync-to-jira -> a project which was written by Ralph Bean from Red Hat > 2. Add-On to JIRA - we need to look for an add-on that gives free access to OpenSource projects, same way we got the JIRA instance for oVirt for free. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2188) Investigate Sync of GitHub issues into JIRA
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2188?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2188: ---------------------------------- There isn't official solution for it, but we got access to a private system from Ralph Bean to use for syncing between GitHub to downstream JIRA, so we'll it if needed. > Investigate Sync of GitHub issues into JIRA > ------------------------------------------- > > Key: OVIRT-2188 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2188 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Lago > Reporter: Eyal Edri > Assignee: infra > > As a Lago maintainer and part of the oVirt infra team, I would like to track all my GitHub issues together > with my other tasks for OST in one place, which is the oVirt JIRA. > There are a few options to check for this purpose: > 1. https://www.pagure.io/sync-to-jira -> a project which was written by Ralph Bean from Red Hat > 2. Add-On to JIRA - we need to look for an add-on that gives free access to OpenSource projects, same way we got the JIRA instance for oVirt for free. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95764,2 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 Nov '18

28 Nov '18

Change 95764,2 (vdsm) 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://gerrit.ovirt.org/#/c/95764/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3556/

1 0

[JIRA] (OVIRT-2598) Reducing email notifications to infra ML
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2598?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2598: ---------------------------------- git clone jenkins repo cd jobs/confs/projects git grep infra(a)ovirt.org defaults.yaml: email-to: 'infra(a)ovirt.org' ovirt-appliance/ovirt-appliance.yaml: email-to: 'infra(a)ovirt.org, yturgema(a)redhat.com' ovirt-node-ng/ovirt-node-ng.yaml: email-to: 'infra(a)ovirt.org, yturgema(a)redhat.com' ovirt-node-ng/ovirt-node-ng.yaml: email-to: 'infra(a)ovirt.org, yturgema(a)redhat.com' ovirt/change-queues.yaml: email-recipients: 'infra(a)ovirt.org' ovirt/system-tests.yaml: email-to: infra(a)ovirt.org system/system_backup.yaml: mail_to: infra(a)ovirt.org system/system_jobs.yaml: recipients: 'infra(a)ovirt.org' > Reducing email notifications to infra ML > ---------------------------------------- > > Key: OVIRT-2598 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2598 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Liora Milbaum > Assignee: infra > > At the moment, there are email notifications sent to infra ML which are not required. Those can be dropped from the yaml. > For example (according to [~eedri]: > Build-artifacts jobs shouldn't email infra(a)ovirt.org. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2598) Reducing email notifications to infra ML
by Liora Milbaum (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2598?page=com.atlassian.jira.… ] Liora Milbaum commented on OVIRT-2598: -------------------------------------- I get them as part of the infra ML > Reducing email notifications to infra ML > ---------------------------------------- > > Key: OVIRT-2598 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2598 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Liora Milbaum > Assignee: infra > > At the moment, there are email notifications sent to infra ML which are not required. Those can be dropped from the yaml. > For example (according to [~eedri]: > Build-artifacts jobs shouldn't email infra(a)ovirt.org. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2598) Reducing email notifications to infra ML
by Barak Korren (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2598?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2598: ------------------------------------- Can you be specific? Which emails? Build-artifacts jobs for example do not send emails anywhere... > Reducing email notifications to infra ML > ---------------------------------------- > > Key: OVIRT-2598 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2598 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Liora Milbaum > Assignee: infra > > At the moment, there are email notifications sent to infra ML which are not required. Those can be dropped from the yaml. > For example (according to [~eedri]: > Build-artifacts jobs shouldn't email infra(a)ovirt.org. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95794, 1 (ovirt-hosted-engine-ha) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 Nov '18

28 Nov '18

Change 95794,1 (ovirt-hosted-engine-ha) 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://gerrit.ovirt.org/#/c/95794/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3554/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

Failed to run project_setup.sh for: #2658 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-65026.

1 0

[JIRA] (OVIRT-2598) Reducing email notifications to infra ML
by Liora Milbaum (oVirt JIRA) 28 Nov '18

28 Nov '18

Liora Milbaum created OVIRT-2598: ------------------------------------ Summary: Reducing email notifications to infra ML Key: OVIRT-2598 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2598 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Liora Milbaum Assignee: infra At the moment, there are email notifications sent to infra ML which are not required. Those can be dropped from the yaml. For example (according to [~eedri]: Build-artifacts jobs shouldn't email infra(a)ovirt.org. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

Failed to run project_setup.sh for: #2655 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-jl76p.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

Failed to run project_setup.sh for: #2655 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-nnr68.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

Failed to run project_setup.sh for: #2655 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-61xr7.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

Failed to run project_setup.sh for: #2653 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-spk3b.

1 0

[CQ]: 95749,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 Nov '18

28 Nov '18

Change 95749,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/95749/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3552/

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2594: ---------------------------------- I took off all the fc27 slaves for now. > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2594: ---------------------------------- you're right, found it later, took the slave offline. > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Ehud Yonasi (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2594: ------------------------------------ It was a fc27 slave after all: 09:32:36 [check-patch.el7.x86_64] Running on vm0162.workers-phx.ovirt.org in /home/jenkins/workspace/vdsm_standard-check-patch Maybe we will disconnect them meanwhile? > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Eyal Edri (oVirt JIRA) 28 Nov '18

28 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2594: ---------------------------------- [~bkorren(a)redhat.com] this one failed on el7 slave, so maybe its not related to fc27? > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2597) Two failures on reposync for tested repo
by Dafna Ron (oVirt JIRA) 28 Nov '18

28 Nov '18

Dafna Ron created OVIRT-2597: -------------------------------- Summary: Two failures on reposync for tested repo Key: OVIRT-2597 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2597 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We had two failures on master last night with {noformat} 23:45:59 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. {noformat} Full error: https://pastebin.com/weBAa8ZD Last failed build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11707/consol… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95660,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 28 Nov '18

28 Nov '18

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

2 1

[CQ]: 95760,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 28 Nov '18

28 Nov '18

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

2 1

[JIRA] (OVIRT-2596) Dropping whitelist from reposync
by Dafna Ron (oVirt JIRA) 28 Nov '18

28 Nov '18

Dafna Ron created OVIRT-2596: -------------------------------- Summary: Dropping whitelist from reposync Key: OVIRT-2596 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2596 Project: oVirt - virtualization made easy Issue Type: Epic Reporter: Dafna Ron Assignee: infra Priority: High We have been having the automatic reposync tool run and packages which should be downloading from a specific repo are changing location. We need to go over reposync and simplify the whitelist. Use the exclude list + reduce as much as possible the include list (especially on small repos) so that we do not have to deal with packages changing location so much. Since we have several reposync files and we need to make sure removing whitelist packages will not increase our run times, I opened it as an epic and will open specific tickets per tasks. Eyal started a couple of patches: [1] https://gerrit.ovirt.org/#/q/topic:drop_whitelist_small_repos+(status:open+… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #1948
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ 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-kvm-common-el7-x86_…> > 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 b75848a829f6096faa2982c7f1f65a28970d2a8b (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b75848a829f6096faa2982c7f1f65a28970d2a8b Commit message: "container: shutdown if jnlp agent failed 3 times" > git rev-list --no-walk b75848a829f6096faa2982c7f1f65a28970d2a8b # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins958790176175838037.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 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-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' Build step 'Execute shell' marked build as failure

1 1

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #52
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/52…> ------------------------------------------ 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-fc29-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 b75848a829f6096faa2982c7f1f65a28970d2a8b (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b75848a829f6096faa2982c7f1f65a28970d2a8b Commit message: "container: shutdown if jnlp agent failed 3 times" > git rev-list --no-walk b75848a829f6096faa2982c7f1f65a28970d2a8b # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins6066688200241379761.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 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-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 95749,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 Nov '18

28 Nov '18

Change 95749,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/95749/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3550/

1 0

oVirt infra daily report - unstable production jobs - 657
by jenkins＠jenkins.phx.ovirt.org 28 Nov '18

28 Nov '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/657//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 95794, 1 (ovirt-hosted-engine-ha) failed "ovirt-4.2" system tests
by oVirt Jenkins 27 Nov '18

27 Nov '18

Change 95794,1 (ovirt-hosted-engine-ha) 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://gerrit.ovirt.org/#/c/95794/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3545/

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Nir Soffer (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2594: ----------------------------------- Another failure: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/243/ On Tue, Nov 27, 2018 at 1:38 PM Eyal Edri (oVirt JIRA) < > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Eyal Edri (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2594: ---------------------------------- There are quite a few fc27 slaves - http://jenkins.ovirt.org/label/fc27/ Let's verify that indeed all of them are causing issues before removing them and causing lack of resources. > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

2 1

[JIRA] (OVIRT-2578) failures in ovirt-4.2 for 2 projects on iscsi disk space
by Evgheni Dereveanchin (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2578?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2578: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > failures in ovirt-4.2 for 2 projects on iscsi disk space > -------------------------------------------------------- > > Key: OVIRT-2578 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2578 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Priority: Highest > Labels: ost_code_regression, ost_failures > > we failed both ovirt-engine and ovirt-ansible-vm > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/ > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… > Changes reported were: > https://gerrit.ovirt.org/#/c/95436/1 > https://github.com/oVirt/ovirt-ansible-vm-infra/commit/d17bb187d66df41ac7fa… > Dominik was failing locally as well so its not infra > no OST merge could have caused it > We could not see any regression that could have caused it either but we suddenly started passing: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… > First patch on ovirt-engine that passed was: https://gerrit.ovirt.org/#/c/95447/ > This seems to be a code regression only we do not know where and it may have been quietly fixed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #2087
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/2087/displ…> ------------------------------------------ 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 b75848a829f6096faa2982c7f1f65a28970d2a8b (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b75848a829f6096faa2982c7f1f65a28970d2a8b Commit message: "container: shutdown if jnlp agent failed 3 times" > git rev-list --no-walk b75848a829f6096faa2982c7f1f65a28970d2a8b # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5262957764429549674.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

1 1

[CQ]: 95732, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '18

27 Nov '18

A system test invoked by the "ovirt-4.2" change queue including change 95732,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 95525,2 (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 95525,2 (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/95732/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95525/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3544/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Failed to run project_setup.sh for: #2638 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-7912s.

1 0

[JIRA] (OVIRT-2595) Re: identities on gerrit.ovirt.org
by Daniel Belenky (oVirt JIRA) 27 Nov '18

27 Nov '18

Daniel Belenky created OVIRT-2595: ------------------------------------- Summary: Re: identities on gerrit.ovirt.org Key: OVIRT-2595 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2595 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Daniel Belenky Assignee: infra fwd to infra-support On Tue, Nov 27, 2018 at 4:19 PM Dominik Holler <dholler(a)redhat.com> wrote: > Hi, > can you please remove the identities with the email address > thegreenkepper(a)hollyhome.ath.cx > and > dominik.holler(a)gmail.com > from gerrit.ovirt.org. > But please do not delete dholler(a)redhat.com. > Thanks, > Dominik > _______________________________________________ > 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/C7OLABFOL6YXV… > -- DANIEL BELENKY -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

identities on gerrit.ovirt.org
by Dominik Holler 27 Nov '18

27 Nov '18

Hi, can you please remove the identities with the email address thegreenkepper(a)hollyhome.ath.cx and dominik.holler(a)gmail.com from gerrit.ovirt.org. But please do not delete dholler(a)redhat.com. Thanks, Dominik

2 1

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Failed to run project_setup.sh for: #1503 jenkins [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 vm0009.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Failed to run project_setup.sh for: #1503 jenkins [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 vm0041.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Failed to run project_setup.sh for: #1503 jenkins [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 vm0203.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2581) ovirt-engine is failing on master due to missing packages
by Dafna Ron (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2581?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2581: ----------------------------- Resolution: Fixed Status: Done (was: To Do) this issue was resolved > ovirt-engine is failing on master due to missing packages > --------------------------------------------------------- > > Key: OVIRT-2581 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2581 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11202/ > failure is due to missing packages: > {noformat} > 2018-11-19 13:51:51,498-0500 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-11-19 13:51:51,499-0500 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-I0X8XAo2i4/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-I0X8XAo2i4/otopi-plugins/otopi/packagers/yumpackager.py", line 248, in _packages > self.processTransaction() > File "/tmp/ovirt-I0X8XAo2i4/otopi-plugins/otopi/packagers/yumpackager.py", line 262, in processTransaction > if self._miniyum.buildTransaction(): > File "/tmp/ovirt-I0X8XAo2i4/pythonlib/otopi/miniyum.py", line 920, in buildTransaction > raise yum.Errors.YumBaseError(msg) > YumBaseError: [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-11-19 13:51:51,500-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Package installation': [u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libepoxy.so.0()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libgbm.so.1()(64bit)', u'10:qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 requires libibumad.so.3()(64bit)'] > 2018-11-19 13:51:51,519-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: > id uid local foreign state pid exe > {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95463, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Nov '18

27 Nov '18

A system test invoked by the "ovirt-master" change queue including change 95463,5 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 95589,4 (vdsm) 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 95589,4 (vdsm) 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/95463/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95589/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11696/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 376 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/376/ Build Number: 376 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #376 [Gal Ben Haim] oc-on-ovirt: Update Orb version to 4.2.7 ----------------- Failed Tests: ----------------- No tests ran.

1 8

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Eyal Edri (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2594: ---------------------------------- Nothing on those slaves desc indicated they have an issue, so I'm not sure that was the reason they were taken offline. In any case if they are not OK, they should be reinstalled as centos 7. [~ederevea] can you reinstall all the fc27 slaves as centos7? Probably best to bring them down now ( I would but I don't have access to jenkins for some reason, I can't login ) > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 130 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build Number: 130 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Barak Korren (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2594: ------------------------------------- This looks like a very old known issue - this happens when someone sets up a slave when the {{jenkins}} UID/GID are 1000. [~eedri], [~ena(a)redhat.com] - this seems to be all happenning on the fc27 slaves you brought up, I guess now we know why they were down in the 1st place... [~nsoffer(a)redhat.com] WRT your 2nd issue - we actually have fixes for that where possible - but not in STDCI V1... The code structure of STDCI V1 makes this close to impossible to do there... But for this particular issue, its not really possible to tell the difference because the failure is occurring in the innermost {{mock}} invocation that is launching your script... > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 376 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Nov '18

27 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/376/ Build Number: 376 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #376 [Gal Ben Haim] oc-on-ovirt: Update Orb version to 4.2.7 ----------------- Failed Tests: ----------------- No tests ran.

1 8

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Barak Korren (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2556: ------------------------------------- We need to fix this, or at least come up with some idea as to why is this happening, because like I said, it does not make sense. Also if 1/9 tests fails because of this, you would now rerun all 9 hereby wasting quite a bit of resources.... At the very least I think we may want to add some canary script before your tests start to fail on this and properly flag this as a system error rather then a test failure. [~dbelenky(a)redhat.com] FYI, any idea why we're seeing this again now? > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Roman Mohr > Assignee: infra > Priority: High > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Roman Mohr (oVirt JIRA) 27 Nov '18

27 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2556: ----------------------------------- Just to clarify: it is this time not that critical, since as you say the slot probably got immediately recycled. But it happens from time to time and therefore destroys a run. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Roman Mohr > Assignee: infra > Priority: High > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0