- Infra - oVirt List Archives

Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #1
by jenkins＠jenkins.phx.ovirt.org 15 Oct '19

15 Oct '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-sac-gluster-ansible-el7-x8…> ------------------------------------------ Started by user Dafna Ron [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-sac-gluster-ansible-el7-x8…> No credentials specified Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <http://jenkins.ovirt.org/job/system-sync_mirrors-sac-gluster-ansible-el7-x8…> # timeout=10 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/* > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 No valid HEAD. Skipping the resetting > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > 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 4bdc9bbf0f723360cc3ebd6e0be463c590fc177a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 4bdc9bbf0f723360cc3ebd6e0be463c590fc177a Commit message: "Adding repo sac-gluster-ansible-el7 to local mirror" First time build. Skipping changelog. [system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4169954494809897005.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror sac-gluster-ansible-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 sac-gluster-ansible-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror sac-gluster-ansible-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=sac-gluster-ansible-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 sac-gluster-ansible-el7 yum + local repo_name=sac-gluster-ansible-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/sac-gluster-ansible-el7 /var/www/html/repos/yum/sac-gluster-ansible-el7/base + check_yum_sync_needed sac-gluster-ansible-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=sac-gluster-ansible-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/sac-gluster-ansible-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync sac-gluster-ansible-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=sac-gluster-ansible-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=sac-gluster-ansible-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/sac-gluster-ansible-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 sac-gluster-ansible-el7: [Errno 256] No more mirrors to try. https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/repodat…: [Errno 14] HTTPS Error 404 - Not Found + reposync_out= Build step 'Execute shell' marked build as failure

1 258

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #1019
by jenkins＠jenkins.phx.ovirt.org 15 Oct '19

15 Oct '19

1 1

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

15 Oct '19

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

1 0

[CQ]: 100880, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Oct '19

15 Oct '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 223 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Oct '19

14 Oct '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/223/ Build Number: 223 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #223 [Galit Rosenthal] Network suite use same deploy script as basic suite ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_master_storage_domain_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- 002_bootstrap: INFO: lago-compat-4-3-suite-master-host-0: up lago-compat-4-3-suite-master-host-1: installing ost_utils.general_utils: DEBUG: attempt 2/120, 1 seconds sleeping 002_bootstrap: INFO: lago-compat-4-3-suite-master-host-0: up lago-compat-4-3-suite-master-host-1: installing 002_bootstrap: DEBUG: random host: lago-compat-4-3-suite-master-host-0 --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py", line 449, in add_master_storage_domain add_nfs_storage_domain(prefix) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py", line 453, in add_nfs_storage_domain add_generic_nfs_storage_domain(prefix, SD_NFS_NAME, SD_NFS_HOST_NAME, SD_NFS_PATH, nfs_version='v4_2') File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py", line 505, in add_generic_nfs_storage_domain _add_storage_domain(api, p) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py", line 424, in _add_storage_domain lambda: sd_service.get().status == sdk4.types.StorageDomainStatus.UNATTACHED File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__ self.gen.throw(type, value, traceback) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test_utils/__init__.py", line 265, in TestEvent lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\n002_bootstrap: INFO: lago-compat-4-3-suite-master-host-0: up\nlago-compat-4-3-suite-master-host-1: installing\n\nost_utils.general_utils: DEBUG: attempt 2/120, 1 seconds sleeping\n002_bootstrap: INFO: lago-compat-4-3-suite-master-host-0: up\nlago-compat-4-3-suite-master-host-1: installing\n\n002_bootstrap: DEBUG: random host: lago-compat-4-3-suite-master-host-0\n--------------------- >> end captured logging << ---------------------'

1 1

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

14 Oct '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/978//artifact/exported-a… Cheers, Jenkins

1 0

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

14 Oct '19

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

1 0

[CQ]: 101769,13 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Oct '19

14 Oct '19

Change 101769,13 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/101769/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16506/

1 0

[CQ]: 103960, 4 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 14 Oct '19

