- Devel - oVirt List Archives

outage alert: Gerrit.ovirt.org is down
by Eyal Edri 08 Jun '17

08 Jun '17

FYI, Gerrit.ovirt.org which is hosted on Amazon seems to be not responding, we're investigating the issue and will report shortly once we identify the problem. oVirt infra. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 1

[ OST Failure Report ] [ oVirt master ] [ 06-06-2017 ] live_storage_migration
by Evgheni Dereveanchin 08 Jun '17

08 Jun '17

Hi, We have the following test failing on master: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7050/testR… Stack trace from engine.log: 2017-06-06 12:15:13,150-04 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (DefaultQuartzScheduler2) [2b9829cc-1fce-47c8-93d8-c97b5531c930] Error during ValidateFailure.: java.lang.IllegalArgumentException: Cannot validate operation on disk for action of type LiveMigrateDisk as it is not an allowed command for the disk content type. at org.ovirt.engine.core.bll.validator.storage.DiskOperationsValidator.isOperationAllowedOnDisk(DiskOperationsValidator.java:34) [bll.jar:] at org.ovirt.engine.core.bll.storage.disk.MoveOrCopyDiskCommand.checkOperationAllowedOnDiskContentType(MoveOrCopyDiskCommand.java:187) [bll.jar:] at org.ovirt.engine.core.bll.storage.disk.MoveOrCopyDiskCommand.validate(MoveOrCopyDiskCommand.java:144) [bll.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.validate(LiveMigrateDiskCommand.java:360) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.internalValidate(CommandBase.java:849) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:403) [bll.jar:] ... Suspect patches: https://gerrit.ovirt.org/#/c/77521/ https://gerrit.ovirt.org/#/c/77452/ full engine.log: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… first failing job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7050/ -- Regards, Evgheni Dereveanchin

2 1

Need Support to fix oVirt Engine - Fails to start engine VM
by Rizwan Qureshi 08 Jun '17

08 Jun '17

--_000_LOXP123MB106111E7C95DE5E4C1CE0364EDC90LOXP123MB1061GBRP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Developers, We are new to ovirt developers list, infact new to oVirt also. We unfortuna= tely managed to break our oVirt installation. The engine VM does not seem t= o start after we updated to 4.0 from 3.6 and did a restart. We are looking for someone specialized to fix this kind of issues. I have f= ailed to find anyone who provides support for oVirt so resorting to the dev= elopers list now. Already tried using the users list and someone did try to= help but could not get it to work. You can see the thread below for refere= nce and logs that I posted: http://lists.ovirt.org/pipermail/users/2017-May/082309.html Can anyone help please? -- Best Regards, Rizwan Qureshi VoIP Admin Ph: 01482427836 --_000_LOXP123MB106111E7C95DE5E4C1CE0364EDC90LOXP123MB1061GBRP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> Hello Developers,<o:p></o:p> We are new to ovirt developers list, infact new to o= Virt also. We unfortunately managed to break our oVirt installation. The en= gine VM does not seem to start after we updated to 4.0 from 3.6 and did a r= estart.<o:p></o:p> <o:p> </o:p> We are looking for someone specialized to fix this k= ind of issues. I have failed to find anyone who provides support for oVirt = so resorting to the developers list now. Already tried using the users list= and someone did try to help but could not get it to work. You can see the thread below for reference and logs th= at I posted:<o:p></o:p> <o:p> </o:p> <a href=3D"http://lists.ovirt.org/pipermail/users/20= 17-May/082309.html">http://lists.ovirt.org/pipermail/users/2017-May/082309.= html</a><o:p></o:p> <o:p> </o:p> Can anyone help please?<o:p></o:p> <o:p> </o:p> --<o:p></o:p> Best Regards,<o:p></o:p>= Rizwan Qureshi<o:p></o:p></span= > VoIP Admin<o:p></o:p></p= > Ph: 01482427836<o:p></o:p></spa= n> <o:p> </o:p> </div> </body> </html> --_000_LOXP123MB106111E7C95DE5E4C1CE0364EDC90LOXP123MB1061GBRP_--

2 1

