- Devel - oVirt List Archives

Unable to add host in oVirt 4.2 (clean install)
by Marek Libra 05 Oct '17

05 Oct '17

Since Andrej ran in similar issue today, I'm posting for others: When installing oVirt 4.2 first alpha release from scratch on fresh Centos 7 minimal, adding host failed. Unfortunately, I don't have log messages anymore, but I remember last errors were misleadingly related to ovn (no matter the ovn was not configured on the engine). The issue was resolved by manual installation of python-netaddr package on the host. Subsequently, adding the host in webadmin passed. What package should require the python-netaddr? ovirt-provider-ovn-driver? I hope it helps, Marek

3 2

Ansible Help Requested
by Phillip Bailey 02 Oct '17

02 Oct '17

Hi all, I'm working on the new Cockpit hosted engine wizard and could use some input from all of you. One goal of this project is to move away from reliance on the existing OTOPI-based tools and towards an ansible-based approach. The items below are things we'd like to do using ansible, if possible. If any of you have existing plays or suggestions for the best way to use ansible to solve these problems, please let me know. Thanks! 1. Verify provided storage settings for all allowable storage types. 2. Verify compatibility of selected CPU type for the engine VM with the host's CPU -Phillip Bailey

4 5

Re: [ovirt-devel] [Qemu-block] qemu-img: Check failed: No space left on device
by Stefan Hajnoczi 02 Oct '17

02 Oct '17

On Tue, Sep 26, 2017 at 04:31:22PM +0200, Nicolas Ecarnot wrote: > Le 21/09/2017 à 16:31, Stefan Hajnoczi a écrit : > > On Tue, Sep 19, 2017 at 12:09:06PM +0200, Nicolas Ecarnot wrote: > > > Hello, > > > > > > First post here, so maybe I should introduce myself : > > > - I'm a sysadmin for decades and currently managing 4 oVirt clusters, made > > > out of tens of hypervisors, all are CentOS 7.2+ based. > > > - I'm very happy with this solution we choose especially because it is based > > > on qemu-kvm (open source, reliable, documented). > > > > > > On one VM, we experienced the following : > > > - oVirt/vdsm is detecting an issue on the image > > > - following this hints https://access.redhat.com/solutions/1173623, I > > > managed to detect one error and fix it > > > - the VM is now running perfectly > > > > > > On two other VMs, we experienced a similar situation, except the check stage > > > is showing something like 14000+ errors, and the relevant logs are : > > > > > > Repairing refcount block 14 is outside image > > > ERROR could not resize image: Invalid argument > > > ERROR cluster 425984 refcount=0 reference=1 > > > ERROR cluster 425985 refcount=0 reference=1 > > > [... repeating the previous line 7000+ times...] > > > ERROR cluster 457166 refcount=0 reference=1 > > > Rebuilding refcount structure > > > ERROR writing refblock: No space left on device > > > qemu-img: Check failed: No space left on device > > > > Please run strace qemu-img info /the/relevant/logical/volume/path. It Sorry, "qemu-img info" should be your "qemu-img check" command. > > will print all the syscalls that qemu-img makes. That way we'll be able > > to verify that the ENOSPC error is coming from a pwritev syscall. > I did but I'm not skilled enough to ensure where the ENOSPC error is coming > from. > > Is your question meaning the reads and/or the writes may come from or go to > places outside the expected boundaries? I was interested in the syscall (probably pwritev or similar) related to the following output from qemu-img check: ERROR writing refblock: No space left on device Feel free to post your strace log so we can analyze it. > > > You surely know that oVirt/RHEV is storing its qcow2 images in dedicated > > > logical volumes. > > > > > > pvs/vgs/lvs are all showing there is plenty of space available, so I > > > understand that I don't understand what "No space left on device" means. > > > > After you have the strace data you can look at the file offset from the > > failing pwritev syscall and check that it's really within the LV. > > > > I think there is no fancy thin provisioning going on at the LVM level > > with oVirt, but if there is then perhaps a write within the LV could > > still result in an ENOSPC error. It would be worth confirming that > > these are class "thick" LVs. > > I think there is no such thin prov. at the LVM level, but I wouldn't swear. > Don't you mind if I forward your question to the oVirt mailing-list? Sure, feel free to CC other mailing lists. I have added oVirt devel. Stefan

