March 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1251) create status.ovirt.org

by eyal edri [Administrator] (oVirt JIRA)

eyal edri [Administrator] created OVIRT-1251: ------------------------------------------------ Summary: create status.ovirt.org Key: OVIRT-1251 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra Similar to other projects: https://status.newrelic.com/ https://status.centos.org/ It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

7 years, 6 months

1
0
0 / 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.pl... ] eyal edri [Administrator] updated OST-39: ----------------------------------------- Status: In Review (was: To Do) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

7 years, 6 months

1
0
0 / 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.pl... ] eyal edri [Administrator] commented on OST-39: ---------------------------------------------- still trying to move it to blocked status, please ignore for now. > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

7 years, 6 months

1
0
0 / 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.pl... ] eyal edri [Administrator] updated OST-39: ----------------------------------------- Status: To Do (was: In Review) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

7 years, 6 months

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #146

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/146/disp...> ------------------------------------------ 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 ed4375cef5aea05f4940a81483eda9488f364078 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ed4375cef5aea05f4940a81483eda9488f364078 > git rev-list ed4375cef5aea05f4940a81483eda9488f364078 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson21156725790525527.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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1429, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 911, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 899, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

7 years, 6 months

1
1
0 / 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5783 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_11_521338780.1489294534269 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5783/, Build Number: 5783, Build Status: FAILURE ------=_Part_11_521338780.1489294534269--

7 years, 6 months

1
1
0 / 0

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 07/02/17 ] [ add_secondary_storage_domains ]

by Nir Soffer

Is this 4.1 or 4.0 test? These vdsm logs are in 4.0 format. בתאריך 7 במרץ 2017 10:17 לפנה״צ,‏ "Yaniv Kaul" <ykaul(a)redhat.com> כתב: On Tue, Mar 7, 2017 at 9:44 AM Daniel Belenky <dbelenky(a)redhat.com> wrote: > *Test failed:* add_secondary_storage_domains > > *Link to failed Job: *test-repo_ovirt_experimental_4.1/889 > <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exp...> > > *Link to all logs: *logs from Jenkins > <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exp...> > > *Error snippet from log:* > > 2017-03-07 01:29:03,789::utils.py::_ret_via_queue::59::lago.utils::ERROR::Error > while running thread > > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in _ret_via_queue > queue.put({'return': func()}) > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 574, in add_iso_storage_domain > add_generic_nfs_storage_domain(prefix, SD_ISO_NAME, SD_ISO_HOST_NAME, SD_ISO_PATH, sd_format='v1', sd_type='iso', nfs_version='v3') > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 437, in add_generic_nfs_storage_domain > add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version) > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 493, in add_generic_nfs_storage_domain_4 > _add_storage_domain_4(api, p) > File "/home/jenkins/workspace/test-repo_ovirt_experimental_4.1/ovirt-system-tests/basic-suite-4.1/test-scenarios/002_bootstrap.py", line 407, in _add_storage_domain_4 > id=sd.id, > File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 3488, in add > self._check_fault(response) > File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 98, in _check_fault > Service._raise_error(response, fault) > File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 71, in _raise_error > raise Error(msg) > Error: Fault reason is "Operation Failed". Fault detail is "[Storage domain cannot be reached. Please ensure it is accessible from the host(s).]". HTTP response code is 400. > > Looking at http://jenkins.ovirt.org/view/experimental%20jobs/job/ test-repo_ovirt_experimental_4.1/889/artifact/exported- artifacts/basic-suit-4.1-el7/test_logs/basic-suite-4.1/ post-002_bootstrap.py/lago-basic-suite-4-1-host1/_var_log/vdsm/supervdsm.log : I don't see the return of the mount command: MainProcess|jsonrpc/3::DEBUG::2017-03-06 20:26:01,872::supervdsmServer: :93::SuperVdsm.ServerCallback::(wrapper) call mount with (u'192.168.201.2: /exports/nfs/iso', u'/rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso') {'vfstype': 'nfs', 'mntOpts': 'soft,nosharecache,timeo=600,retrans=6,nfsvers=3', 'timeout': None, 'cgroup': None} MainProcess|jsonrpc/3::DEBUG::2017-03-06 20:26:01,872::commands::69::root::(execCmd) /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 192.168.201.2:/exports/nfs/iso /rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso (cwd None) MainProcess|jsonrpc/4::DEBUG::2017-03-06 20:29:02,501::supervdsmServer: :93::SuperVdsm.ServerCallback::(wrapper) call hbaRescan with () {} MainProcess|jsonrpc/4::DEBUG::2017-03-06 20:29:02,501::commands::69::storage.HBA::(execCmd) /usr/bin/taskset --cpu-list 0-1 /usr/libexec/vdsm/fc-scan (cwd None) MainProcess|jsonrpc/4::DEBUG::2017-03-06 20:29:02,573::supervdsmServer: :100::SuperVdsm.ServerCallback::(wrapper) return hbaRescan with None ... (I don't know why we do all those hbaRescan, but that's unrelated) Where on host0 it does return: MainProcess|jsonrpc/5::DEBUG::2017-03-06 20:25:20,369::supervdsmServer::93::SuperVdsm.ServerCallback::(wrapper) call mount with (u'192.168.201.2:/exports/nfs/iso', u'/rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso') {'vfstype': 'nfs', 'mntOpts': 'soft,nosharecache,timeo=600,retrans=6,nfsvers=3', 'timeout': None, 'cgroup': None} MainProcess|jsonrpc/5::DEBUG::2017-03-06 20:25:20,369::commands::69::root::(execCmd) /usr/bin/taskset --cpu-list 0-1 /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6,nfsvers=3 192.168.201.2:/exports/nfs/iso /rhev/data-center/mnt/192.168.201.2:_exports_nfs_iso (cwd None) MainProcess|jsonrpc/5::DEBUG::2017-03-06 20:25:20,504::supervdsmServer::100::SuperVdsm.ServerCallback::(wrapper) return mount with None On the storage server, both requests are seen: Mar 6 20:25:20 lago-basic-suite-4-1-engine rpc.mountd[4279]: authenticated mount request from 192.168.201.4:970 for /exports/nfs/iso (/exports/nfs/iso) Mar 6 20:26:01 lago-basic-suite-4-1-engine rpc.mountd[4279]: authenticated mount request from 192.168.201.3:948 for /exports/nfs/iso (/exports/nfs/iso) -- > > *Daniel Belenky* > > *RHV DevOps* > > *Red Hat Israel* > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

7 years, 6 months

2
3
0 / 0

oVirt infra daily report - unstable production jobs - 255

by jenkins＠jenkins.phx.ovirt.org

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

7 years, 6 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 254

by jenkins＠jenkins.phx.ovirt.org

------=_Part_2_1955332907.1489186819044 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/254//artifact/exported... Cheers, Jenkins ------=_Part_2_1955332907.1489186819044 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 10/03/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x8...">ovirt-system-tests_master_check-patch-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  NOT STABLE YET </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/">ovirt_4.1_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/">repos_4.1_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc25_merged/">repos_master_check-closure_fc25_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.  </td></tr> ------=_Part_2_1955332907.1489186819044--

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages

by Pavel Zhukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jir... ] Pavel Zhukov updated OVIRT-1250: -------------------------------- Issue Type: Bug (was: Improvement) > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.1#100035)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra March 2017