May 2019 - Devel - Ovirt List Archives

by Geschwentner, Patrick

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/j... ). Can you confirm the defect? Best regards Patrick

2 years, 5 months

6
11
0 / 0

OST's basic suite UI sanity tests optimization

by Marcin Sobczyk

Hi, _TL; DR_ Let's cut the running time of '008_basic_ui_sanity.py' by more than 3 minutes by sacrificing Firefox and Chrome screenshots in favor of Chromium. During the OST hackathon in Brno this year, I saw an opportunity to optimize basic UI sanity tests from basic suite. The way we currently run them, is by setting up a Selenium grid using 3 docker containers, with a dedicated network... that's insanity! (pun intended). Let's a look at the running time of '008_basic_ui_sanity.py' scenario (https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te...): 01:31:50 @ Run test: 008_basic_ui_sanity.py: 01:31:50 nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] 01:31:50 # init: 01:31:50 # init: Success (in 0:00:00) 01:31:50 # start_grid: 01:34:05 # start_grid: Success (in 0:02:15) 01:34:05 # initialize_chrome: 01:34:18 # initialize_chrome: Success (in 0:00:13) 01:34:18 # login: 01:34:27 # login: Success (in 0:00:08) 01:34:27 # left_nav: 01:34:45 # left_nav: Success (in 0:00:18) 01:34:45 # close_driver: 01:34:46 # close_driver: Success (in 0:00:00) 01:34:46 # initialize_firefox: 01:35:02 # initialize_firefox: Success (in 0:00:16) 01:35:02 # login: 01:35:11 # login: Success (in 0:00:08) 01:35:11 # left_nav: 01:35:29 # left_nav: Success (in 0:00:18) 01:35:29 # cleanup: 01:35:36 # cleanup: Success (in 0:00:06) 01:35:36 # Results located at /dev/shm/ost/deployment-basic-suite-master/008_basic_ui_sanity.py.junit.xml 01:35:36 @ Run test: 008_basic_ui_sanity.py: Success (in 0:03:45) Starting the Selenium grid takes 2:15 out of 3:35 of total running time! I've investigated a lot of approaches and came up with something like this: * install 'chromium-headless' package on engine VM * download 'chromedriver' and 'selenium hub' jar and deploy them in '/var/opt/' on engine's VM * run 'selenium.jar' on engine VM from '008_basic_ui_sanity.py' by using Lago's ssh * connect to the Selenium instance running on the engine in '008_basic_ui_sanity.py' * make screenshots This series of patches represent the changes: https://gerrit.ovirt.org/#/q/topic:selenium-on-engine+(status:open+OR+sta.... This is the new running time (https://jenkins.ovirt.org/view/oVirt system tests/job/ovirt-system-tests_manual/4195/): 20:13:26 @ Run test: 008_basic_ui_sanity.py: 20:13:26 nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] 20:13:26 # init: 20:13:26 # init: Success (in 0:00:00) 20:13:26 # make_screenshots: 20:13:27 * Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdb6004f8d0>: Failed to establish a new connection: [Errno 111] Connection refused',)': /wd/hub 20:13:27 * Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdb6004fa10>: Failed to establish a new connection: [Errno 111] Connection refused',)': /wd/hub 20:13:27 * Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdb6004fb50>: Failed to establish a new connection: [Errno 111] Connection refused',)': /wd/hub 20:13:28 * Redirecting http://192.168.201.4:4444/wd/hub -> http://192.168.201.4:4444/wd/hub/static/resource/hub.html 20:14:02 # make_screenshots: Success (in 0:00:35) 20:14:02 # Results located at /dev/shm/ost/deployment-basic-suite-master/008_basic_ui_sanity.py.junit.xml 20:14:02 @ Run test: 008_basic_ui_sanity.py: Success (in 0:00:35) (The 'NewConnectionErrors' is waiting for Selenium hub to be up and running, I can silence these later). And the screenshots are here: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... _The pros:_ * we cut the running time by more than 3 minutes _The cons:_ * we don't get Firefox or Chrome screenshots - we get Chromium screenshots (although AFAIK, QE has much more Selenium tests which cover both Firefox and Chrome) * we polute the engine VM with 'chromium-headless' package and deps (in total: 'chromium-headless', 'chromium-common', 'flac-libs' and 'minizip'), although we can remove these after the tests _Some design choices explained:_ Q: Why engine VM? A: Because the engine VM already has 'X11' libs. We could install 'chromium-headless' (and even other browsers) on our Jenkins executors, but that would mess them up a lot. Q: Why Chromium? A: Because it has a separate 'headless' package. Q: Why not use 'chromedriver' RPM in favor of https://chromedriver.storage.googleapis.com Chromedriver builds? A: Because the RPM version pulls a lot of extra dependencies even on the engine VM ('gtk3', 'cairo' etc.). Builds from the URL are the offical Google Chromedriver builds, they contain a single binary, and they work for us. _What still needs to be polished with the patches:_ * Currently 'setup_engine_selenium.sh' script downloads each time 'selenium.jar' and 'chromedriver.zip' (even with these downloads we get much faster set-up times) - we should bake these into the engine VM image template. * 'selenium_hub_running' function in 'selenium_on_engine.py' is hackish - an ability to run an ssh command with a context manager (and auto-terminate on it exits) should be part of Lago. Can be refactored. Questions, comments, reviews are welcome. Regards, Marcin

