- Infra - oVirt List Archives

Build failed in Jenkins: system-mk_mirrors_index-yum #34411
by jenkins＠jenkins.phx.ovirt.org 23 Jul '18

23 Jul '18

See <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/34411/display/redi…> ------------------------------------------ Started by upstream project "system-sync_mirrors-centos-opstools-testing-el7-x86_64" build number 1655 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/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 2f98558c97f22c06e50cbd4e435866e077ecdba6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2f98558c97f22c06e50cbd4e435866e077ecdba6 Commit message: "Add DSL handling for the 'reporting' option" > git rev-list --no-walk 2f98558c97f22c06e50cbd4e435866e077ecdba6 # timeout=10 [system-mk_mirrors_index-yum] $ /bin/bash -xe /tmp/jenkins2111071547745659223.sh + jenkins/scripts/mirror_mgr.sh write_latest_lists yum Acquired lock: latest_lists_yum Writing latest index files for yum repos mv: cannot create regular file ‘/var/www/html/repos/yum/all_latest.py’: No space left on device mv: cannot create regular file ‘/var/www/html/repos/yum/all_latest.json’: No space left on device mv: cannot create regular file ‘/var/www/html/repos/yum/all_latest.yaml’: No space left on device Released lock: latest_lists_yum Build step 'Execute shell' marked build as failure

1 48

[JIRA] (OVIRT-2362) on fc27 globl_setup.sh installes 'python2-paramiko' and then remove it
by Barak Korren (oVirt JIRA) 23 Jul '18

23 Jul '18

Barak Korren created OVIRT-2362: ----------------------------------- Summary: on fc27 globl_setup.sh installes 'python2-paramiko' and then remove it Key: OVIRT-2362 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2362 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra We should decide if we need it there or not and modify the script, as it is right now, it simply slows down node allocation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

oVirt infra daily report - unstable production jobs - 529
by jenkins＠jenkins.phx.ovirt.org 23 Jul '18

