- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 262 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Jun '18

06 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/262/ Build Number: 262 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #262 [Yuval Turgeman] Added ovirt-node-ng suite that deploys HE [Sandro Bonazzola] ovirt-engine-extension: drop fc27 [Yuval Turgeman] Add imgbased to stdci-v2 [Sandro Bonazzola] releng-tools: add automation [Sandro Bonazzola] ovirt-imageio: move to fc28 ----------------- Failed Tests: ----------------- No tests ran.

1 15

[CQ]: 91614,10 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 06 Jun '18

06 Jun '18

Change 91614,10 (ovirt-provider-ovn) 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/91614/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2312/

1 0

oVirt infra weekly meeting notes 06.06.2018
by Evgheni Dereveanchin 06 Jun '18

06 Jun '18

Hi everyone, Please find the topics of this week's infra meeting below: *PHX - PHX Engine upgraded to 4.2.3- HE Storage migration under review: OVIRT-2075 <https://ovirt-jira.atlassian.net/browse/OVIRT-2075>- FC26 <https://jenkins.ovirt.org/label/fc26/> slaves to be replaced with FC28 <https://jenkins.ovirt.org/label/fc28/>: OVIRT-2017 <https://ovirt-jira.atlassian.net/browse/OVIRT-2017>- Add to staging first- Disable all other slaves on staging- Test with github and gerrit triggers- Invoke dummy change queue- Grafana updated to FC28- SSL missing on several systems:- mirrors.phx- graphite.phxOther topics: - Gerrit slowness reported again: OVIRT-2143 <https://ovirt-jira.atlassian.net/browse/OVIRT-2143>- Verify if git pack is needed- Verify if postgres vacuuming- Ask Roy for advice on Java performance troubleshooting- Review hosted Gerrit solutions like gerrithub- Alterway02 crashed this week, need to move to OSAS: OVIRT-502 <https://ovirt-jira.atlassian.net/browse/OVIRT-502>* -- Regards, Evgheni Dereveanchin

1 0

[JIRA] (OVIRT-2000) Upgrade badge-plugin to at least 1.3
by Barak Korren (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2000?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2000: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Upgrade badge-plugin to at least 1.3 > ------------------------------------ > > Key: OVIRT-2000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Master > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > We need to upgrade the badge-plugin, see OVIRT-1998 about the motivation to do it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2147) Add docker to OST requirements
by Gal Ben Haim (oVirt JIRA) 06 Jun '18

06 Jun '18

Gal Ben Haim created OVIRT-2147: ----------------------------------- Summary: Add docker to OST requirements Key: OVIRT-2147 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2147 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra - Explain in the docs that docker is needed because of the UI tests. - Verify in run_suite that docker is available. We can use the "requirements" section in the suite's vars file that docker is needed (or implement more generic requirement). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2146) Add ability to run build_reposync_config.sh with two images
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