4 years, 1 month

7
10
0 / 0

Storage test case needs to be fixed: 002_bootstrap.resize_and_refresh_storage_domain

by Dafna Ron

Hi Tal, I am seeing random failures for test 002_bootstrap.resize_and_refresh_storage_domain It looks like this is a timing issue since by the time we print out the error we actually see the resize succeeded. see example below: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/testR... Can you please assign someone from the storage team to fix this test? Thanks, Dafna

4 years, 2 months

4
14
0 / 0

ovirt-engine has been tagged (ovirt-engine-4.3.4.2)

by Tal Nisan

4 years, 3 months

1
0
0 / 0

Fwd: Fedora 28 End Of Life

by Sandro Bonazzola

FYI. Fedora 29 oVirt packages building is still in progress. The following package still need to be built, help with getting them built on fedora 29 will be appreciated. cockpit-ovirt engine-db-query ovirt-engine-api-explorer ovirt-engine-appliance ovirt-engine-extension-aaa-misc ovirt-engine-nodejs-modules ovirt-engine-sdk-python (sdk3) ovirt-engine-ui-extensions ovirt-engine-yarn ovirt-guest-agent-windows ovirt-guest-tools-iso ovirt-host ovirt-hosted-engine-ha ovirt-hosted-engine-setup ovirt-node-ng-image ovirt-provider-ovn ovirt-scheduler-proxy vdsm Thanks ---------- Forwarded message --------- Da: Mohan Boddu <mboddu(a)bhujji.com> Date: mer 29 mag 2019 alle ore 01:05 Subject: Fedora 28 End Of Life To: <announce(a)lists.fedoraproject.org>, < test-announce(a)lists.fedoraproject.org>, < devel-announce(a)lists.fedoraproject.org> As of the 28th of May 2019, Fedora 28 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 28. Fedora 29 will continue to receive updates until approximately one month after the release of Fedora 31. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Sche... [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora... -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

4 years, 3 months

1
0
0 / 0

VDSM Python 3 RPMs are available

by Marcin Sobczyk

Hi, I'm happy to announce, that with [1] landing in master, we're now building Python 3 packages for VDSM. Example pipeline run can be found here [2]. Currently the py3 RPMs still have some broken dependencies and there are ongoing efforts to fix these. All scripts in built RPMs have py3 shebang lines, but there is no guarantee that all of them will work. We also build for Fedora 28 only - more patches are on the way that will build RPMs for Fedora 30. If you want to make py3 RPMs out of your VDSM patch, you simply need to post 'ci please build' in gerrit - that will launch 'build-artifacts' stdci stage which produces py2 and py3 RPMs in its sub-stages. Regards, Marcin [1] https://gerrit.ovirt.org/#/c/100135/ [2] https://jenkins.ovirt.org/job/vdsm_standard-on-merge/755/artifact/

4 years, 3 months

2
1
0 / 0

vdsm has been tagged (v4.30.17)

by Milan Zamazal

4 years, 3 months

1
0
0 / 0

sanlock 3.7.3-1 is available for testing

by Nir Soffer

This is the first version providing proper 4K API, and will be consumed by vdsm soon when the package is available. We will have soft dependency to allow testing 4k sorage on platforms that provide this package. sanlock 3.7.3 is available now for testing on: ## CentOS Enable this repo: http://buildlogs.centos.org/centos/$releasever/virt/$basearch/ovirt-4.3/ Sandro, shouldn't it be in: https://cbs.centos.org/repos/virt7-ovirt-43-testing/$basearch/os/ ## Fedora I requested sanlock-3.7.3 for update-testing yesterday in the morning, but the package is still pending after more than a day. To get the package now, you can download the rpms from koji: f28: https://kojipkgs.fedoraproject.org//packages/sanlock/3.7.3/1.fc28/x86_64/ f29: https://kojipkgs.fedoraproject.org//packages/sanlock/3.7.3/1.fc29/x86_64/ f30: https://kojipkgs.fedoraproject.org//packages/sanlock/3.7.3/1.fc30/x86_64/ Thanks for testing sanlock! Nir

4 years, 3 months

4
5
0 / 0

Re: [ovirt-users] Donating hardware to the oVirt project - a great opportunity to contribute

by Eyal Edri

Also adding infra and devel lists. On Thu, May 23, 2019 at 11:19 AM Evgheni Dereveanchin <ederevea(a)redhat.com> wrote: > Hi everyone, > > My name is Evgheni and I'm in charge of the infrastructure used by oVirt > to host the code, test it and serve packages to users. Currently we heavily > rely on our PHX data center [1] for these tasks. It consists of several > dozen bare metal servers that work as hypervisors, storage servers and bare > metal CI hosts. We use them quite effectively yet the amount of workload is > always growing so now is a good time to ask our community for help. If you > happen to have physical servers or VMs that could be used as part of oVirt > infra - please let us know. We created a page [2] describing hardware specs > that would allow us make the infra more stable and grow its capacity. > > If you have any other ideas or input about the oVirt infra - feel free to > reach out to me or start a discussion on the Infra list [3]. > > Regards, > Evgheni > > [1] > https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Overview/in... > [2] https://ovirt.org/community/get-involved/donate-hardware.html > [3] https://lists.ovirt.org/ > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/message/H3BHMU3DHFS... > -- Eyal edri MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)

4 years, 3 months

1
0
0 / 0

Lago oVirt plugin v0.46 Release Announcement

by Galit Rosenthal

Hi, On behalf of the Lago team, I'm pleased to announce that lago-ost-plugin v0.46, is available. This release adds support for Fedora 29 and includes some bug fixes and new features. New Features - Fedora29 requires gcc which is missing - Fedora requires dnf-utils - Lago ost plugin does not need to depend directly on createrepo. repoman depends on it (on createrepo_c which is OK). This a This allows us to get rid of 'yum' if needed. Bug Fixes - Fix Lago ExtractPathNoPathError - Fix "with_repo_server" docstrings Installing And Upgrading To upgrade using yum or dnf, simply run: yum/dnf update lago-ost-plugin Resources Docs: http://lago-ost-plugin.readthedocs.io/en/latest/ GitHub: https://github.com/lago-project/lago-ost-plugin YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ OST Docs: http://ovirt-system-tests.readthedocs.io/en/latest/ Changelog: http://lago-ost-plugin.readthedocs.io/en/latest/_static/ChangeLog.txt As always, if you find any issues, please open an issue on the GitHub page. Enjoy! Galit -- GALIT ROSENTHAL SOFTWARE ENGINEER Red Hat <https://www.redhat.com/> galit(a)redhat.com T: 972-9-7692230 <https://red.ht/sig>

4 years, 3 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Devel May 2019