May 2018 - Infra - oVirt List Archives

Build failed in Jenkins: system-mk_mirrors_index-yum #29048
by jenkins＠jenkins.phx.ovirt.org 02 May '18

02 May '18

See <http://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/29048/display/redi…> ------------------------------------------ Started by upstream project "system-sync_mirrors-fedora-base-fc25-x86_64" build number 1326 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 ef9aa7f132ae66930b6d5b50e846f0253dcbe2f7 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ef9aa7f132ae66930b6d5b50e846f0253dcbe2f7 Commit message: "Create fc28 mirror jobs" > git rev-list --no-walk ef9aa7f132ae66930b6d5b50e846f0253dcbe2f7 # timeout=10 [system-mk_mirrors_index-yum] $ /bin/bash -xe /tmp/jenkins4763381836278420349.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.yaml’: 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.py’: No space left on device Released lock: latest_lists_yum Build step 'Execute shell' marked build as failure

1 2

[JIRA] (OVIRT-1990) Setup a change-queue for oVirt 4.2.3
by Barak Korren (oVirt JIRA) 02 May '18

02 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1990?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1990: ----------------------------------- Assignee: Barak Korren (was: infra) > Setup a change-queue for oVirt 4.2.3 > ------------------------------------ > > Key: OVIRT-1990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1990 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > Singe engine now branched into 4.2.3, we may need a new CQ to test it. > Making a CQ involves: > # Making new OST suites for it > # Making the CQ itself. > This is a super-ticket that will be used to track smaller tickets to work on this -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-1990) Setup a change-queue for oVirt 4.2.3
by Barak Korren (oVirt JIRA) 02 May '18

02 May '18

Barak Korren created OVIRT-1990: ----------------------------------- Summary: Setup a change-queue for oVirt 4.2.3 Key: OVIRT-1990 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1990 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: Highest Singe engine now branched into 4.2.3, we may need a new CQ to test it. Making a CQ involves: # Making new OST suites for it # Making the CQ itself. This is a super-ticket that will be used to track smaller tickets to work on this -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-1990) Setup a change-queue for oVirt 4.2.3
by Barak Korren (oVirt JIRA) 02 May '18

02 May '18

This is a multi-part message in MIME format... ------------=_1525268643-23560-161 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1990?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1990: -------------------------------- Epic Link: OVIRT-400 > Setup a change-queue for oVirt 4.2.3 > ------------------------------------ > > Key: OVIRT-1990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1990 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Singe engine now branched into 4.2.3, we may need a new CQ to test it. > Making a CQ involves: > # Making new OST suites for it > # Making the CQ itself. > This is a super-ticket that will be used to track smaller tickets to work on this -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083) ------------=_1525268643-23560-161 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1990?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1990:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Setup a change-queue for oVirt 4.2.3</h3> <pre> Key: OVIRT-1990 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1990 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Change Queue Reporter: Barak Korren Assignee: infra Priority: Highest</pre> <p>Singe engine now branched into 4.2.3, we may need a new CQ to test it. Making a CQ involves: # Making new OST suites for it # Making the CQ itself. This is a super-ticket that will be used to track smaller tickets to work on this</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1525268643-23560-161--

1 0

Broken deps wihle testing master? Here some info
by Sandro Bonazzola 02 May '18

02 May '18

Hi, ovirt-release-master enables testing repos from CentOS. Testing repos are now switching to CentOS 7.5.1804 so you now need to enable also the CR repo when testing master on CentOS. CentOS 7.5 should be released this week or in worst case next week, so this is just a temporary issue while 7.5 is being rolled out. oVirt release 4.2 uses stable repos and is not affected by this temporary glitch. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

[JIRA] (OVIRT-1989) remove old Fedora mirrors
by Evgheni Dereveanchin (oVirt JIRA) 02 May '18

02 May '18