Dafna Ron created OVIRT-2146: -------------------------------- Summary: Add ability to run build_reposync_config.sh with two images Key: OVIRT-2146 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2146 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra we currently only able to run build_reposync_config.sh with two images which is good when we have only image per a release. however, if we need to run engine and hosts with different distros it would help if we can run it with two images/assign an image to a specific machine (host with image x and engine with image y) when running the tool. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2145) Jenkins.ovirt Permissions request
by eyal edri (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2145?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2145: -------------------------------- Assignee: Gal Ben Haim (was: infra) > Jenkins.ovirt Permissions request > --------------------------------- > > Key: OVIRT-2145 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2145 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: Gal Zaidman > Assignee: Gal Ben Haim > > Hey, > I'd like to get developer permissions for my user gzaidman on jenkins.ovirt > thanks, Gal -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2145) Jenkins.ovirt Permissions request
by Gal Zaidman (oVirt JIRA) 06 Jun '18

06 Jun '18

Gal Zaidman created OVIRT-2145: ---------------------------------- Summary: Jenkins.ovirt Permissions request Key: OVIRT-2145 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2145 Project: oVirt - virtualization made easy Issue Type: Task Components: Jenkins Master Reporter: Gal Zaidman Assignee: infra Hey, I'd like to get developer permissions for my user gzaidman on jenkins.ovirt thanks, Gal -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2131: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2131: ---------------------------------- I think this is an external repo which we should be re-blocking by reverting change that eyal did. > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2131: ----------------------------- Labels: cq-issue-traking ost_failures ost_infra (was: cq-issue-traking ost_failures ost_infra ost_race) > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2131: ----------------------------- Labels: cq-issue-traking ost_failures ost_infra ost_race (was: cq-issue-traking ost_failures ost_infra) > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra, ost_race > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4
by Barak Korren (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2141?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2141: ------------------------------------- [~dron] I think you should already make a ticket tracking race conditions on the relevant test and link it as a "causes" ticket to this one. > dwh fails on prepare_migration_attachments_ipv4 > ------------------------------------------------ > > Key: OVIRT-2141 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > Change 91956,1 (ovirt-dwh) 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/91956/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ > I cannot see an actual error. > I suspect that the issue is that we fail to get stats at times: > GetStatsAsyncVDSCommand(HostName = lago-basic-suite-4-2-host-0 > the host become non-responsive and tests fail. > I re-added the change since I want to see if it fails again on the same issue. > however, we still need to look into why the vds is not responding. > I kept the build so that we can look at logs: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2141?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2141: ----------------------------- Resolution: Fixed Status: Done (was: To Do) race condition > dwh fails on prepare_migration_attachments_ipv4 > ------------------------------------------------ > > Key: OVIRT-2141 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > Change 91956,1 (ovirt-dwh) 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/91956/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ > I cannot see an actual error. > I suspect that the issue is that we fail to get stats at times: > GetStatsAsyncVDSCommand(HostName = lago-basic-suite-4-2-host-0 > the host become non-responsive and tests fail. > I re-added the change since I want to see if it fails again on the same issue. > however, we still need to look into why the vds is not responding. > I kept the build so that we can look at logs: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2141?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2141: ---------------------------------- the change passed on the second time. this seemed to have been a race condition. closing this for now but if happens again we should look closer at the test. > dwh fails on prepare_migration_attachments_ipv4 > ------------------------------------------------ > > Key: OVIRT-2141 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > Change 91956,1 (ovirt-dwh) 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/91956/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ > I cannot see an actual error. > I suspect that the issue is that we fail to get stats at times: > GetStatsAsyncVDSCommand(HostName = lago-basic-suite-4-2-host-0 > the host become non-responsive and tests fail. > I re-added the change since I want to see if it fails again on the same issue. > however, we still need to look into why the vds is not responding. > I kept the build so that we can look at logs: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4
by Dafna Ron (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2141?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2141: ----------------------------- Labels: ost_failures ost_infra ost_race (was: ost_failures) > dwh fails on prepare_migration_attachments_ipv4 > ------------------------------------------------ > > Key: OVIRT-2141 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > Change 91956,1 (ovirt-dwh) 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/91956/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ > I cannot see an actual error. > I suspect that the issue is that we fail to get stats at times: > GetStatsAsyncVDSCommand(HostName = lago-basic-suite-4-2-host-0 > the host become non-responsive and tests fail. > I re-added the change since I want to see if it fails again on the same issue. > however, we still need to look into why the vds is not responding. > I kept the build so that we can look at logs: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91968, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Jun '18

06 Jun '18

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

1 0

[JIRA] (OVIRT-2144) Extend "build_reposync_config.sh" to support a suite as an input
by Gal Ben Haim (oVirt JIRA) 06 Jun '18

06 Jun '18

Gal Ben Haim created OVIRT-2144: ----------------------------------- Summary: Extend "build_reposync_config.sh" to support a suite as an input Key: OVIRT-2144 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2144 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Gal Ben Haim Assignee: infra As an OST maintainer, I would like to generate a reposync--config for a suite, without getting into the low level details such as lago-image, lago-repo, which packages the suite uses etc... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2143) gerrit.ovirt.org response time
by eyal edri (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2143?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2143: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > gerrit.ovirt.org response time > ------------------------------ > > Key: OVIRT-2143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2143 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Eitan Raviv > Assignee: Evgheni Dereveanchin > Priority: High > > Hi, > In the past few weeks me and other team members are experiencing > considerable slowness in response time of the gerrit.ovirt.org GUI app > in the browser when fetching a patch summary page or one of the files > in the patch. Wait times of up to 15 seconds are not uncommon even for > small patches, and up to a 50 sec delay was experienced today with > recently closed patches from the past week. > Any help would be highly appreciated. > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2143) gerrit.ovirt.org response time
by eyal edri (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2143?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2143: ----------------------------- Issue Type: Outage (was: By-EMAIL) > gerrit.ovirt.org response time > ------------------------------ > > Key: OVIRT-2143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2143 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Eitan Raviv > Assignee: infra > Priority: High > > Hi, > In the past few weeks me and other team members are experiencing > considerable slowness in response time of the gerrit.ovirt.org GUI app > in the browser when fetching a patch summary page or one of the files > in the patch. Wait times of up to 15 seconds are not uncommon even for > small patches, and up to a 50 sec delay was experienced today with > recently closed patches from the past week. > Any help would be highly appreciated. > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2143) gerrit.ovirt.org response time
by eyal edri (oVirt JIRA) 06 Jun '18

06 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2143?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2143: ----------------------------- Priority: High (was: Medium) > gerrit.ovirt.org response time > ------------------------------ > > Key: OVIRT-2143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2143 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eitan Raviv > Assignee: infra > Priority: High > > Hi, > In the past few weeks me and other team members are experiencing > considerable slowness in response time of the gerrit.ovirt.org GUI app > in the browser when fetching a patch summary page or one of the files > in the patch. Wait times of up to 15 seconds are not uncommon even for > small patches, and up to a 50 sec delay was experienced today with > recently closed patches from the past week. > Any help would be highly appreciated. > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 90802, 14 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Jun '18

06 Jun '18

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

1 0

[JIRA] (OVIRT-2143) gerrit.ovirt.org response time
by Eitan Raviv (oVirt JIRA) 06 Jun '18

06 Jun '18

Eitan Raviv created OVIRT-2143: ---------------------------------- Summary: gerrit.ovirt.org response time Key: OVIRT-2143 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2143 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Eitan Raviv Assignee: infra Hi, In the past few weeks me and other team members are experiencing considerable slowness in response time of the gerrit.ovirt.org GUI app in the browser when fetching a patch summary page or one of the files in the patch. Wait times of up to 15 seconds are not uncommon even for small patches, and up to a 50 sec delay was experienced today with recently closed patches from the past week. Any help would be highly appreciated. Thanks Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 235 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Jun '18

06 Jun '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/235/ Build Number: 235 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #235 [Eyal Edri] Refresh ovirt-master reposync with latest pkgs ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 91959, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Jun '18

06 Jun '18

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

1 0

[JIRA] (OVIRT-2142) Add info about the "reposync builder" tool to the docs
by Gal Ben Haim (oVirt JIRA) 06 Jun '18

06 Jun '18

Gal Ben Haim created OVIRT-2142: ----------------------------------- Summary: Add info about the "reposync builder" tool to the docs Key: OVIRT-2142 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2142 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Gal Ben Haim Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1552
by jenkins＠jenkins.phx.ovirt.org 06 Jun '18

06 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1552/displ…> Changes: [Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch [Sandro Bonazzola] ovirt-release: switch to fc28 [Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org" ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 12e9d5a2a03ed2f83187aecdffb67ad8cbcfc4ba (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 12e9d5a2a03ed2f83187aecdffb67ad8cbcfc4ba Commit message: "OST: pin HC suites to "ovirt-srv05.phx.ovirt.org"" > git rev-list --no-walk 5cb82835887b96781c1ec5514c0309078f60d3f2 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins816805244158341348.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 2

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 452 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Jun '18

06 Jun '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/452/ Build Number: 452 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #452 [Eyal Edri] Refresh ovirt-master reposync with latest pkgs [Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch [Sandro Bonazzola] ovirt-release: switch to fc28 [Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org" ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 90688, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[CQ]: 91809, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[CQ]: 91844, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[CQ]: 91927, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 232 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Jun '18

05 Jun '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/232/ Build Number: 232 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #232 [Eyal Edri] Refresh ovirt-master reposync with latest pkgs ----------------- Failed Tests: ----------------- No tests ran.

1 2

[CQ]: 91949, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2141?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2141: ----------------------------- Issue Type: Bug (was: Task) > dwh fails on prepare_migration_attachments_ipv4 > ------------------------------------------------ > > Key: OVIRT-2141 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91956,1 (ovirt-dwh) 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/91956/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ > I cannot see an actual error. > I suspect that the issue is that we fail to get stats at times: > GetStatsAsyncVDSCommand(HostName = lago-basic-suite-4-2-host-0 > the host become non-responsive and tests fail. > I re-added the change since I want to see if it fails again on the same issue. > however, we still need to look into why the vds is not responding. > I kept the build so that we can look at logs: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2141) dwh fails on prepare_migration_attachments_ipv4
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

Dafna Ron created OVIRT-2141: -------------------------------- Summary: dwh fails on prepare_migration_attachments_ipv4 Key: OVIRT-2141 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2141 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra Change 91956,1 (ovirt-dwh) 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/91956/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ I cannot see an actual error. I suspect that the issue is that we fail to get stats at times: GetStatsAsyncVDSCommand(HostName = lago-basic-suite-4-2-host-0 the host become non-responsive and tests fail. I re-added the change since I want to see if it fails again on the same issue. however, we still need to look into why the vds is not responding. I kept the build so that we can look at logs: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2299/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2140: ---------------------------------------- Issue Type: Improvement (was: Bug) > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 05 Jun '18

05 Jun '18

Evgheni Dereveanchin created OVIRT-2140: ------------------------------------------- Summary: enforce SSL on resources.ovirt.org Key: OVIRT-2140 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2139) enforce SSL on jenkins.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 05 Jun '18

05 Jun '18

Evgheni Dereveanchin created OVIRT-2139: ------------------------------------------- Summary: enforce SSL on jenkins.ovirt.org Key: OVIRT-2139 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2139 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra SSL was enabled on Jenkins with OVIRT-1471, this ticket is to transform the non-SSL virtual host into a redirect to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91919, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[CQ]: 91956,1 (ovirt-dwh) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2092: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > standard-enqueue 4.2 not running > -------------------------------- > > Key: OVIRT-2092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > but the tested is showing that it only ran once (yesterday): > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > and "next test" job is showing empty queue: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2137) default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2137?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2137: -------------------------------- Assignee: Dafna Ron (was: infra) > default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND > --------------------------------------------------------------------- > > Key: OVIRT-2137 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2137 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: cq-issue-traking, ost_code_regression, ost_failures > > Change 91888,3 (ovirt-engine) is probably the reason behind recent system test > failures in the "ovirt-master" change queue and needs to be fixed. > This change had been removed from the testing queue. Artifacts build from this > change will not be released until it is fixed. > For further details about the change see: > https://gerrit.ovirt.org/#/c/91888/3 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/ > I think that we are sending a request to cpu and because of the change done on NULL strings we are failing to get type of cpu which fails the test: > ' 2018-06-04 11:57:19,852-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' > 2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Compiled stored procedure. Call string is [{call getvdsbyclusteri > d(?, ?, ?)}] > 2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] SqlCall for procedure [GetVdsByClusterId] compiled > 2018-06-04 11:57:19,878-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: getAllForCluster, params: [9cbb05e6-680f-11e8-b07e-5452c0a8c904], timeE > lapsed: 25ms > 2018-06-04 11:57:19,879-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUST > ER,VAR__ACTION__UPDATE,VAR__TYPE__CLUSTER,ACTION_TYPE_FAILED_CPU_NOT_FOUND > 2018-06-04 11:57:19,881-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' > 2018-06-04 11:57:19,881-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationP > arameters:{commandId='36bf82e7-eec8-4b36-99af-db5ade902593', user='null', commandType='Unknown'}], timeElapsed: 58ms > 2018-06-04 11:57:19,886-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-6) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] > ' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2138) Revert "open external repos for master until centos 7.5 calms down"
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

Dafna Ron created OVIRT-2138: -------------------------------- Summary: Revert "open external repos for master until centos 7.5 calms down" Key: OVIRT-2138 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2138 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra I created the ticket but need to make sure it passes CI before merging: https://gerrit.ovirt.org/#/c/91936/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2137) default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

Dafna Ron created OVIRT-2137: -------------------------------- Summary: default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND Key: OVIRT-2137 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2137 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Change 91888,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/91888/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/ I think that we are sending a request to cpu and because of the change done on NULL strings we are failing to get type of cpu which fails the test: ' 2018-06-04 11:57:19,852-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Compiled stored procedure. Call string is [{call getvdsbyclusteri d(?, ?, ?)}] 2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] SqlCall for procedure [GetVdsByClusterId] compiled 2018-06-04 11:57:19,878-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: getAllForCluster, params: [9cbb05e6-680f-11e8-b07e-5452c0a8c904], timeE lapsed: 25ms 2018-06-04 11:57:19,879-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUST ER,VAR__ACTION__UPDATE,VAR__TYPE__CLUSTER,ACTION_TYPE_FAILED_CPU_NOT_FOUND 2018-06-04 11:57:19,881-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2018-06-04 11:57:19,881-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationP arameters:{commandId='36bf82e7-eec8-4b36-99af-db5ade902593', user='null', commandType='Unknown'}], timeElapsed: 58ms 2018-06-04 11:57:19,886-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-6) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] ' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
by Barak Korren (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2136?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2136: ----------------------------------- Assignee: Barak Korren (was: infra) > Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer > --------------------------------------------------------------- > > Key: OVIRT-2136 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: danken > Assignee: Barak Korren > > Please add Milan to vdsm-maintainers list. > ---------- Forwarded message ---------- > From: Edward Haas <ehaas(a)redhat.com> > Date: Mon, Jun 4, 2018 at 3:35 PM > Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer > To: "devel(a)ovirt.org" <devel(a)ovirt.org> > Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas > <edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg > <danken(a)redhat.com> > +1 > Thanks, > Edy. > > On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote: > > > > Approved. > > > > On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski > > <piotr.kliczewski(a)gmail.com> wrote: > >> +1 > >> > >>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote: > >>> > >>> > >>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >>>> > >>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com> > >>>> wrote: > >>>>> > >>>>> Hi all, > >>>>> > >>>>> Milan Zamazal has been working on the oVirt project for more than 2.5 > >>>>> years. > >>>>> Let me highlight some of his many contributions to the project: > >>>>> > >>>>> - Since January this year - 2018, he's been a maintainer for the stable > >>>>> branches. > >>>>> - He developed important features like memory hotunplug, which required > >>>>> tight cooperation > >>>>> and communication with the other layers of the stack (libvirt, qemu). > >>>>> - He is a mentor in the Outreachy program, which lead to creation of the > >>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer > >>>>> - He contributed more than 290 patches to the Vdsm project in master > >>>>> branch alone, excluding backports and contributions to Engine > >>>>> - He contributed and is contributing testcases and fixes to the oVirt > >>>>> System Test suite, a tool which was already pivotal in ensuring the > >>>>> quality of the oVirt project. > >>>>> > >>>>> As reviewer, Milan is responsive and his comments are always > >>>>> comprehensive and well focused, > >>>>> with strong attitude towards getting things done and done right. > >>>>> > >>>>> Milan also demonstrated his ability to adapt to the needs of the project: > >>>>> - he demonstrated careful and thoughtful patch management while > >>>>> maintaining the stable branches > >>>>> - he also demonstrated he's not shy to tackle large and needed changes > >>>>> during the 4.1 and 4.2 cycles, > >>>>> when we deeply reorganized the XML processing in the virt code. > >>>>> > >>>>> For those reasons, and many more, I think he will be a good addition to > >>>>> the maintainers team, and I propose him as virt co-maintainer. > >>>>> > >>>>> Please share your thoughts > >>>> > >>>> > >>>> +1 > >>> > >>> > >>> FWIW, +1 > >>> > >>>> > >>>> > >>>> Nir > >>>> > >>>> > >>>> _______________________________________________ > >>>> 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/QELJ7YNZVW65H… > >>>> > >>> > >>> > >>> _______________________________________________ > >>> 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/YIMB6QHQ37DVL… > >>> > >> _______________________________________________ > >> 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/YBK7IHQELSEFN… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
by Barak Korren (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2136?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2136: -------------------------------- Component/s: Gerrit/git > Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer > --------------------------------------------------------------- > > Key: OVIRT-2136 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: danken > Assignee: infra > > Please add Milan to vdsm-maintainers list. > ---------- Forwarded message ---------- > From: Edward Haas <ehaas(a)redhat.com> > Date: Mon, Jun 4, 2018 at 3:35 PM > Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer > To: "devel(a)ovirt.org" <devel(a)ovirt.org> > Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas > <edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg > <danken(a)redhat.com> > +1 > Thanks, > Edy. > > On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote: > > > > Approved. > > > > On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski > > <piotr.kliczewski(a)gmail.com> wrote: > >> +1 > >> > >>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote: > >>> > >>> > >>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >>>> > >>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com> > >>>> wrote: > >>>>> > >>>>> Hi all, > >>>>> > >>>>> Milan Zamazal has been working on the oVirt project for more than 2.5 > >>>>> years. > >>>>> Let me highlight some of his many contributions to the project: > >>>>> > >>>>> - Since January this year - 2018, he's been a maintainer for the stable > >>>>> branches. > >>>>> - He developed important features like memory hotunplug, which required > >>>>> tight cooperation > >>>>> and communication with the other layers of the stack (libvirt, qemu). > >>>>> - He is a mentor in the Outreachy program, which lead to creation of the > >>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer > >>>>> - He contributed more than 290 patches to the Vdsm project in master > >>>>> branch alone, excluding backports and contributions to Engine > >>>>> - He contributed and is contributing testcases and fixes to the oVirt > >>>>> System Test suite, a tool which was already pivotal in ensuring the > >>>>> quality of the oVirt project. > >>>>> > >>>>> As reviewer, Milan is responsive and his comments are always > >>>>> comprehensive and well focused, > >>>>> with strong attitude towards getting things done and done right. > >>>>> > >>>>> Milan also demonstrated his ability to adapt to the needs of the project: > >>>>> - he demonstrated careful and thoughtful patch management while > >>>>> maintaining the stable branches > >>>>> - he also demonstrated he's not shy to tackle large and needed changes > >>>>> during the 4.1 and 4.2 cycles, > >>>>> when we deeply reorganized the XML processing in the virt code. > >>>>> > >>>>> For those reasons, and many more, I think he will be a good addition to > >>>>> the maintainers team, and I propose him as virt co-maintainer. > >>>>> > >>>>> Please share your thoughts > >>>> > >>>> > >>>> +1 > >>> > >>> > >>> FWIW, +1 > >>> > >>>> > >>>> > >>>> Nir > >>>> > >>>> > >>>> _______________________________________________ > >>>> 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/QELJ7YNZVW65H… > >>>> > >>> > >>> > >>> _______________________________________________ > >>> 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/YIMB6QHQ37DVL… > >>> > >> _______________________________________________ > >> 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/YBK7IHQELSEFN… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by Barak Korren (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2078: ------------------------------------- This is beginning to look like an epic - at least the Gerrit and CI aspects should probably be dealt with separately. > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Barak Korren (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1834: ------------------------------------- {quote} I know that signal handling in Jenkins is a difficult task. Maybe let's change the job to wipe the workspace before running git? {quote} That would destroy all the caches we worked very hard to keep around, including the Git cache itself which cab be quite significant. As I already commented elsewhere, this is not an easy problem to solve in our current architecture: For V1 Jobs - because Jenkins freestyle jobs do not allow you to easily add functionality before the git cloning is performed. For V2 jobs - pipelines to not allow you to embed arbitrary shell scripts in the jobs so you need to clone the repo before you can run any meaningful preparation steps. This issue is essentially an aspect of what we call "the chicken and egg" issue where we have to prepare the Jenkins slave before we can clone any code to it, but we need the code to do the preparation. Our current direction for solving this long-term is to move the slave preparation steps out from the jobs (OVIRT-1984) > Jenkins failure - perhaps bad permissions > ----------------------------------------- > > Key: OVIRT-1834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01* > hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at > org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01* > at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at > hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* > at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* > at hudson.model.Run.execute(Run.java:1724)*10:53:01* at > hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at > hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01* > at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by: > hudson.plugins.git.GitException: Command "git clean -fdx" returned > status code 1:*10:53:01* stdout: Removing > basic-suite-master/LagoInitFile*10:53:01* Removing > basic-suite-master/extra_sources*10:53:01* Removing > basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing > basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing > basic-suite-master/test_utils/constants.pyc*10:53:01* Removing > basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing > exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* > Removing mock_script_sid.x4jv1R*10:53:01* Removing > mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning: > failed to remove .pki/*10:53:01* warning: failed to remove > deployment-basic-suite-master/default/uuid*10:53:01* warning: failed > to remove deployment-basic-suite-master/default/id_rsa > ... > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
by danken (oVirt JIRA) 05 Jun '18

05 Jun '18

danken created OVIRT-2136: ----------------------------- Summary: Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer Key: OVIRT-2136 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra Please add Milan to vdsm-maintainers list. ---------- Forwarded message ---------- From: Edward Haas <ehaas(a)redhat.com> Date: Mon, Jun 4, 2018 at 3:35 PM Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer To: "devel(a)ovirt.org" <devel(a)ovirt.org> Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas <edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg <danken(a)redhat.com> +1 Thanks, Edy. > On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote: > > Approved. > > On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski > <piotr.kliczewski(a)gmail.com> wrote: >> +1 >> >>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote: >>> >>> >>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> >>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com> >>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> Milan Zamazal has been working on the oVirt project for more than 2.5 >>>>> years. >>>>> Let me highlight some of his many contributions to the project: >>>>> >>>>> - Since January this year - 2018, he's been a maintainer for the stable >>>>> branches. >>>>> - He developed important features like memory hotunplug, which required >>>>> tight cooperation >>>>> and communication with the other layers of the stack (libvirt, qemu). >>>>> - He is a mentor in the Outreachy program, which lead to creation of the >>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer >>>>> - He contributed more than 290 patches to the Vdsm project in master >>>>> branch alone, excluding backports and contributions to Engine >>>>> - He contributed and is contributing testcases and fixes to the oVirt >>>>> System Test suite, a tool which was already pivotal in ensuring the >>>>> quality of the oVirt project. >>>>> >>>>> As reviewer, Milan is responsive and his comments are always >>>>> comprehensive and well focused, >>>>> with strong attitude towards getting things done and done right. >>>>> >>>>> Milan also demonstrated his ability to adapt to the needs of the project: >>>>> - he demonstrated careful and thoughtful patch management while >>>>> maintaining the stable branches >>>>> - he also demonstrated he's not shy to tackle large and needed changes >>>>> during the 4.1 and 4.2 cycles, >>>>> when we deeply reorganized the XML processing in the virt code. >>>>> >>>>> For those reasons, and many more, I think he will be a good addition to >>>>> the maintainers team, and I propose him as virt co-maintainer. >>>>> >>>>> Please share your thoughts >>>> >>>> >>>> +1 >>> >>> >>> FWIW, +1 >>> >>>> >>>> >>>> Nir >>>> >>>> >>>> _______________________________________________ >>>> 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/QELJ7YNZVW65H… >>>> >>> >>> >>> _______________________________________________ >>> 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/YIMB6QHQ37DVL… >>> >> _______________________________________________ >> 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/YBK7IHQELSEFN… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0