1 0

OST Failure he-basic
by Dominik Holler 02 Oct '17

02 Oct '17

Hi all, OST he-basic is currently failing [1] during setup "hosted-engine" during Connecting Storage Pool with the message Failed to execute stage 'Misc configuration': 'functools.partial' object has no attribute 'getAllTasksStatuses' Since the lago-he-basic-suite-master-engine VM is inaccessible after the problem, I have no idea how to locate the problem. Dominik [1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests…

3 3

Missing ovirtmgmt (was: Change in ovirt-system-tests[master]: he: Run hosted-engine --vm-status)
by Yedidyah Bar David 02 Oct '17

02 Oct '17

Hi all, On Sun, Oct 1, 2017 at 10:15 AM, Code Review <gerrit(a)ovirt.org> wrote: > Jenkins CI posted comments on this change. > > View Change > > Patch set 1:Continuous-Integration -1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > : FAILURE Above was triggered by [1]. It failed with [2]: TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt] ********************* fatal: [lago-he-basic-suite-master-host1]: FAILED! => {"changed": true, "cmd": ["vdsm-tool", "ovn-config", "192.168.200.99", "ovirtmgmt"], "delta": "0:00:00.623565", "end": "2017-10-01 03:15:11.179717", "failed": true, "msg": "non-zero return code", "rc": 1, "start": "2017-10-01 03:15:10.556152", "stderr": "Traceback (most recent call last):\n File \"/usr/bin/vdsm-tool\", line 219, in main\n return tool_command[cmd][\"command\"](*args)\n File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 58, in ovn_config\n ip_address = get_ip_addr(get_network(network_caps(), net_name))\n File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 79, in get_network\n raise NetworkNotFoundError(net_name)\nNetworkNotFoundError: ovirtmgmt", "stderr_lines": ["Traceback (most recent call last):", " File \"/usr/bin/vdsm-tool\", line 219, in main", " return tool_command[cmd][\"command\"](*args)", " File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 58, in ovn_config", " ip_address = get_ip_addr(get_network(network_caps(), net_name))", " File \"/usr/lib/python2.7/site-packages/vdsm/tool/ovn_config.py\", line 79, in get_network", " raise NetworkNotFoundError(net_name)", "NetworkNotFoundError: ovirtmgmt"], "stdout": "", "stdout_lines": []} Meaning, 'ovirtmgmt' is missing. In host-deploy [3] of this host, I see that the engine asked host-deploy to configure ovirtmgmt: 2017-10-01 03:14:36,036-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### Customization phase, use 'install' to proceed 2017-10-01 03:14:36,036-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### COMMAND> 2017-10-01 03:14:36,036-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QHidden: FALSE 2017-10-01 03:14:36,037-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ***Q:STRING CUSTOMIZATION_COMMAND 2017-10-01 03:14:36,037-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QEnd: CUSTOMIZATION_COMMAND 2017-10-01 03:14:36,038-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:RECEIVE env-query -k HOSTED_ENGINE_CONFIG/bridge 2017-10-01 03:14:36,038-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QStart: HOSTED_ENGINE_CONFIG/bridge 2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### 2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### Please specify value for 'HOSTED_ENGINE_CONFIG/bridge': 2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ### Response is VALUE HOSTED_ENGINE_CONFIG/bridge=type:value or ABORT HOSTED_ENGINE_CONFIG/bridge 2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND ***Q:VALUE HOSTED_ENGINE_CONFIG/bridge 2017-10-01 03:14:36,039-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QEnd: HOSTED_ENGINE_CONFIG/bridge 2017-10-01 03:14:36,040-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:RECEIVE VALUE HOSTED_ENGINE_CONFIG/bridge=str:ovirtmgmt 2017-10-01 03:14:36,040-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%QStart: CUSTOMIZATION_COMMAND However, AFAIU this was deprecated quite a long time ago [4], and does not appear in other runs, e.g. the latest succeeded run of the same job [5][6]. Also, I can't see in engine log there [7] how ovirtmgmt was created (if at all). I now see a difference between them: The successful one [7] passed to ansible: --extra-vars=host_deploy_ovn_central=null And the failed one [8] passed: --extra-vars=host_deploy_ovn_central=192.168.200.99 So perhaps this was caused by a recent change related to OVN? Although I looked at engine git log and can't find anything. Thanks, [1] https://gerrit.ovirt.org/82403 [2] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [4] https://gerrit.ovirt.org/70833 [5] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [6] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [7] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [8] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > > To view, visit change 82403. To unsubscribe, visit settings. > > Gerrit-Project: ovirt-system-tests > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I46f453c7e86ce0e3a7282aca4d56f23363d1683b > Gerrit-Change-Number: 82403 > Gerrit-PatchSet: 1 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Comment-Date: Sun, 01 Oct 2017 07:15:31 +0000 > Gerrit-HasComments: No -- Didi