This is a multi-part message in MIME format... ------------=_1525264444-19614-211 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1989: ------------------------------------------- Summary: remove old Fedora mirrors Key: OVIRT-1989 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1989 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low Fedora 28 is out, opening the ticket to review and remove old mirrors of previous versions. Current Fedora mirrors and their disk usage: |38G|/var/www/html/repos/yum/fedora-base-fc25| |22G |/var/www/html/repos/yum/fedora-updates-fc25| |68G |/var/www/html/repos/yum/fedora-base-fc26| |66G |/var/www/html/repos/yum/fedora-updates-fc26| |48G |/var/www/html/repos/yum/fedora-base-fc27| |62G |/var/www/html/repos/yum/fedora-updates-fc27| |92G |/var/www/html/repos/yum/fedora-base-fcraw| We do not seem to have any Fedora 25 jobs left in CI so at least that version can be easily removed. Also worth flushing fcraw as it likely contains lots of outdated package versions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083) ------------=_1525264444-19614-211 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1989:</h3> <pre> Summary: remove old Fedora mirrors Key: OVIRT-1989 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1989 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low</pre> <p>Fedora 28 is out, opening the ticket to review and remove old mirrors of previous versions.</p> <p>Current Fedora mirrors and their disk usage:</p> <p>|38G|/var/www/html/repos/yum/fedora-base-fc25| |22G |/var/www/html/repos/yum/fedora-updates-fc25| |68G |/var/www/html/repos/yum/fedora-base-fc26| |66G |/var/www/html/repos/yum/fedora-updates-fc26| |48G |/var/www/html/repos/yum/fedora-base-fc27| |62G |/var/www/html/repos/yum/fedora-updates-fc27| |92G |/var/www/html/repos/yum/fedora-base-fcraw|</p> <p>We do not seem to have any Fedora 25 jobs left in CI so at least that version can be easily removed. Also worth flushing fcraw as it likely contains lots of outdated package versions.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1525264444-19614-211--

1 0

[oVirt CI] standard-enqueue - Build #13037 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 02 May '18

02 May '18

------=_Part_465_1268574334.1525254821508 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/13037/ Build Name: #13037 Build Description: Gerrit: 90818 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/90818 - title: Showing pop-up on click of volume snapshot New button - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Gobinda <godas(a)redhat.com> ------=_Part_465_1268574334.1525254821508--

1 2

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 127 - Failure!
by jenkins＠jenkins.phx.ovirt.org 02 May '18

02 May '18

------=_Part_455_805508777.1525224928259 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/127/ Build Number: 127 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #127 [Yaniv Kaul] You cannot pin a VM with vNUMA to more than 1 host. This is not good for ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: False != True after 180 seconds 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-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 202, in snapshot_merge lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 267, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 251, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 180 seconds ------=_Part_455_805508777.1525224928259--

1 1

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py
by Daniel Belenky (oVirt JIRA) 02 May '18

02 May '18

This is a multi-part message in MIME format... ------------=_1525247059-30270-371 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1988: ---------------------------------- Epic Link: OVIRT-400 > Add default behavior in secret_resolvers.py > ------------------------------------------- > > Key: OVIRT-1988 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > Currently, when users try to run CI locally (currently with mock_runner), > if their project has a secret dependency they have to either write a local > secrets file, or to temporary modify their environment.yaml. > The file format should have support for default behavior in case a secret > was not found. Maybe something similar to: > {code:java} > --- > - name: MY_SECRET > valueFrom: > secretKeyRef: > name: secret_name > key: key_from_secret > default: > from-env: ENV_VAR_NAME > # OR > value: default-value > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083) ------------=_1525247059-30270-371 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1988:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Add default behavior in secret_resolvers.py</h3> <pre> Key: OVIRT-1988 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Daniel Belenky Assignee: infra</pre> <h3>Currently, when users try to run CI locally (currently with mock_runner), if their project has a secret dependency they have to either write a local secrets file, or to temporary modify their environment.yaml. The file format should have support for default behavior in case a secret was not found. Maybe something similar to: {code:java}</h3> <ul><li><p>name: MY_SECRET valueFrom:</p> <pre>secretKeyRef: name: secret_name key: key_from_secret default: from-env: ENV_VAR_NAME # OR value: default-value</pre></li></ul> <p>{code}</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1525247059-30270-371--

1 0

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py
by Daniel Belenky (oVirt JIRA) 02 May '18

02 May '18

Daniel Belenky created OVIRT-1988: ------------------------------------- Summary: Add default behavior in secret_resolvers.py Key: OVIRT-1988 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Daniel Belenky Assignee: infra Currently, when users try to run CI locally (currently with mock_runner), if their project has a secret dependency they have to either write a local secrets file, or to temporary modify their environment.yaml. The file format should have support for default behavior in case a secret was not found. Maybe something similar to: {code:java} --- - name: MY_SECRET valueFrom: secretKeyRef: name: secret_name key: key_from_secret default: from-env: ENV_VAR_NAME # OR value: default-value {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0