23 Jul '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/529//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el7-x86_64 #1654
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el7-x86_64/1654/displ…> Changes: [Barak Korren] Move DSL normalization functions to common package [Barak Korren] Re-factor STDCI DSL files for PEP8 [Barak Korren] Add DSL handling for the 'reporting' option ------------------------------------------ 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-el7-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 2f98558c97f22c06e50cbd4e435866e077ecdba6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2f98558c97f22c06e50cbd4e435866e077ecdba6 Commit message: "Add DSL handling for the 'reporting' option" > git rev-list --no-walk b1bec36b3a7a5baf8c1edd7fb4a9763560698de7 # timeout=10 [system-sync_mirrors-epel-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1790625315613362930.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: epel-el7 Syncing yum repo epel-el7 for arch: x86_64 epel-el7/group | 365 kB 00:00 (2/4): nekovm-devel-2.2.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA (1/4): nekovm-2.2.0-5.el7.x86_64.rpm | 388 kB 00:02 (3/4): transifex-client-0. 7% [= ] 0.0 B/s | 547 kB --:-- ETA (2/4): nekovm-devel-2.2.0-5.el7.x86_64.rpm | 25 kB 00:02 (3/4): transifex-client-0.13.4-1.el7.noarch.rpm | 224 kB 00:02 (4/4): wordpress-4.9.7-1.e 13% [== ] 530 kB/s | 1.0 MB 00:12 ETA (4/4): wordpress-4.9.7-1.e 26% [==== ] 696 kB/s | 2.0 MB 00:08 ETA (4/4): wordpress-4.9.7-1.e 48% [=======- ] 1.0 MB/s | 3.7 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 50% [======== ] 963 kB/s | 3.9 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 53% [======== ] 935 kB/s | 4.0 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 55% [========- ] 906 kB/s | 4.2 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 58% [========= ] 884 kB/s | 4.4 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 60% [=========- ] 863 kB/s | 4.6 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 63% [========== ] 847 kB/s | 4.8 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 66% [==========- ] 831 kB/s | 5.0 MB 00:03 ETA (4/4): wordpress-4.9.7-1.e 69% [=========== ] 819 kB/s | 5.2 MB 00:02 ETA (4/4): wordpress-4.9.7-1.e 72% [===========- ] 807 kB/s | 5.5 MB 00:02 ETA (4/4): wordpress-4.9.7-1.e 75% [============ ] 800 kB/s | 5.7 MB 00:02 ETA (4/4): wordpress-4.9.7-1.e 78% [============- ] 792 kB/s | 5.9 MB 00:02 ETA (4/4): wordpress-4.9.7-1.e 81% [============= ] 789 kB/s | 6.2 MB 00:01 ETA (4/4): wordpress-4.9.7-1.e 84% [=============- ] 786 kB/s | 6.4 MB 00:01 ETA (4/4): wordpress-4.9.7-1.e 88% [============== ] 783 kB/s | 6.7 MB 00:01 ETA (4/4): wordpress-4.9.7-1.e 91% [==============- ] 786 kB/s | 6.9 MB 00:00 ETA (4/4): wordpress-4.9.7-1.e 94% [=============== ] 786 kB/s | 7.2 MB 00:00 ETA (4/4): wordpress-4.9.7-1.e 98% [===============-] 787 kB/s | 7.5 MB 00:00 ETA (4/4): wordpress-4.9.7-1.el7.noarch.rpm | 7.0 MB 00:10 Generating yum repo metadata for: epel-el7 Cannot create/verify /var/www/html/repos/yum/epel-el7/base/.repodata Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 374 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/374/ Build Number: 374 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #374 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7faa1234a5f0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type raise Error(msg) Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML --------------------- >> 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type raise Error(msg) 'The response content type \'text/html; charset=iso-8859-1\' isn\'t the expected XML\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7faa1234a5f0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, in get\n return self._internal_get(headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault\n body = self._internal_read_body(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body\n self._connection.check_xml_content_type(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type\n response.headers\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type\n raise Error(msg)\nError: The response content type \'text/html; charset=iso-8859-1\' isn\'t the expected XML\n--------------------- >> end captured logging << ---------------------'

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 403 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/403/ Build Number: 403 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #403 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 149 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/149/ Build Number: 149 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #149 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 590 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/590/ Build Number: 590 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #590 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 409 reason: Conflict detail: Cannot create Snapshot: The following disks are locked: vm0_disk0. Please try again in a few minutes. Stack Trace: Traceback (most recent call last): 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/004_basic_sanity.py", line 194, in snapshot_merge api.vms.get(VM0_NAME).snapshots.add(dead_snap2_params) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34511, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot create Snapshot: The following disks are locked: vm0_disk0. Please try again in a few minutes.

1 5