14 Oct '19

Change 103960,4 (ovirt-provider-ovn) 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/103960/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16502/

1 0

[JIRA] (OVIRT-2807) changing OST ovirt-system-tests_openshift-on-ovirt-suite-4.2 label for openshift integ-tests-container-big
by Evgheni Dereveanchin (oVirt JIRA) 14 Oct '19

14 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2807?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2807: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > changing OST ovirt-system-tests_openshift-on-ovirt-suite-4.2 label for openshift integ-tests-container-big > ---------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2807 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2807 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Evgeny Slutsky > Assignee: Evgheni Dereveanchin > > Hi, > this nightly OST job started to fail: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > it started to fail after the memory limits change for jenkins jobs: > *05:33:29* resources:*05:33:29* limits:*05:33:29* > memory: "14Gi"*05:33:29* requests:*05:33:29* memory: > "14Gi"*05:33:29* securityContext: > its memory requirement is beyond regular 14Gi. > please changed the label: > *05:33:29* labels:*05:33:29* integ-tests-container: ""*05:33:29* > jenkins: "slave"*05:33:29* jenkins/integ-tests-container: > "true" > *to integ-tests-container-big :* > *04:37:00* labels:*04:37:00* integ-tests-container-big: > ""*04:37:00* jenkins: "slave"*04:37:00* > jenkins/integ-tests-container-big: "true" > Thanks. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Oct '19

14 Oct '19

Failed to run project_setup.sh for: #883 kubernetes-nmstate [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-integ-tests-container-9d8dh.

1 0