Who cares about 'memGuaranteedSize'?
by Francesco Romani 08 Jun '17

08 Jun '17

Hi all, We have this field in the Vdsm API: - description: The amount of memory guaranteed to the VM in MB name: memGuaranteedSize type: uint Available in VmDefinition, VMFullInfo, VmParameters Vdsm dutifully records and reports this value - but doesn't use it. It is used exactly once for balloon stata: stats['balloonInfo'].update({ 'balloon_max': str(max_mem), 'balloon_min': str( int(vm.conf.get('memGuaranteedSize', '0')) * 1024), 'balloon_cur': str(balloon_cur), 'balloon_target': str(balloon_target) }) Now, a quick git grep in both MOM and Engine reveals no obvious usages. Am I missing something? Can we drop this for 4.2, and deprecate it in next(4.1) ? Thanks, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

2 1

[ OST Failue Report ] [ oVirt master ] [ 7/6/17 ] engine upgrade: 001_upgrade_engine
by Daniel Belenky 07 Jun '17

07 Jun '17

Hi all, oVirt engine upgrade test failed. Version failing: upgrade from 4.1 to master | upgrade from 4.0 to master Link to failed job: test-repo_ovirt_experimental_master/7091/ <http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7091/> Link to suites logs: logs <http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7091/artif…> Suspected patch: Gerrit 77254: packaging: ovirt-provider-ovn password must not be empty by default <https://gerrit.ovirt.org/#/c/77254/> Potential fix(es): [1] 77934: Add ovirtProviderOvnPassword to the answer file <https://gerrit.ovirt.org/#/c/77934/> [2] 77975: Update upgrade engine answer-file with ovirtProviderOvnPassword <https://gerrit.ovirt.org/#/c/77975/> iIt seems that though the answer file includes the ovn password, engine-setup ignores it. Can anyone provide more info/actions can be done in order to fix this issue? Thanks, -- DANIEL BELENKY Associate sw engineer RHEV DEVOPS Red Hat Israel <https://www.redhat.com/> dbelenky(a)redhat.com IRC: #rhev-integ, #rhev-dev <https://red.ht/sig>

1 0

Re: [ovirt-devel] Making event types backwards compatible?
by Michal Skrivanek 07 Jun '17

07 Jun '17

> On 29 May 2017, at 11:44, Juan Hernández <jhernand(a)redhat.com> wrote: > >> On 05/29/2017 11:27 AM, Michal Skrivanek wrote: >> >>> On 29 May 2017, at 10:39, Juan Hernández <jhernand(a)redhat.com> wrote: >>> >>> Hello, >>> >>> It has been recently requested that the API provides event types: >>> >>> [RFE] Expose event types to API >>> https://bugzilla.redhat.com/1453170 >>> >>> Currently the API provides the event code and description, for example: >>> >>> <event href="/ovirt-engine/api/events/8021" id="8021"> >>> <code>19</code> >>> <description>Host myhost failed to recover.</description >>> ... >>> </event> >>> >>> There is no documentation of what is the meaning of codes, except the >>> source code of the engine itself. This forces some applications to add >>> their own code to name mapping. For example, the 'ovirt' Ruby gem used >>> by older versions of ManageIQ to interact with oVirt contains the following: >>> >>> https://github.com/ManageIQ/ovirt/blob/v0.17.0/lib/ovirt/event.rb#L25-L485 >>> >>> We could avoid this by adding to the API a new event attribute that >>> indicates the type: >>> >>> <event href="/ovirt-engine/api/events/8021" id="8021"> >>> <code>19</code> >>> <type>host_recover_failure</type> >>> <description>Host myhost failed to recover.</description> >>> ... >>> </event> >>> >>> Ideally this should be defined as an enum, so that it will be >>> represented as an enum in the SDKs. Alternatively it could just be an >>> string, and we could reuse the 'name' attribute: >>> >>> <event href="/ovirt-engine/api/events/8021" id="8021"> >>> <code>19</code> >>> <name>host_recover_failure</name> >>> <description>Host myhost failed to recover.</description> >>> ... >>> </event> >>> >>> However, the key point to making this useful would be to keep the types >>> (or names) backwards compatible, so that users of the API can rely on >>> their values and meanings. >>> >>> So this is my question to you: can we commit to keep the names and >>> meanings of the backend event types backwards compatible? >> >> Do we even have to make it bw compatible? >> I guess it depends on the actual usage of those names… >> The ovirt ruby gem itself doesn’t do much with it > > We need to make keep it backwards compatible or else tell users "don't > rely on these values, as they may change without notice". > > The 'ovirt' gem doesn't do anything special, it just creates its own > code to name mapping. But the users of the 'ovirt' gem (the ManageIQ > oVirt provider) do rely on the name. For example: > > > https://github.com/ManageIQ/manageiq-providers-ovirt/blob/master/app/models… > > That means that if we ever change the meaning of a code the ManageIQ > provider, for example, will break. Right,then it indeed needs to stay stable. But how is maintaining the enum string different from the code? It is the same information, so if MIQ doesn't use the name directly then it doesn't really matter if it's a code or string. Perhaps deprecate the code and keep the name fixed? Thanks, michal > >>> >>> Regards, >>> Juan Hernandez >>> >>> >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >

4 6

[ovirt-system-tests] ssh to an oVirt VM in Lago
by Valentina Makarova 06 Jun '17

06 Jun '17

Hello! Please, help me to find way to execute some command in oVirt VM. Is it possible to get ssh connection to non-host VM in LAGO? And how can I get ssh connection through the console in my computer? I installed ovirt-system-tests and run tests from basic-suite-master. So there is 2 hosts and 3 vms in my configuration. And I want to execute command inside the vm0 using LAGO (as part of my own test). It is easy for host vm and engine, there is method ''ssh" in ovirt-engine-api-model. And this task for host vm can be performed as there prefix.virt_env.get_vm(VM_NAME).ssh(['bash_command_what_i_want']) Please give me advice, can Iget connection to vm0 in a similar way? And a second question is about ssh to this vm connection from my laptop's console. According run_vm test from 004_basic_sanity.py ( https://github.com/oVirt/ovirt-system-tests/blob/master/basic-suite-master/… ) vm0 should contain interface with ip 192.168.200.200, but ping this from engine (192.168.200.4) Destination Host Unreachable. And 'ping vm0' defined vm0 as 192.168.201.213 and also couldn't reach vm0. And in webadmin (https://engine/ovirt-engine/webadmin/#vms) IP Address field is empty. What is a right way to get connection to vm0 console and execute some command there? Sincerely, Valentina Makarova

5 7

planned Jenkins restart
by Evgheni Dereveanchin 06 Jun '17

06 Jun '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

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

[VDSM] flake8 3.0.4 failing vdsm builds
by Nir Soffer 02 Jun '17

02 Jun '17

Hi all, flake8 started to fail today with import error, failing vdsm builds with this error: Traceback (most recent call last): File "/home/nsoffer/src/vdsm/.tox/flake8/bin/flake8", line 7, in <module> from flake8.main.cli import main File "/home/nsoffer/src/vdsm/.tox/flake8/lib/python2.7/site-packages/flake8/main/cli.py", line 2, in <module> from flake8.main import application File "/home/nsoffer/src/vdsm/.tox/flake8/lib/python2.7/site-packages/flake8/main/application.py", line 14, in <module> from flake8.main import options File "/home/nsoffer/src/vdsm/.tox/flake8/lib/python2.7/site-packages/flake8/main/options.py", line 3, in <module> from flake8.main import vcs File "/home/nsoffer/src/vdsm/.tox/flake8/lib/python2.7/site-packages/flake8/main/vcs.py", line 4, in <module> from flake8.main import mercurial File "/home/nsoffer/src/vdsm/.tox/flake8/lib/python2.7/site-packages/flake8/main/mercurial.py", line 7, in <module> import configparser File "/usr/lib/python2.7/site-packages/configparser.py", line 12, in <module> from backports.configparser import ( ImportError: No module named configparser I posted this patch updating tox to use flake8 3.1.0: https://gerrit.ovirt.org/77727 Please rebase on this patch if your build fail. Thanks, Nir

1 0