August 2019 - 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

what is a telecommunications job
by kumarfield28＠gmail.com 23 Sep '19

23 Sep '19

These days, you will often come across telecommunication field technician jobs on the internet and newspapers. This must have gotten you curious regarding telecom engineer jobs. You might be wondering whether it would be the right career option for you and what kind of telecom services you will need to provide if this is the field you opt for. If that is the case, this is where your search culminates since we will provide you with the required details regarding telecom engineer jobs and services among other things. https://www.fieldengineer.com/blogs/telecom-engineer-job-description/

3 2

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 179 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Sep '19

01 Sep '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/179/ Build Number: 179 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #179 [edwardh(a)redhat.com] network, ovirtlib: Expose the root system through sdkentity ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.ha_recovery_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2 lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0 lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output: 7527 lago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527 lago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 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/004_basic_sanity.py", line 725, in ha_recovery 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 << --------------------\nlago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output:\n 7527\n\nlago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527\n\nlago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0\n--------------------- >> end captured logging << ---------------------'

1 1

oVirt infra daily report - unstable production jobs - 934
by jenkins＠jenkins.phx.ovirt.org 01 Sep '19

01 Sep '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/934//artifact/exported-a… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 933
by jenkins＠jenkins.phx.ovirt.org 31 Aug '19

31 Aug '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/933//artifact/exported-a… Cheers, Jenkins

1 0

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

30 Aug '19

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

1 0

[oVirt] [CQ weekly status] [30-08-2019]
by Dusan Fodor 30 Aug '19

30 Aug '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: NOT RELEVANT This CQ is not followed anymore, since it's about to be decommissioned. *CQ-4.3*: YELLOW (#1) Last failure was on 28-08 for ovirt-web-ui. It was solved soon after by change 57c5c4b. *CQ-Master:* RED (#1) Last failure was on 30-08 for ovirt-engine in host-deployment. This issue is under investigation. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt .org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

1 0

[CQ]: 102980, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Aug '19

30 Aug '19

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

1 0

[CQ]: 101707, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Aug '19

30 Aug '19

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

1 0

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

30 Aug '19

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

1 0