June 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1432) Need to remove disk usage post build from STD-CI
by Gil Shinar (oVirt JIRA) 05 Jun '17

05 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1432?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1432: ----------------------------------- I looked at the Jenkins and saw that this plugin in pending uninstallation. This looks like a serious bug unless it is waiting for the next restart. [~ederevea] When are planing the next Jenkins restart? You need to meake sure that after the restart, this pluging had been uninstalled. If it hadn't been uninstalled, please try to manually remove the folder from the file-system and restart the service again. > Need to remove disk usage post build from STD-CI > ------------------------------------------------ > > Key: OVIRT-1432 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1432 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > Disk usage plugin sometimes causes jobs to run endlessly. > Today I have also seen that on the main Jenkins page, I can see builds that are still running and stuck on calculating disk space but if I look for this specific build in the job's page, it seems like it has been completed (either failed or succeeded). -- This message was sent by Atlassian JIRA (v1000.1026.0#100045)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7023 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jun '17

05 Jun '17

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

1 1

[JIRA] (OVIRT-1432) Need to remove disk usage post build from STD-CI
by Gil Shinar (oVirt JIRA) 05 Jun '17

05 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1432?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1432: ----------------------------------- I'm almost sure that Barak had told me that he is going to remove this plugin but looks like it is still there. > Need to remove disk usage post build from STD-CI > ------------------------------------------------ > > Key: OVIRT-1432 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1432 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > Disk usage plugin sometimes causes jobs to run endlessly. > Today I have also seen that on the main Jenkins page, I can see builds that are still running and stuck on calculating disk space but if I look for this specific build in the job's page, it seems like it has been completed (either failed or succeeded). -- This message was sent by Atlassian JIRA (v1000.1026.0#100045)

1 0

[JIRA] (OVIRT-1432) Need to remove disk usage post build from STD-CI
by Gil Shinar (oVirt JIRA) 05 Jun '17

05 Jun '17

Gil Shinar created OVIRT-1432: --------------------------------- Summary: Need to remove disk usage post build from STD-CI Key: OVIRT-1432 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1432 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gil Shinar Assignee: infra Disk usage plugin sometimes causes jobs to run endlessly. Today I have also seen that on the main Jenkins page, I can see builds that are still running and stuck on calculating disk space but if I look for this specific build in the job's page, it seems like it has been completed (either failed or succeeded). -- This message was sent by Atlassian JIRA (v1000.1026.0#100045)

1 0

[JIRA] (OVIRT-1431) Need a test projet in gerrit-staging
by rgolan＠redhat.com (oVirt JIRA) 05 Jun '17

05 Jun '17

rgolan(a)redhat.com created OVIRT-1431: ---------------------------------------- Summary: Need a test projet in gerrit-staging Key: OVIRT-1431 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1431 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: rgolan(a)redhat.com Assignee: infra Hi, Please create a test project under gerrit-staging and make me the admin in order to test changes in gerrit reviewer plugin. Thanks -- This message was sent by Atlassian JIRA (v1000.1026.0#100045)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7016 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jun '17

05 Jun '17

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

1 1

oVirt infra daily report - unstable production jobs - 343
by jenkins＠jenkins.phx.ovirt.org 05 Jun '17

05 Jun '17

------=_Part_462_1323508132.1496617205987 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/343//artifact/exported-a… Cheers, Jenkins ------=_Part_462_1323508132.1496617205987 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 - 04/06/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_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;hb=…"> jenkins</a> repo.  </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;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_462_1323508132.1496617205987--

1 0

[JIRA] (OVIRT-1430) docker images cleanup in mock_cleanup.sh is done wrong
by Daniel Belenky (oVirt JIRA) 04 Jun '17

04 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1430?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1430: ------------------------------------- Assignee: Daniel Belenky (was: infra) > docker images cleanup in mock_cleanup.sh is done wrong > ------------------------------------------------------ > > Key: OVIRT-1430 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1430 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > We've decided that for now, we'll keep a cache of images coming from centos|fedora official repositories. The cleanup is done by listing all the images which are not coming from those repositories and removing them. The bug is in the way we're listing and addressing images: we're addressing images by image id's, which might be shared between several tags. For instance: if I have a Dockerfile which builds a container from the official centos image and doesn't really change the image, and then I tag the image with a different name: tag, I'll get another reference for the official image, and the cleanup will remove it. > Another issue that might come up, is that we do have an image, but its tag has changed during the ran form 'latest' to something else. In this case, the cleanup will just fail the job as it won't have find the image with the different tag that have changed. -- This message was sent by Atlassian JIRA (v1000.1026.0#100045)

1 0

[JIRA] (OVIRT-1430) docker images cleanup in mock_cleanup.sh is done wrong
by Daniel Belenky (oVirt JIRA) 04 Jun '17

04 Jun '17

Daniel Belenky created OVIRT-1430: ------------------------------------- Summary: docker images cleanup in mock_cleanup.sh is done wrong Key: OVIRT-1430 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1430 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra We've decided that for now, we'll keep a cache of images coming from centos|fedora official repositories. The cleanup is done by listing all the images which are not coming from those repositories and removing them. The bug is in the way we're listing and addressing images: we're addressing images by image id's, which might be shared between several tags. For instance: if I have a Dockerfile which builds a container from the official centos image and doesn't really change the image, and then I tag the image with a different name: tag, I'll get another reference for the official image, and the cleanup will remove it. Another issue that might come up, is that we do have an image, but its tag has changed during the ran form 'latest' to something else. In this case, the cleanup will just fail the job as it won't have find the image with the different tag that have changed. -- This message was sent by Atlassian JIRA (v1000.1026.0#100045)

1 0

Fwd: Lago v0.39 is out!
by Nadav Goldin 04 Jun '17

04 Jun '17

---------- Forwarded message ---------- From: Nadav Goldin <ngoldin(a)redhat.com> Date: Sun, Jun 4, 2017 at 2:24 PM Subject: Lago v0.39 is out! To: lago-devel(a)ovirt.org On behalf of the Lago team, I'm pleased to announce the new release of Lago and Lago-ost-plugin: Lago - v0.39 Lago-ost-plugin v0.41 This is the first release where we've separated Lago and lago-ost-plugin(aka ovirtlago) to different repositories, installation procedures should be the same. However, from now on the lago-ost-plugin will follow a different release cycle. It's repository can be found at [1], and docs at [2]. Note that 'lago-ost-plugin' requires Lago >= 0.39. What's new ========= Lago ------- 1. Improved Ansible inventory support. For more details see [3]. 2. Lago SDK - Allows to run most CLI operations directly from Python. See [4] for the docs, and [5] for an example. This is mostly standardization of the already provided SDK. 3. Debian network support in bootstrap stage. Lago Images ----------------- 3 New images were added, please help in verifying them: 1. fc25-base 2. debian8-base 3. ubuntu16.04-base There is a known issue with host name resolution after boot in debian, but it does not affect connectivity. Tests/CI ------------ 1. Moved to tox to setup the virtualenv during the tests: * `tox -e docs` - builds the docs. * `tox -e py27` - run unittests and linters. * `tox -c tox-sdk.ini -- --stage check_patch/check_merged` - to run the functional SDK tests for each stage(after you have installed lago - either in a nested virtualenv or from RPMs). 2. Added SDK functional tests: * Easy to run sanity check while developing, under tests/functional-sdk run: `pytest -s -vvv --setup-show --stage check_patch test_sdk_sanity.py` 3. Added multi-distro tests, which means prior to merging every Lago patch, we'll ensure the core images in templates.ovirt.org are functional with the new patch. 4. Added ansible functional tests on check-merged. For the full changelog see [6]. Upgrading ======== To upgrade using yum or dnf, simply run: ``` yum/dnf update lago ``` Resources ======== Lago Docs: http://lago.readthedocs.io/en/latest/ GitHub: https://github.com/lago-project/lago/ YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ OST Docs: http://ovirt-system-tests.readthedocs.io/en/latest/ As always, if you find any problems, please open an issue in the GitHub page. Enjoy! Nadav. [1] https://github.com/lago-project/lago-ost-plugin [2] http://lago-ost-plugin.readthedocs.io/en/latest/ [3] https://github.com/lago-project/lago/pull/544 [4] http://lago.readthedocs.io/en/stable/SDK.html [5] https://github.com/lago-project/lago/blob/master/docs/examples/lago_sdk_one… [6] https://github.com/lago-project/lago/compare/0.38...0.39

1 0