[JIRA] (OVIRT-2330) Host specific resource allocation for stdci containers
by Gal Ben Haim (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2330?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2330: -------------------------------- Description: To maximize the utilization of stdci containers, we need a mechanism that can decide how much RAM and CPU each stdci container gets and how many stdci containers we can run on that host. A special handling should be done for user-defined containers (those are ones that the user run as part of his script). Those containers are created using a mounted docker socket, so the resource limit we put on the STDCI container will not affect them. was:To maximize the utilization of stdci containers, we need a mechanism that can decide how much RAM and CPU each stdci container gets and how many stdci containers we can run on that host > Host specific resource allocation for stdci containers > ------------------------------------------------------ > > Key: OVIRT-2330 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2330 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > To maximize the utilization of stdci containers, we need a mechanism that can decide how much RAM and CPU each stdci container gets and how many stdci containers we can run on that host. > A special handling should be done for user-defined containers (those are ones that the user run as part of his script). Those containers are created using a mounted docker socket, so the resource limit we put on the STDCI container will not affect them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 626 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/626/ Build Number: 626 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #626 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2361?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2361: -------------------------------- Component/s: Repositories Mgmt > Remove 4.1 tested repo > ---------------------- > > Key: OVIRT-2361 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt > Reporter: Ehud Yonasi > Assignee: infra > > current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2361?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2361: -------------------------------- Issue Type: Task (was: Outage) > Remove 4.1 tested repo > ---------------------- > > Key: OVIRT-2361 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ehud Yonasi > Assignee: infra > > current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Ehud Yonasi (oVirt JIRA) 22 Jul '18

22 Jul '18

Ehud Yonasi created OVIRT-2361: ---------------------------------- Summary: Remove 4.1 tested repo Key: OVIRT-2361 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Ehud Yonasi Assignee: infra current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Ehud Yonasi (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2361?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2361: ------------------------------- Epic Link: OVIRT-2044 > Remove 4.1 tested repo > ---------------------- > > Key: OVIRT-2361 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Ehud Yonasi > Assignee: infra > > current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- Here is how you can gain access to the env vars you passed to Dokcer, no need to pass them as files: https://unix.stackexchange.com/questions/146995/inherit-environment-variabl… and, as mentioned on that ticket, its a good idea to have an early one-shot service that will copy the variables you need into /etc/environment to make them available to non-root services. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2360) Enable setting a default version for the OST manual job and set 4.2 as the default.
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2360?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2360: ----------------------------------- Assignee: Ehud Yonasi (was: infra) > Enable setting a default version for the OST manual job and set 4.2 as the default. > ----------------------------------------------------------------------------------- > > Key: OVIRT-2360 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2360 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Barak Korren > Assignee: Ehud Yonasi > Priority: High > > We need to ensure the default oVirt version can be configure when using the OST mnaul job template. Once we do that we need to also configure the default to be 4.2 currently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2360) Enable setting a default version for the OST manual job and set 4.2 as the default.
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

Barak Korren created OVIRT-2360: ----------------------------------- Summary: Enable setting a default version for the OST manual job and set 4.2 as the default. Key: OVIRT-2360 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2360 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Manual job Reporter: Barak Korren Assignee: infra Priority: High We need to ensure the default oVirt version can be configure when using the OST mnaul job template. Once we do that we need to also configure the default to be 4.2 currently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky edited comment on OVIRT-2359 at 7/22/18 11:11 AM: ----------------------------------------------------------------- But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode with some system infomration about stdci in /etc/stdci is a good solution. WDYT? was (Author: dbelenky(a)redhat.com) But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode that some system infomration about stdci in /etc/stdci is a good solution. WDYT? > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode that some system infomration about stdci in /etc/stdci is a good solution. WDYT? > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- I think that systemd drops environment information by design in order to ensure clean environment for every process it starts. Maybe there is a workaround but what's wrong with EnvironmentFiles? You'll have to provide this infomration to systemd anyway, so by having a well know directory in a host with N systemd environment files, one for every container, you have all the needed information you need to run them. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-1993) Looking for a new task to help with
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1993?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1993: ---------------------------------- Its on the previous comment: 3. Join the infra weekly meetings on Wed 14:00 UTC ( https://bluejeans.com/902682731 ), this week is off, but next week should be on. > Looking for a new task to help with > ----------------------------------- > > Key: OVIRT-1993 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1993 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sailesh baskar > Assignee: infra > > I would like to open a new ticket in the infrastructure team. Can you help > in the process? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93234,1 (ioprocess) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Jul '18

22 Jul '18

Change 93234,1 (ioprocess) 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/93234/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2693/

2 1

[JIRA] (OVIRT-2353) remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job
by Ehud Yonasi (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2353?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2353: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job > ------------------------------------------------------------ > > Key: OVIRT-2353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2353 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Ehud Yonasi > > this job is failing and Daniel confirmed we do not need it any longer. > can we remove it or cancel alerts for it? > https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-gl… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2353) remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job
by Ehud Yonasi (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2353?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2353: ------------------------------------ This job was created by me for sandro, and it is now fixed. i sent a couple of emails to ignore it (and btw this is a living proof that replying to emails might not be the best solution for syncing infra owners :) ) Details are here: [1] Jira Ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2290 [2] Gerrit Patch: https://gerrit.ovirt.org/#/c/93041/ > remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job > ------------------------------------------------------------ > > Key: OVIRT-2353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2353 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > this job is failing and Daniel confirmed we do not need it any longer. > can we remove it or cancel alerts for it? > https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-gl… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2353) remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2353?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2353: ---------------------------------- +1 from me, [~sbonazzo(a)redhat.com] and @sahina which isn't here should also ACK, But you can also verify it by checking if it is on any OST reposync file or in the official oVirt release RPMs. > remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job > ------------------------------------------------------------ > > Key: OVIRT-2353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2353 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > this job is failing and Daniel confirmed we do not need it any longer. > can we remove it or cancel alerts for it? > https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-gl… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2358: ------------------------------------- [~eedri] not sure I see where the gap is. [~sradco(a)redhat.com] can you use links to reosurces instead of Jenkins? > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2358: ---------------------------------- [~bkorren(a)redhat.com] I mean, can we provide a reasonable way for [~sradco(a)redhat.com] to get the same info she needs to a release and not have to use the 'keep forever' option? even if its manual ( as its today as well ). > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2358: ------------------------------------- [~eedri] yeah, look at the job output/artifacts. Not sure what you mean by "an immediate alternative option", this is a manual process where people update a ropman configurationfil in releng-tools, they can put any URL there including ones that point to resoures.ovirt.org. Also this being a repoman configuration file, people can do quite complex things like put a general link to the repo on resources and then use filters to select the exact desired set of packages. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- it sounds very strange that systemd just drops the environment information passed to the container; We shouldn't be inventing our own ways to pass this information; There must be some work-around for this somewhere; Perhaps the root environment is exposed by some file in /proc or /sys? > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2358: ---------------------------------- Is there an easy way to for someone to know the RPM name? I didn't understand from your answer if there is an immediate alternative option to the current flow. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- currently, in order to start an stdci container, you need to write an environment file for systemd. This file needs information such as the agent's name, the secret, etc. We need it because systemd unitfile doesn't have access to the environment where docker set's the variables (root user's environment). So you need one systemd-environment file per container. It's done dynamically when you run not during the build. Thinking of it now, it serves a completely different purpose and shoudn't be mixed. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-4.1-testing-el7-x86_64 #1
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-testing-el7-…> ------------------------------------------ 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-glusterfs-4.1-testing-el7-…> Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-testing-el7-…> # 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 a0f3a1b493603a886874a3128be830a462c211ad (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a0f3a1b493603a886874a3128be830a462c211ad Commit message: "Add engine-db-query to stdci-v2" First time build. Skipping changelog. [system-sync_mirrors-glusterfs-4.1-testing-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2502757672743858937.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-4.1-testing-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Warning: cannot find repository glusterfs-4.1-testing-el7 No repositories found Build step 'Execute shell' marked build as failure

1 15

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2358: ------------------------------------- [~eedri] as you've said, stuff can be taken from resources, which is a far better storage space space then jenkins... then again, to figure out the link to resource you need to know the RPM anme, while to Jenkins you get a direct link in the notification sent to Gerrit > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- not sure what do you mean by one file per container - this needs to be dynamically done by the container itself as it starts and not statically at build time. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2358: ---------------------------------- [~bkorren@redhat.com][~dbelenky@redhat.com] currently there is no other way to support the builds other than keep forever? If not, please help Shirly with her request. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Shirly Radco (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-2358: ------------------------------------- I understand, but currently this is the process that we use for linking the builds to the releng-tools for the RHV build. I talked to Lev and Barak, I understand that they need revisit this process... But this is how it is done today. So, we keep the builds in jenkins for at least a version. After the discussion we had I found that I should be able to revert the "keep forever". Since this option was missing for me I did not know it was available for others. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- yeah, maybe that's a better approach. We will also benefit from it in the systemd unitfile - currently we need to read variables such as the JNLP secret and the agent name from a systemd-environment file. Maybe having one file per container that will hold all the needed information can help us here. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-4.1-el7-x86_64 #1
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-el7-x86_64/1…> ------------------------------------------ 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-glusterfs-4.1-el7-x86_64/w…> Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-el7-x86_64/w…> # 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 a0f3a1b493603a886874a3128be830a462c211ad (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a0f3a1b493603a886874a3128be830a462c211ad Commit message: "Add engine-db-query to stdci-v2" First time build. Skipping changelog. [system-sync_mirrors-glusterfs-4.1-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3284599783114877569.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-4.1-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Warning: cannot find repository glusterfs-4.1-el7 No repositories found Build step 'Execute shell' marked build as failure

2 23

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2359 at 7/22/18 8:28 AM: -------------------------------------------------------------- I see, hmm... perhaps we need some container start-up script that would copy things into /etc/environment to make them available for all users in the container. was (Author: bkorren(a)redhat.com) I see, hmm... perhaps we need some container start-up script that would copy things into /etc/environment to make then available for all users in the container. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- I see, hmm... perhaps we need some container start-up script that would copy things into /etc/environment to make then available for all users in the container. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- I never said Jenkins should have anything to do with it. I said that it has to be set in Jenkins's user aka "jenkins" that is created during the build. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2359: ---------------------------------- Description: We need to set a variable under the jenkins user that will indicate we're running inside a container. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93178,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Jul '18

22 Jul '18

Change 93178,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/93178/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2690/

3 2

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- I say jenkins should have nothing to do with this, it should be set by the script that starts up the containers. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2358: ---------------------------------- Can you please explain why do you need to keep forever builds? for which project and what is the goal? All of the artifacts you build in Jenkins usually go to resources.ovirt.org and kept there for at least one month. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2359: ---------------------------------- Epic Link: OVIRT-2326 > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

Daniel Belenky created OVIRT-2359: ------------------------------------- Summary: Set environment variable in jenkins user's env to inidicate it's a container Key: OVIRT-2359 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Shirly Radco (oVirt JIRA) 22 Jul '18

22 Jul '18

Shirly Radco created OVIRT-2358: ----------------------------------- Summary: Permissions to revert "keep build forever" in jenkins Key: OVIRT-2358 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Shirly Radco Assignee: infra Hi, I seem to be missing permission to revert "keep build forever" in jenkins. Can you add me this permission? Thanks, -- SHIRLY RADCO BI SENIOR SOFTWARE ENGINEER Red Hat Israel <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-fc28-x86_64 - Build # 4 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build Number: 4 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #4 [Yuval Turgeman] automation: remove build-artifacts* from stdci-v2 ----------------- Failed Tests: ----------------- No tests ran.

1 1

Re: Change in ovirt-engine[master]: packaging: setup: postgres95: Verify selinux file contexts
by Yedidyah Bar David 22 Jul '18

22 Jul '18

On Thu, Jul 19, 2018 at 12:47 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. > > Change subject: packaging: setup: postgres95: Verify selinux file contexts > ...................................................................... > > > Patch Set 4: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc28-x86_64/12… : FAILURE This failed (more than ones, but not always, for now) with: 09:13:11 No match for argument: otopi 09:13:11 Error: Unable to find a match Not sure if that's related, but since some weeks ago, we no longer have in master a package called 'otopi'. Instead, a new package 'python2-otopi' should provide otopi. Any idea? Thanks. > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/417… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/93147 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: Ic12c5252d1f7597b1ab5ff012b195ed04addbe48 > Gerrit-Change-Number: 93147 > Gerrit-PatchSet: 4 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > Gerrit-Reviewer: Ido Rosenzwig <irosenzw(a)redhat.com> > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-Comment-Date: Thu, 19 Jul 2018 09:47:40 +0000 > Gerrit-HasComments: No -- Didi

2 3