3 3

Live Documentation - Deep Dive
by Ori Liel 02 Oct '17

02 Oct '17

Below is a link to the video recording of the "Live Documentation" deep dive presentation. https://bluejeans.com/s/Ug3GX/ Thanks for listening, Ori.

1 0

Updated invitation: API Live Documentation - Deep Dive @ Mon Oct 2, 2017 9am - 10am (EDT) (devel@ovirt.org)
by oliel＠redhat.com 02 Oct '17

02 Oct '17

This event has been changed. Title: API Live Documentation - Deep Dive Deep dive on the new way to document operations in the API https://bluejeans.com/u/oliel/3879/ When: Mon Oct 2, 2017 9am – 10am Eastern Time (changed) Where: https://bluejeans.com/u/oliel/ Calendar: devel(a)ovirt.org Who: * oliel(a)redhat.com - organizer * devel(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NzdibGw2N3ZqYWJyZjk5Z… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Updated invitation: API Live Documentation - Deep Dive @ Mon Oct 2, 2017 4pm - 5pm (EDT) (devel@ovirt.org)
by oliel＠redhat.com 02 Oct '17

02 Oct '17

This event has been changed. Title: API Live Documentation - Deep Dive Deep dive on the new way to document operations in the API https://bluejeans.com/u/oliel/3879/ When: Mon Oct 2, 2017 4pm – 5pm Eastern Time Where: https://bluejeans.com/u/oliel/ (changed) Calendar: devel(a)ovirt.org Who: * oliel(a)redhat.com - organizer * devel(a)ovirt.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NzdibGw2N3ZqYWJyZjk5Z… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

[ OST Failure Report ] [ oVirt master ] [ 01-10-2017 ] [ change-queue-tester ]
by Shlomo Ben David 02 Oct '17

02 Oct '17

Hi, Link to suspected patches: https://gerrit.ovirt.org/#/c/82350/2 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue- tester/2949/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2949/artifact… (Relevant) error snippet from the log: <error> lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-master_change-queue-tester@2/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 372, in live_storage_migration disk_service.get().status, types.DiskStatus.OK) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != ok after 600 seconds </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCE | RHCVA IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

3 5

Invitation to API 'Live Documentation' presentation - Oct 2
by Ori Liel 02 Oct '17

02 Oct '17

This coming Monday, Oct 2, I will present a new feature in the API which has to do with documentation of API operations (it's more exciting than it sounds). This presentation is important for everyone submitting patches to the ovirt-engine-api-model, because these patches will be required to use the documentation infrastructure in the proper manner. I invite you all to be there, at: https://bluejeans.com/u/oliel/3879/ Ori

2 2