[CQ]: f387d7a (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Oct '19

14 Oct '19

A system test invoked by the "ovirt-4.3" change queue including change f387d7a (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/f387d7ac6adcbcd2c260da0… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2289/

1 0

[CQ]: f387d7a (ovirt-engine-sdk-go) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Oct '19

14 Oct '19

A system test invoked by the "ovirt-master" change queue including change f387d7a (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/f387d7ac6adcbcd2c260da0… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16495/

1 0

[CQ]: d584a66 (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Oct '19

13 Oct '19

A system test invoked by the "ovirt-4.3" change queue including change d584a66 (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/d584a6668d840927ca7fc7e… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2287/

1 0

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

13 Oct '19

A system test invoked by the "ovirt-master" change queue including change d584a66 (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/d584a6668d840927ca7fc7e… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16493/

1 0

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

13 Oct '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/977//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: fbbe965 (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests
by oVirt Jenkins 13 Oct '19

13 Oct '19

Change fbbe965 (ovirt-engine-sdk-go) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2285/

1 0

[CQ]: fbbe965 (ovirt-engine-sdk-go) failed "ovirt-master" system tests
by oVirt Jenkins 13 Oct '19

13 Oct '19

Change fbbe965 (ovirt-engine-sdk-go) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16491/

1 0

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

12 Oct '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/976//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 104046,6 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Oct '19

12 Oct '19

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

1 0

[CQ]: 796046f (ovirt-engine-sdk-go) failed "ovirt-master" system tests
by oVirt Jenkins 12 Oct '19

12 Oct '19

Change 796046f (ovirt-engine-sdk-go) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/796046f9e71dafc8df6f536… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16483/

1 0

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

11 Oct '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/975//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 103610,8 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 11 Oct '19

11 Oct '19

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

1 0

[CQ]: 104058, 1 (imgbased) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Oct '19

11 Oct '19

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

1 0

[CQ]: 103689,10 (imgbased) failed "ovirt-master" system tests
by oVirt Jenkins 11 Oct '19

11 Oct '19

Change 103689,10 (imgbased) 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/103689/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16470/

1 0

[CQ]: cf69d89 (ovirt-ansible-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 11 Oct '19

11 Oct '19

Change cf69d89 (ovirt-ansible-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-engine-setup/commit/cf69d893932f1353… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16464/

1 0

[CQ]: 103933, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Oct '19

11 Oct '19

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

1 0

[CQ]: 103760, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Oct '19

11 Oct '19

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

1 0

[CQ]: 103759, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Oct '19

10 Oct '19

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

1 0

[CQ]: 103779,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 10 Oct '19

10 Oct '19

Change 103779,3 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/103779/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16457/

1 0

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

10 Oct '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/974//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: cfe8e00 (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Oct '19

10 Oct '19

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

1 0

[CQ]: 103038, 5 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Oct '19

10 Oct '19

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

1 0

[CQ]: 103553,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 10 Oct '19

10 Oct '19

Change 103553,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/103553/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16444/

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 10 Oct '19

10 Oct '19

Failed to run project_setup.sh for: #856 kubernetes-nmstate [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-integ-tests-container-14zlx.

1 0

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

10 Oct '19

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

1 0

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt
by Eyal Edri (oVirt JIRA) 10 Oct '19

10 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2812?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2812: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > move Douglas' rhvanalyzer repo under oVirt > ------------------------------------------ > > Key: OVIRT-2812 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2812 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: 103929,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 10 Oct '19

10 Oct '19

Change 103929,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/103929/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16439/

1 0

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt
by Eyal Edri (oVirt JIRA) 10 Oct '19

10 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2812?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2812: ---------------------------------- Done, added Michal as admin for the repo. > move Douglas' rhvanalyzer repo under oVirt > ------------------------------------------ > > Key: OVIRT-2812 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2812 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt
by Douglas Landgraf (oVirt JIRA) 10 Oct '19

10 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2812?page=com.atlassian.jira.… ] Douglas Landgraf commented on OVIRT-2812: ----------------------------------------- Please Add this project under oVirt upstream: [https://github.com/dougsland/openshift-rhvanalyzer|https://github.com/dougs…] > move Douglas' rhvanalyzer repo under oVirt > ------------------------------------------ > > Key: OVIRT-2812 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2812 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

2 1

[JIRA] (OVIRT-2813) EL8 builds fail to mount loop device - kernel too old?
by Marcin Sobczyk (oVirt JIRA) 10 Oct '19

10 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2813?page=com.atlassian.jira.… ] Marcin Sobczyk commented on OVIRT-2813: --------------------------------------- Hi, On 10/10/19 6:14 AM, Yuval Turgeman wrote: > You may be running out of loop devices, if that's the case, you need > to manually mknod them, see > https://github.com/oVirt/ovirt-node-ng-image/blob/56a2797b5ef84bd56ab95fdb0… > > On Thursday, October 10, 2019, Nir Soffer <nsoffer(a)redhat.com > <mailto:nsoffer@redhat.com>> wrote: > > On Wed, Oct 9, 2019 at 11:56 PM Nir Soffer <nsoffer(a)redhat.com > <mailto:nsoffer@redhat.com>> wrote: > > I'm trying to run imageio tests on el8 mock, and the tests > fail early when trying to create storage > for testing: > > [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-ext4-mount > Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. > [userstorage] INFO Creating file /var/tmp/imageio-storage/file-512-ext4-mount/file > [userstorage] INFO Creating backing file /var/tmp/imageio-storage/file-512-xfs-backing > [userstorage] INFO Creating loop device /var/tmp/imageio-storage/file-512-xfs-loop > [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-xfs-mount > mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad option, bad superblock on /dev/loop4, missing codepage or helper program, or other error. > Traceback (most recent call last): > File "/usr/local/bin/userstorage", line 10, in <module> > sys.exit(main()) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 42, in main > create(cfg) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 52, in create > b.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", line 47, in create > self._mount.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 53, in create > self._mount_loop() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 94, in _mount_loop > ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', '/var/tmp/imageio-storage/file-512-xfs-loop', '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit status 32. > > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti… > <https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti…> > > > Same code runs fine in Travis: > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > <https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863> > > > And also locally on Fedora 29: > $ ../jenkins/mock_configs/mock_runner.sh -C > ../jenkins/mock_configs -p el8 > ... > ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 > ## took 85 seconds > ## rc = 0 > > > My guess is that we run el8 jobs on el7 hosts with old kernels > (Suggestion: Use Linux kernel >= 3.18 for improved stability > of the metadata and journal checksum features.) > > > Here is info from failed builds: > > DEBUG buildroot.py:503: kernel version == 3.10.0-693.11.6.el7.ppc64le > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593/artif… > <https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593/artif…> > > DEBUG buildroot.py:503: kernel version == 3.10.0-957.12.1.el7.x86_64 > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593/artif… > <https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593/artif…> > and successful builds: > > DEBUG buildroot.py:503: kernel version == 5.1.18-200.fc29.x86_64 > My laptop > > Runtime kernel version: 4.15.0-1032-gcp > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > <https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863> > > > This issue will affects vdsm, using similar code to create > storage for testing. > > For vdsm the issue is more tricky, since it requires same > host/distro: > > 49 - tests-py37: > 50 runtime-requirements: > 51 host-distro: same > > So I think we need: > - make slaves with newer kernel (fc29? fc30?) with the el8 > mock env > - add el8 slaves for running el8 mock with "host-distro: same" > AFAIK Anton was working on that and we should have el8-native ci slaves maybe even today. +Anton > > If we don't have a solution we need to disable el8 tests, or > continue testing without > storage, which will skip about 200 tests. > > Nir > > EL8 builds fail to mount loop device - kernel too old? > ------------------------------------------------------ > > Key: OVIRT-2813 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2813 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I'm trying to run imageio tests on el8 mock, and the tests fail early when > trying to create storage > for testing: > [userstorage] INFO Creating filesystem > /var/tmp/imageio-storage/file-512-ext4-mount > Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features. > [userstorage] INFO Creating file > /var/tmp/imageio-storage/file-512-ext4-mount/file > [userstorage] INFO Creating backing file > /var/tmp/imageio-storage/file-512-xfs-backing > [userstorage] INFO Creating loop device > /var/tmp/imageio-storage/file-512-xfs-loop > [userstorage] INFO Creating filesystem > /var/tmp/imageio-storage/file-512-xfs-mount > mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad > option, bad superblock on /dev/loop4, missing codepage or helper > program, or other error. > Traceback (most recent call last): > File "/usr/local/bin/userstorage", line 10, in <module> > sys.exit(main()) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", > line 42, in main > create(cfg) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", > line 52, in create > b.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", > line 47, in create > self._mount.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", > line 53, in create > self._mount_loop() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", > line 94, in _mount_loop > ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', > '/var/tmp/imageio-storage/file-512-xfs-loop', > '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit > status 32. > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti… > Same code runs fine in Travis: > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > And also locally on Fedora 29: > $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p el8 > ... > ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 > ## took 85 seconds > ## rc = 0 > My guess is that we run el8 jobs on el7 hosts with old kernels > (Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features.) > This issue will affects vdsm, using similar code to create storage for > testing. > For vdsm the issue is more tricky, since it requires same host/distro: > 49 - tests-py37: > 50 runtime-requirements: > 51 host-distro: same > So I think we need: > - make slaves with newer kernel (fc29? fc30?) with the el8 mock env > - add el8 slaves for running el8 mock with "host-distro: same" > If we don't have a solution we need to disable el8 tests, or continue > testing without > storage, which will skip about 200 tests. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2813) EL8 builds fail to mount loop device - kernel too old?
by Yuval Turgeman (oVirt JIRA) 10 Oct '19

10 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2813?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-2813: --------------------------------------- You may be running out of loop devices, if that's the case, you need to manually mknod them, see https://github.com/oVirt/ovirt-node-ng-image/blob/56a2797b5ef84bd56ab95fdb0… On Thursday, October 10, 2019, Nir Soffer <nsoffer(a)redhat.com> wrote: > On Wed, Oct 9, 2019 at 11:56 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> I'm trying to run imageio tests on el8 mock, and the tests fail early >> when trying to create storage >> for testing: >> >> [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-ext4-mount >> Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. >> [userstorage] INFO Creating file /var/tmp/imageio-storage/file-512-ext4-mount/file >> [userstorage] INFO Creating backing file /var/tmp/imageio-storage/file-512-xfs-backing >> [userstorage] INFO Creating loop device /var/tmp/imageio-storage/file-512-xfs-loop >> [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-xfs-mount >> mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad option, bad superblock on /dev/loop4, missing codepage or helper program, or other error. >> Traceback (most recent call last): >> File "/usr/local/bin/userstorage", line 10, in <module> >> sys.exit(main()) >> File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 42, in main >> create(cfg) >> File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 52, in create >> b.create() >> File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", line 47, in create >> self._mount.create() >> File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 53, in create >> self._mount_loop() >> File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 94, in _mount_loop >> ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) >> File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call >> raise CalledProcessError(retcode, cmd) >> subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', '/var/tmp/imageio-storage/file-512-xfs-loop', '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit status 32. >> >> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check- >> patch/1593//artifact/check-patch.el8.ppc64le/mock_logs/ >> script/stdout_stderr.log >> >> >> Same code runs fine in Travis: >> https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 >> >> >> And also locally on Fedora 29: >> $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p >> el8 >> ... >> ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 >> ## took 85 seconds >> ## rc = 0 >> >> >> My guess is that we run el8 jobs on el7 hosts with old kernels >> (Suggestion: Use Linux kernel >= 3.18 for improved stability of the >> metadata and journal checksum features.) >> > > Here is info from failed builds: > > DEBUG buildroot.py:503: kernel version == 3.10.0-693.11.6.el7.ppc64le > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check- > patch/1593/artifact/check-patch.el8.ppc64le/mock_logs/init/root.log > > DEBUG buildroot.py:503: kernel version == 3.10.0-957.12.1.el7.x86_64 > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check- > patch/1593/artifact/check-patch.el8.x86_64/mock_logs/init/root.log > > and successful builds: > > DEBUG buildroot.py:503: kernel version == 5.1.18-200.fc29.x86_64 > My laptop > > Runtime kernel version: 4.15.0-1032-gcp > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > > > This issue will affects vdsm, using similar code to create storage for >> testing. >> >> For vdsm the issue is more tricky, since it requires same host/distro: >> >> 49 - tests-py37: >> 50 runtime-requirements: >> 51 host-distro: same >> >> So I think we need: >> - make slaves with newer kernel (fc29? fc30?) with the el8 mock env >> - add el8 slaves for running el8 mock with "host-distro: same" >> >> If we don't have a solution we need to disable el8 tests, or continue >> testing without >> storage, which will skip about 200 tests. >> >> Nir >> >> > EL8 builds fail to mount loop device - kernel too old? > ------------------------------------------------------ > > Key: OVIRT-2813 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2813 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I'm trying to run imageio tests on el8 mock, and the tests fail early when > trying to create storage > for testing: > [userstorage] INFO Creating filesystem > /var/tmp/imageio-storage/file-512-ext4-mount > Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features. > [userstorage] INFO Creating file > /var/tmp/imageio-storage/file-512-ext4-mount/file > [userstorage] INFO Creating backing file > /var/tmp/imageio-storage/file-512-xfs-backing > [userstorage] INFO Creating loop device > /var/tmp/imageio-storage/file-512-xfs-loop > [userstorage] INFO Creating filesystem > /var/tmp/imageio-storage/file-512-xfs-mount > mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad > option, bad superblock on /dev/loop4, missing codepage or helper > program, or other error. > Traceback (most recent call last): > File "/usr/local/bin/userstorage", line 10, in <module> > sys.exit(main()) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", > line 42, in main > create(cfg) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", > line 52, in create > b.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", > line 47, in create > self._mount.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", > line 53, in create > self._mount_loop() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", > line 94, in _mount_loop > ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', > '/var/tmp/imageio-storage/file-512-xfs-loop', > '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit > status 32. > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti… > Same code runs fine in Travis: > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > And also locally on Fedora 29: > $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p el8 > ... > ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 > ## took 85 seconds > ## rc = 0 > My guess is that we run el8 jobs on el7 hosts with old kernels > (Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features.) > This issue will affects vdsm, using similar code to create storage for > testing. > For vdsm the issue is more tricky, since it requires same host/distro: > 49 - tests-py37: > 50 runtime-requirements: > 51 host-distro: same > So I think we need: > - make slaves with newer kernel (fc29? fc30?) with the el8 mock env > - add el8 slaves for running el8 mock with "host-distro: same" > If we don't have a solution we need to disable el8 tests, or continue > testing without > storage, which will skip about 200 tests. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: 103925,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

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

1 0

[CQ]: 103706, 4 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

Change 103706,4 (ovirt-hosted-engine-setup) 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/103706/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16436/

1 0

[CQ]: 103725, 6 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Oct '19

09 Oct '19

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

1 0

[CQ]: 104004, 2 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

Change 104004,2 (ovirt-hosted-engine-ha) 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/104004/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16432/

1 0

oVirt infra daily report - unstable production jobs - 973
by jenkins＠jenkins.phx.ovirt.org 09 Oct '19

09 Oct '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/973//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 103387, 8 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Oct '19

09 Oct '19

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

1 0

[JIRA] (OVIRT-2813) EL8 builds fail to mount loop device - kernel too old?
by Nir Soffer (oVirt JIRA) 09 Oct '19

09 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2813?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2813: ----------------------------------- On Wed, Oct 9, 2019 at 11:56 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > I'm trying to run imageio tests on el8 mock, and the tests fail early when > trying to create storage > for testing: > > [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-ext4-mount > Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. > [userstorage] INFO Creating file /var/tmp/imageio-storage/file-512-ext4-mount/file > [userstorage] INFO Creating backing file /var/tmp/imageio-storage/file-512-xfs-backing > [userstorage] INFO Creating loop device /var/tmp/imageio-storage/file-512-xfs-loop > [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-xfs-mount > mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad option, bad superblock on /dev/loop4, missing codepage or helper program, or other error. > Traceback (most recent call last): > File "/usr/local/bin/userstorage", line 10, in <module> > sys.exit(main()) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 42, in main > create(cfg) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 52, in create > b.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", line 47, in create > self._mount.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 53, in create > self._mount_loop() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 94, in _mount_loop > ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', '/var/tmp/imageio-storage/file-512-xfs-loop', '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit status 32. > > > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti… > > > Same code runs fine in Travis: > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > > > And also locally on Fedora 29: > $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p el8 > ... > ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 > ## took 85 seconds > ## rc = 0 > > > My guess is that we run el8 jobs on el7 hosts with old kernels > (Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features.) > Here is info from failed builds: DEBUG buildroot.py:503: kernel version == 3.10.0-693.11.6.el7.ppc64le https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593/artif… DEBUG buildroot.py:503: kernel version == 3.10.0-957.12.1.el7.x86_64 https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593/artif… and successful builds: DEBUG buildroot.py:503: kernel version == 5.1.18-200.fc29.x86_64 My laptop Runtime kernel version: 4.15.0-1032-gcp https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 This issue will affects vdsm, using similar code to create storage for > testing. > > For vdsm the issue is more tricky, since it requires same host/distro: > > 49 - tests-py37: > 50 runtime-requirements: > 51 host-distro: same > > So I think we need: > - make slaves with newer kernel (fc29? fc30?) with the el8 mock env > - add el8 slaves for running el8 mock with "host-distro: same" > > If we don't have a solution we need to disable el8 tests, or continue > testing without > storage, which will skip about 200 tests. > > Nir > > > EL8 builds fail to mount loop device - kernel too old? > ------------------------------------------------------ > > Key: OVIRT-2813 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2813 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I'm trying to run imageio tests on el8 mock, and the tests fail early when > trying to create storage > for testing: > [userstorage] INFO Creating filesystem > /var/tmp/imageio-storage/file-512-ext4-mount > Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features. > [userstorage] INFO Creating file > /var/tmp/imageio-storage/file-512-ext4-mount/file > [userstorage] INFO Creating backing file > /var/tmp/imageio-storage/file-512-xfs-backing > [userstorage] INFO Creating loop device > /var/tmp/imageio-storage/file-512-xfs-loop > [userstorage] INFO Creating filesystem > /var/tmp/imageio-storage/file-512-xfs-mount > mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad > option, bad superblock on /dev/loop4, missing codepage or helper > program, or other error. > Traceback (most recent call last): > File "/usr/local/bin/userstorage", line 10, in <module> > sys.exit(main()) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", > line 42, in main > create(cfg) > File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", > line 52, in create > b.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", > line 47, in create > self._mount.create() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", > line 53, in create > self._mount_loop() > File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", > line 94, in _mount_loop > ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', > '/var/tmp/imageio-storage/file-512-xfs-loop', > '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit > status 32. > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti… > Same code runs fine in Travis: > https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 > And also locally on Fedora 29: > $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p el8 > ... > ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 > ## took 85 seconds > ## rc = 0 > My guess is that we run el8 jobs on el7 hosts with old kernels > (Suggestion: Use Linux kernel >= 3.18 for improved stability of the > metadata and journal checksum features.) > This issue will affects vdsm, using similar code to create storage for > testing. > For vdsm the issue is more tricky, since it requires same host/distro: > 49 - tests-py37: > 50 runtime-requirements: > 51 host-distro: same > So I think we need: > - make slaves with newer kernel (fc29? fc30?) with the el8 mock env > - add el8 slaves for running el8 mock with "host-distro: same" > If we don't have a solution we need to disable el8 tests, or continue > testing without > storage, which will skip about 200 tests. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2813) EL8 builds fail to mount loop device - kernel too old?
by Nir Soffer (oVirt JIRA) 09 Oct '19

09 Oct '19

Nir Soffer created OVIRT-2813: --------------------------------- Summary: EL8 builds fail to mount loop device - kernel too old? Key: OVIRT-2813 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2813 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I'm trying to run imageio tests on el8 mock, and the tests fail early when trying to create storage for testing: [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-ext4-mount Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. [userstorage] INFO Creating file /var/tmp/imageio-storage/file-512-ext4-mount/file [userstorage] INFO Creating backing file /var/tmp/imageio-storage/file-512-xfs-backing [userstorage] INFO Creating loop device /var/tmp/imageio-storage/file-512-xfs-loop [userstorage] INFO Creating filesystem /var/tmp/imageio-storage/file-512-xfs-mount mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad option, bad superblock on /dev/loop4, missing codepage or helper program, or other error. Traceback (most recent call last): File "/usr/local/bin/userstorage", line 10, in <module> sys.exit(main()) File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 42, in main create(cfg) File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", line 52, in create b.create() File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", line 47, in create self._mount.create() File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 53, in create self._mount_loop() File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 94, in _mount_loop ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path]) File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', '/var/tmp/imageio-storage/file-512-xfs-loop', '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit status 32. https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1593//arti… Same code runs fine in Travis: https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863 And also locally on Fedora 29: $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p el8 ... ## Wed Oct 9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64 ## took 85 seconds ## rc = 0 My guess is that we run el8 jobs on el7 hosts with old kernels (Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features.) This issue will affects vdsm, using similar code to create storage for testing. For vdsm the issue is more tricky, since it requires same host/distro: 49 - tests-py37: 50 runtime-requirements: 51 host-distro: same So I think we need: - make slaves with newer kernel (fc29? fc30?) with the el8 mock env - add el8 slaves for running el8 mock with "host-distro: same" If we don't have a solution we need to disable el8 tests, or continue testing without storage, which will skip about 200 tests. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0