July 2019 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error: Adding new Host to ovirt-engine
by Ahmad Khiet 14 Aug '23

14 Aug '23

Hi, Can't add new host to ovirt engine, because the following error: 2019-06-12 12:23:09,664 p=4134 u=engine | TASK [ovirt-host-deploy-facts : Set facts] ************************************* 2019-06-12 12:23:09,684 p=4134 u=engine | ok: [10.35.1.17] => { "ansible_facts": { "ansible_python_interpreter": "/usr/bin/python2", "host_deploy_vdsm_version": "4.40.0" }, "changed": false } 2019-06-12 12:23:09,697 p=4134 u=engine | TASK [ovirt-provider-ovn-driver : Install ovs] ********************************* 2019-06-12 12:23:09,726 p=4134 u=engine | fatal: [10.35.1.17]: FAILED! => {} MSG: The conditional check 'cluster_switch == "ovs" or (ovn_central is defined and ovn_central | ipaddr and ovn_engine_cluster_version is version_compare('4.2', '>='))' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller The error appears to be in '/home/engine/apps/engine/share/ovirt-engine/playbooks/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - block: - name: Install ovs ^ here 2019-06-12 12:23:09,728 p=4134 u=engine | PLAY RECAP ********************************************************************* 2019-06-12 12:23:09,728 p=4134 u=engine | 10.35.1.17 : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 whats missing!? Thanks -- Ahmad Khiet Red Hat <https://www.redhat.com/> akhiet(a)redhat.com M: +972-54-6225629 <https://red.ht/sig>

7 10

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

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/jav… ). Can you confirm the defect? Best regards Patrick

6 11

Relaunching the website migration project
by Marc Dequènes (Duck) 22 Aug '19

22 Aug '19

Quack, ### A pinch of history As a short introduction for those who do not know me as I rarely post here: I'm part of Red Hat OSPO Comminfra Team (previously OSPO was called OSAS) and currently hosting and taking care of the website. This topic has been discussed many times: neither people writing the site neither us for the maintenance are happy with the current state of affair. But we had not real plan and picking a random tool which might lead to similar problems and without any way to support it properly was not very appealing. Moreover we tried migrating to Middleman 4, the obvious path to modernization, but this happened to be more complicated than expected and this new version had terrible performance problems. As you now version 3 is already slow, and that's quite an understatement. In the meanwhile a few things have changed, and people taking care of the website too, so let's talk about the current situation. (very short version of the history around this) ### Why now? What has changed: * several projects moved to Jekyll, a software we were already investigating at the time and is being used by Google Pages (they created it in fact), and they were very happy with the result; we believe it has the necessary features, it is well maintained because Google uses it heavily, and it's very fast * we've tried Jekyll ourselves, we're happy too, and we do have the Ansible playbooks and tooling to deploy it now * over time the website had some waves of cleanup (still needs quite some love though) and recently the blog moved to WordPress to get comment support and a more friendly interface (see OVIRT-2652) which allowed more cleanup (see #2030) With the blog separated and a lot of custom Ruby code removed, the tooling ready, I believe we can now work on migrating the content. We may realize Jekyll is not the right tool, but people seemed to like the idea at the time and current experience seem to indicate it should improve things and be maintainable. The goal here is to experiment and switch to production only if we're happy with it. ### Early work I have started a branch called 'jekyll_migration' to put my work on it. This is very early work (I just started), I already hit various difficulties, and I can't commit 100% of my time on it so it will require some time. Several of my changes happened to not be really specific to the migration, and the current site would benefit from these fixes/cleanups/simplifications… thus I'll extracts these changes and create separate PRs for master. If you wish to help, then you can contact me directly or reply to this thread. You may also create PRs to this topic branch, but please do not push anything directly. Regards. \_o<

5 9

OST's basic suite UI sanity tests optimization
by Marcin Sobczyk 07 Aug '19

07 Aug '19

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-test…) 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+statu…. 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-test… _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

7 10

All loader-container nodes are offline, 99 jobs in the queue, jobs stuck for 2 hours
by Nir Soffer 01 Aug '19

01 Aug '19

2 1

Re: Vdsm NFS on RHEL 8
by Amit Bawer 31 Jul '19

31 Jul '19

Per +Milan Zamazal <mzamazal(a)redhat.com> comment, adding +devel <devel(a)ovirt.org> On Wed, Jul 24, 2019 at 11:32 AM Michal Skrivanek < michal.skrivanek(a)redhat.com> wrote: > > > On 24 Jul 2019, at 10:24, Amit Bawer <abawer(a)redhat.com> wrote: > > Thanks, applied the fixed patch. > > No I am punished for choosing not to work with SSL/TLS in Vdsm when trying > to "Run" VM. > - Any known workaround for this? > > > That’s part of the ongoing fixes, please don’t discuss this privately, > this belongs to devel@ list. > Many people are struggling with the same issues while they’re working on > their areas, and we need complete visibility > > > 24 04:04:54,610-0400 INFO (vm/01de706d) [virt.vm] > (vmId='01de706d-ee4c-484f-a17f-6b3355adf047') <?xml version='1.0' > encoding='utf-8'?> > <domain xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm=" > http://ovirt.org/vm/1.0" type="kvm"> > <name>vm1</name> > <uuid>01de706d-ee4c-484f-a17f-6b3355adf047</uuid> > <memory>1048576</memory> > <currentMemory>1048576</currentMemory> > <iothreads>1</iothreads> > <maxMemory slots="16">4194304</maxMemory> > <vcpu current="1">16</vcpu> > <sysinfo type="smbios"> > <system> > <entry name="manufacturer">oVirt</entry> > <entry name="product">RHEL</entry> > <entry name="version">8.0-0.44.el8</entry> > <entry > name="serial">e5825ba8-473e-4821-829a-bc6dbbe79617</entry> > <entry name="uuid">01de706d-ee4c-484f-a17f-6b3355adf047</entry> > </system> > </sysinfo> > <clock adjustment="0" offset="variable"> > <timer name="rtc" tickpolicy="catchup" /> > <timer name="pit" tickpolicy="delay" /> > <timer name="hpet" present="no" /> > </clock> > <features> > <acpi /> > </features> > <cpu match="exact"> > <model>SandyBridge</model> > <topology cores="1" sockets="16" threads="1" /> > <numa> > <cell cpus="0-15" id="0" memory="1048576" /> > </numa> > </cpu> > <cputune /> > <devices> > <input bus="usb" type="tablet" /> > <channel type="unix"> > <target name="ovirt-guest-agent.0" type="virtio" /> > <source mode="bind" > path="/var/lib/libvirt/qemu/channels/01de706d-ee4c-484f-a17f-6b3355adf047.ovirt-guest-agent.0" > /> > </channel> > <channel type="unix"> > <target name="org.qemu.guest_agent.0" type="virtio" /> > <source mode="bind" > path="/var/lib/libvirt/qemu/channels/01de706d-ee4c-484f-a17f-6b3355adf047.org.qemu.guest_agent.0" > /> > </channel> > <rng model="virtio"> > <backend model="random">/dev/urandom</backend> > <alias name="ua-117e932d-e465-40d6-9005-bf7d7eb22023" /> > </rng> > <graphics autoport="yes" passwd="*****" > passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1" type="spice"> > <channel mode="secure" name="main" /> > <channel mode="secure" name="inputs" /> > <channel mode="secure" name="cursor" /> > <channel mode="secure" name="playback" /> > <channel mode="secure" name="record" /> > <channel mode="secure" name="display" /> > <channel mode="secure" name="smartcard" /> > <channel mode="secure" name="usbredir" /> > <listen network="vdsm-ovirtmgmt" type="network" /> > </graphics> > <controller index="0" model="piix3-uhci" type="usb" /> > <controller index="0" model="virtio-scsi" type="scsi"> > <driver iothread="1" /> > <alias name="ua-73437643-3c01-4763-b8ef-c4275527606b" /> > </controller> > <graphics autoport="yes" keymap="en-us" passwd="*****" > passwdValidTo="1970-01-01T00:00:01" port="-1" type="vnc"> > <listen network="vdsm-ovirtmgmt" type="network" /> > </graphics> > <memballoon model="virtio"> > <stats period="5" /> > <alias name="ua-93d69b50-e010-4879-80db-713ee4a11727" /> > </memballoon> > <controller index="0" ports="16" type="virtio-serial"> > <alias name="ua-cd3edc3f-25c5-4fef-b555-cedf45c86adc" /> > </controller> > <video> > <model heads="1" ram="65536" type="qxl" vgamem="16384" > vram="8192" /> > <alias name="ua-d660095f-dfe6-4f2c-aa76-c3525fb6244e" /> > </video> > <channel type="spicevmc"> > <target name="com.redhat.spice.0" type="virtio" /> > </channel> > <disk device="cdrom" snapshot="no" type="file"> > <driver error_policy="report" name="qemu" type="raw" /> > <source file="" startupPolicy="optional"> > <seclabel model="dac" relabel="no" type="none" /> > </source> > <target bus="ide" dev="hdc" /> > <readonly /> > <alias name="ua-917aea8a-bc4b-4d15-8580-a0c442e925ee" /> > </disk> > <disk device="disk" snapshot="no" type="file"> > <target bus="scsi" dev="sda" /> > <source file="/rhev/data-center/mnt/10.35.1.6: > _exports_data/f49de997-9fb7-4ef8-82bd-f5b97ba31fb0/images/7dee6442-1838-48dd-892a-86fb96a85737/da070fc0-4af5-406e-bf2b-2cf4d89eb276"> > <seclabel model="dac" relabel="no" type="none" /> > </source> > <driver cache="none" error_policy="stop" io="threads" > name="qemu" type="raw" /> > <alias name="ua-7dee6442-1838-48dd-892a-86fb96a85737" /> > <address bus="0" controller="0" target="0" type="drive" > unit="0" /> > <boot order="1" /> > <serial>7dee6442-1838-48dd-892a-86fb96a85737</serial> > </disk> > </devices> > <pm> > <suspend-to-disk enabled="no" /> > <suspend-to-mem enabled="no" /> > </pm> > <os> > <type arch="x86_64" machine="pc-i440fx-rhel7.6.0">hvm</type> > <smbios mode="sysinfo" /> > </os> > <metadata> > <ns0:qos /> > <ovirt-vm:vm> > <ovirt-vm:minGuaranteedMemoryMb > type="int">1024</ovirt-vm:minGuaranteedMemoryMb> > <ovirt-vm:clusterVersion>4.4</ovirt-vm:clusterVersion> > <ovirt-vm:custom /> > <ovirt-vm:device devtype="disk" name="sda"> > > <ovirt-vm:poolID>dab8cf3a-a969-11e9-84eb-080027624b78</ovirt-vm:poolID> > > <ovirt-vm:volumeID>da070fc0-4af5-406e-bf2b-2cf4d89eb276</ovirt-vm:volumeID> > > <ovirt-vm:imageID>7dee6442-1838-48dd-892a-86fb96a85737</ovirt-vm:imageID> > > <ovirt-vm:domainID>f49de997-9fb7-4ef8-82bd-f5b97ba31fb0</ovirt-vm:domainID> > </ovirt-vm:device> > <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> > <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior> > </ovirt-vm:vm> > </metadata> > </domain> > (vm:2570) > 2019-07-24 04:04:55,348-0400 ERROR (vm/01de706d) [virt.vm] > (vmId='01de706d-ee4c-484f-a17f-6b3355adf047') The vm start process failed > (vm:841) > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 775, in > _startUnderlyingVm > self._run() > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2575, in > _run > dom.createWithFlags(flags) > File > "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line > 131, in wrapper > ret = f(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line > 94, in wrapper > return func(inst, *args, **kwargs) > File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1110, in > createWithFlags > if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', > dom=self) > libvirt.libvirtError: unsupported configuration: Auto allocation of spice > TLS port requested but spice TLS is disabled in qemu.conf > 2019-07-24 04:04:55,348-0400 INFO (vm/01de706d) [virt.vm] > (vmId='01de706d-ee4c-484f-a17f-6b3355adf047') Changed state to Down: > unsupported configuration: Auto allocation of spice TLS port requested but > spice TLS is disabled in qemu.conf (code=1) (vm:1595) > 2019-07-24 04:04:55,525-0400 INFO (vm/01de706d) [virt.vm] > (vmId='01de706d-ee4c-484f-a17f-6b3355adf047') Stopping connection > (guestagent:455) > 2019-07-24 04:04:55,525-0400 DEBUG (vm/01de706d) [jsonrpc.Notification] > Sending event {"jsonrpc": "2.0", "method": > "|virt|VM_status|01de706d-ee4c-484f-a17f-6b3355adf047", "params": > {"01de706d-ee4c-484f-a17f-6b3355adf047": {"status": "Down", "vmId": > "01de706d-ee4c-484f-a17f-6b3355adf047", "exitCode": 1, "exitMessage": > "unsupported configuration: Auto allocation of spice TLS port requested but > spice TLS is disabled in qemu.conf", "exitReason": 1}, "notify_time": > 4440824940}} (__init__:181) > > On Tue, Jul 23, 2019 at 6:14 PM Milan Zamazal <mzamazal(a)redhat.com> wrote: > >> Amit Bawer <abawer(a)redhat.com> writes: >> >> > Ok, applied the given patch. Now I have following error trace in >> vdsm.log >> > when trying to "Run" the VM: >> > >> > 2019-07-23 09:57:55,167-0400 ERROR (vm/01de706d) [virt.vm] >> > (vmId='01de706d-ee4c-484f-a17f-6b3355adf047') Failed to setup device >> spice >> > (vm:2344) >> > Traceback (most recent call last): >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2341, in >> > _setup_devices >> > dev_object.setup() >> > File >> "/usr/lib/python3.6/site-packages/vdsm/virt/vmdevices/graphics.py", >> > line 95, in setup >> > displaynetwork.create_network(display_network, self.vmid) >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/displaynetwork.py", >> line >> > 29, in create_network >> > libvirtnetwork.create_network(netname, display_device, >> user_reference) >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/libvirtnetwork.py", >> line >> > 91, in create_network >> > _createNetwork(createNetworkDef(netname, bridged, iface)) >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/libvirtnetwork.py", >> line >> > 108, in _createNetwork >> > net = conn.networkDefineXML(netXml) >> > File >> "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", >> > line 131, in wrapper >> > ret = f(*args, **kwargs) >> > File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line >> 94, >> > in wrapper >> > return func(inst, *args, **kwargs) >> > File "/usr/lib64/python3.6/site-packages/libvirt.py", line 4235, in >> > networkDefineXML >> > ret = libvirtmod.virNetworkDefineXML(self._o, xml) >> > TypeError: virNetworkDefineXML() argument 2 must be str or None, not >> bytes >> >> I believe https://gerrit.ovirt.org/102136 (untested) should fix it. >> >> > On Tue, Jul 23, 2019 at 3:56 PM Milan Zamazal <mzamazal(a)redhat.com> >> wrote: >> > >> >> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> > Hi Milan, >> >> > >> >> > I am trying to run VM on a RHEL8 host attached NFS domain. >> >> > I get the following error in vdsm.log >> >> > Do you happen to know what it means? >> >> >> >> Probably yes, does https://gerrit.ovirt.org/102127 (untested) fix it? >> >> >> >> > Thanks, >> >> > Amit >> >> > >> >> > Traceback (most recent call last): >> >> > File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line >> 124, >> >> in >> >> > method >> >> > ret = func(*args, **kwargs) >> >> > File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 294, in >> >> destroy >> >> > res = self.vm.destroy(gracefulAttempts) >> >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line >> 4916, in >> >> > destroy >> >> > result = self.doDestroy(gracefulAttempts, reason) >> >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line >> 4935, in >> >> > doDestroy >> >> > return self.releaseVm(gracefulAttempts) >> >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line >> 4828, in >> >> > releaseVm >> >> > self.guestAgent.stop() >> >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/guestagent.py", >> line >> >> > 458, in stop >> >> > self._channelListener.unregister(self._sock.fileno()) >> >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/vmchannels.py", >> line >> >> > 257, in unregister >> >> > self._unregister_fd(fileno) >> >> > File "/usr/lib/python3.6/site-packages/vdsm/virt/vmchannels.py", >> line >> >> 67, >> >> > in _unregister_fd >> >> > self._epoll.unregister(fileno) >> >> > ValueError: file descriptor cannot be a negative integer (-1) >> >> > >> >> > On Thu, Jul 18, 2019 at 8:35 AM Milan Zamazal <mzamazal(a)redhat.com> >> >> wrote: >> >> > >> >> >> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >> >> > 1. Had couple of small patches pushed to darkthrone py3_poc branch >> >> >> > >> >> >> > 2. Have a sequel document to Milan's installation guide abuts >> SSL-less >> >> >> vdsm >> >> >> > and engine: >> >> >> > >> >> >> >> >> >> https://drive.google.com/open?id=1jSt-LXSY8S6J8eTjt_-JU3Ph4ZNNnBoZBaJBWe8lQ… >> >> >> > >> >> >> > 3. Milan, you might want to update the BREW installation section - >> >> vdsm >> >> >> > install wants a more up-to-date ioprocess rpms, >> >> >> > I updated it in the guide copy here: >> >> >> > >> >> >> >> >> >> https://drive.google.com/open?id=1jSt-LXSY8S6J8eTjt_-JU3Ph4ZNNnBoZBaJBWe8lQ… >> >> >> > It now has: >> >> >> > >> >> >> $BREW/ioprocess/1.2.1/1.el8ev/x86_64/ioprocess-1.2.1-1.el8ev.x86_64.rpm \ >> >> >> > >> >> >> >> >> >> $BREW/ioprocess/1.2.1/1.el8ev/x86_64/python3-ioprocess-1.2.1-1.el8ev.x86_64.rpm >> >> >> >> >> >> It should be already in the updated document I sent to rhev-devel@ >> >> >> yesterday. >> >> >> >> >> >> > 4. Latest error when try to register host at engine:"Host >> 10.35.0.136 >> >> is >> >> >> > installed with VDSM version (4.40) and cannot join cluster Default >> >> which >> >> >> is >> >> >> > compatible with VDSM versions [4.17, 4.18]." - Can we fake the >> version >> >> >> > somehow? >> >> >> >> >> >> This has been fixed in Engine, both master and 4.3, some time ago. >> >> >> Please upgrade to current Engine version. >> >> >> >> >> >> > On Wed, Jul 17, 2019 at 4:38 PM Marcin Sobczyk < >> msobczyk(a)redhat.com> >> >> >> wrote: >> >> >> > >> >> >> >> >> >> >> >> On 7/17/19 3:27 PM, Marcin Sobczyk wrote: >> >> >> >> > >> >> >> >> > On 7/17/19 3:04 PM, Milan Zamazal wrote: >> >> >> >> >> Marcin Sobczyk <msobczyk(a)redhat.com> writes: >> >> >> >> >> >> >> >> >> >>> On 7/16/19 5:11 PM, Marcin Sobczyk wrote: >> >> >> >> >>>> On 7/16/19 4:47 PM, Milan Zamazal wrote: >> >> >> >> >>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>> >> >> >> >> >>>>>> +Marcin Sobczyk <msobczyk(a)redhat.com> >> >> >> >> >>>>>> >> >> >> >> >>>>>> On Tue, Jul 16, 2019 at 5:23 PM Amit Bawer < >> abawer(a)redhat.com >> >> > >> >> >> >> >>>>>> wrote: >> >> >> >> >>>>>> >> >> >> >> >>>>>>> I believe i tried all the variations after vdsm.id >> creation. >> >> >> >> >>>>>>> engine.log shows following error for ssh attempts to >> overlord >> >> >> >> >>>>>>> the host >> >> >> >> >>>>>>> from the engine: >> >> >> >> >>>>>>> >> >> >> >> >>>>>>> SS_ERROR(511), An error has occurred during installation >> of >> >> Host >> >> >> >> >>>>>>> rhel8: >> >> >> >> >>>>>>> Failed to execute stage 'Environment customization': No >> >> module >> >> >> >> >>>>>>> named >> >> >> >> >>>>>>> 'rpmUtils'. >> >> >> >> >>>>>>> >> >> >> >> >>>>>>> Could this be the reason? >> >> >> >> >>>>> I don't think Engine can manage the host, this is why we >> have >> >> to >> >> >> >> >>>>> bother >> >> >> >> >>>>> with the manual setup. rpmUtils is no longer available on >> >> RHEL 8, >> >> >> >> >>>>> there >> >> >> >> >>>>> was a patch to ovirt-host-deploy ( >> >> https://gerrit.ovirt.org/101293 >> >> >> ) >> >> >> >> >>>>> but >> >> >> >> >>>>> there are probably more places to fix. >> >> >> >> >>>>> >> >> >> >> >>>>> I can't remember what I did exactly regarding vdsm.id. I >> can >> >> >> >> suggest >> >> >> >> >>>>> only trying switching to maintenance and activate again >> after >> >> the >> >> >> >> >>>>> failed >> >> >> >> >>>>> installation. >> >> >> >> >>>>> >> >> >> >> >>>>> Marcin, do you have any better advice? >> >> >> >> >>>> Nope, unfortunately. Since the host deployment process >> fails in >> >> >> >> >>>> various interesting ways, my methodology also relies on the >> >> >> >> >>>> "maintenance --> activate" trick. >> >> >> >> >>>> I also never generated and 'vdsm.id' by myself. >> >> >> >> >>> Oh, regarding 'vdsm.id'. This might help: >> >> >> >> >>> >> >> >> >> >>> diff --git a/lib/vdsm/host/__init__.py >> >> b/lib/vdsm/host/__init__.py >> >> >> >> >>> index 334c88d1f..2aee4ea77 100644 >> >> >> >> >>> --- a/lib/vdsm/host/__init__.py >> >> >> >> >>> +++ b/lib/vdsm/host/__init__.py >> >> >> >> >>> @@ -47,6 +47,7 @@ def uuid(): >> >> >> >> >>> "system-uuid"], >> >> >> >> >>> raw=True, >> >> >> >> >>> sudo=True) >> >> >> >> >>> + out = out.decode('utf-8') >> >> >> >> >>> out = '\n'.join(line for line in >> >> out.splitlines() >> >> >> >> >>> if not >> line.startswith('#')) >> >> >> >> >> >> >> >> >> >> It indeed seems to help, thank you. Would you like to post a >> >> patch? >> >> >> >> > >> >> >> >> > Great! Sure, will do so. >> >> >> >> >> >> >> >> 3c08f9cc2fc1eb9390f1a68e1828bfb297307603 on darkthrone. Will >> post to >> >> >> >> gerrit later. >> >> >> >> >> >> >> >> > >> >> >> >> > >> >> >> >> >> >> >> >> >> >>>> Still, I never managed to get my RHEL8 host to 'Up' status - >> >> it's >> >> >> >> >>>> still 'NonOperational'. >> >> >> >> >>>> >> >> >> >> >>>> >> >> >> >> >>>>>>> On Tue, Jul 16, 2019 at 4:54 PM Milan Zamazal >> >> >> >> >>>>>>> <mzamazal(a)redhat.com> wrote: >> >> >> >> >>>>>>> >> >> >> >> >>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>>> Getting following error for attempting to Activate the >> >> rhel8 >> >> >> >> >>>>>>>>> host from >> >> >> >> >>>>>>>> web >> >> >> >> >>>>>>>>> mgmt: >> >> >> >> >>>>>>>>> >> >> >> >> >>>>>>>>> [image: image.png] >> >> >> >> >>>>>>>> Ah, right, you must do >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>> uuidgen > /etc/vdsm/vdsm.id >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>> to create the host id. I don't know how to tell Engine >> >> about >> >> >> the >> >> >> >> >>>>>>>> change, perhaps it detects it itself, perhaps the host >> must >> >> be >> >> >> >> >>>>>>>> switched >> >> >> >> >>>>>>>> to maintenance and then activated, perhaps it must be >> >> removed >> >> >> >> >>>>>>>> and added >> >> >> >> >>>>>>>> again (the previously performed actions on the host >> needn't >> >> be >> >> >> >> >>>>>>>> repeated >> >> >> >> >>>>>>>> again in such a case, I believe). >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>>> On Tue, Jul 16, 2019 at 4:27 PM Milan Zamazal >> >> >> >> >>>>>>>>> <mzamazal(a)redhat.com> >> >> >> >> >>>>>>>> wrote: >> >> >> >> >>>>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>>>> >> >> >> >> >>>>>>>>>>> On Tue, Jul 16, 2019 at 3:16 PM Milan Zamazal >> >> >> >> >>>>>>>>>>> <mzamazal(a)redhat.com> >> >> >> >> >>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>> On Tue, Jul 16, 2019 at 12:37 PM Milan Zamazal < >> >> >> >> >>>>>>>> mzamazal(a)redhat.com> >> >> >> >> >>>>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>> On Tue, Jul 16, 2019 at 10:46 AM Milan Zamazal < >> >> >> >> >>>>>>>>>> mzamazal(a)redhat.com> >> >> >> >> >>>>>>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>> after 60s with not interruption it is timedout >> >> >> >> >>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>> No subscription with >> >> >> >> >>>>>>>>>>>>>>>>> 227243a0-c4fc-4fb6-b2ff-6e79ad362452 id >> >> >> >> >>>>>>>>>>>>>>>>> vdsm-client: Request Host.setupNetworks with >> args >> >> >> >> >>>>>>>> {'networks': >> >> >> >> >>>>>>>>>>>>>>>>> {'ovirtmgmt': {'nic': 'ens3', 'bootproto': >> 'dhcp', >> >> >> >> >>>>>>>>>> 'defaultRoute': >> >> >> >> >>>>>>>>>>>>>>>> True}}, >> >> >> >> >>>>>>>>>>>>>>>>> 'bondings': {}, 'options': >> {'connectivityCheck': >> >> >> False}} >> >> >> >> >>>>>>>> timed >> >> >> >> >>>>>>>>>> out >> >> >> >> >>>>>>>>>>>>>> after >> >> >> >> >>>>>>>>>>>>>>>> 60 >> >> >> >> >>>>>>>>>>>>>>>>> seconds >> >> >> >> >>>>>>>>>>>>>>>> You can use the script below to bring up >> ovirtmgmt >> >> >> >> >>>>>>>>>>>>>>>> manually >> >> >> >> >>>>>>>>>> (again, >> >> >> >> >>>>>>>>>>>>>>>> assuming your standard network interface is >> ens3). >> >> It >> >> >> >> >>>>>>>>>>>>>>>> should >> >> >> >> >>>>>>>>>>>> suffice to >> >> >> >> >>>>>>>>>>>>>>>> be able to connect the host to Engine, but you >> have >> >> to >> >> >> >> >>>>>>>>>>>>>>>> run it >> >> >> >> >>>>>>>>>>>> manually >> >> >> >> >>>>>>>>>>>>>>>> after each host boot. >> >> >> >> >>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>> Thanks, I think for RHEL8 brctl was replaced by >> >> nmcli: >> >> >> >> >>>>>>>>>>>>>>> >> >> >> >> >>>>>>>> >> >> >> >> >> >> >> >> >> >> https://computingforgeeks.com/how-to-create-a-linux-network-bridge-on-rhel-… >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>> Does vdsm-client work for you fine otherwise >> (e.g. >> >> for >> >> >> >> >>>>>>>>>>>>>>>> calls >> >> >> >> >>>>>>>> such >> >> >> >> >>>>>>>>>> as >> >> >> >> >>>>>>>>>>>>>>>> `vdsm-client Host getCapabilities'?). If so, >> I'd >> >> >> suggest >> >> >> >> >>>>>>>> catching >> >> >> >> >>>>>>>>>>>>>>>> someone from the networking team (Edward?, >> Bell?) to >> >> >> >> >>>>>>>>>>>>>>>> help you >> >> >> >> >>>>>>>> with >> >> >> >> >>>>>>>>>>>>>>>> setupNetworks. >> >> >> >> >>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>> No, it hangs for any (insecure) command. >> >> >> >> >>>>>>>>>>>>>> Does vdsm-client work with secure commands? >> >> >> >> >>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>> [abawer@dhcp-0-191 RPMS]$ vdsm-client Host >> >> >> >> >>>>>>>>>>>>> getNetworkStatistics >> >> >> >> >>>>>>>>>>>>> vdsm-client: Connection to localhost:54321 with >> >> >> use_tls=True, >> >> >> >> >>>>>>>>>> timeout=60 >> >> >> >> >>>>>>>>>>>>> failed: [Errno 13] Permission denied >> >> >> >> >>>>>>>>>>>> Two things to check: >> >> >> >> >>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>> - Is `vdsm-tool configure' happy and were all the >> >> services >> >> >> >> >>>>>>>> (libvirtd, >> >> >> >> >>>>>>>>>>>> supervdsmd, vdsmd) restarted after last run of >> >> >> vdsm-tool >> >> >> >> >>>>>>>> configure? >> >> >> >> >>>>>>>>>>> Thanks! >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Running insecure vdsm-client worked for following >> config >> >> >> and >> >> >> >> >>>>>>>>>>> course >> >> >> >> >>>>>>>> of >> >> >> >> >>>>>>>>>>> actions: >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> [root@dhcp-0-191 abawer]# egrep "ssl|tls|tcp|auth" >> >> >> >> >>>>>>>> /etc/vdsm/vdsm.conf >> >> >> >> >>>>>>>>>>> /etc/libvirt/libvirtd.conf /etc/libvirt/qemu.conf | >> >> grep -v >> >> >> >> >>>>>>>>>>> "#" >> >> >> >> >>>>>>>>>>> /etc/vdsm/vdsm.conf:ssl = false >> >> >> >> >>>>>>>>>>> /etc/libvirt/libvirtd.conf:auth_unix_ro = "none" >> >> >> >> >>>>>>>>>>> /etc/libvirt/libvirtd.conf:auth_tcp = "none" >> >> >> >> >>>>>>>>>>> /etc/libvirt/libvirtd.conf:auth_unix_rw="none" >> >> >> >> >>>>>>>>>>> /etc/libvirt/libvirtd.conf:listen_tcp = 1 >> >> >> >> >>>>>>>>>>> /etc/libvirt/libvirtd.conf:listen_tls = 0 >> >> >> >> >>>>>>>>>>> /etc/libvirt/qemu.conf:spice_tls=0 >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>> >> >> >> >> >> >> >> >> >> >> /etc/libvirt/qemu.conf:spice_tls_x509_cert_dir="/etc/pki/vdsm/libvirt-spice" >> >> >> >> >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>> >> >> >> >> >>>>>>>>>>> [root@dhcp-0-191 abawer]# vdsm-tool configure >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Checking configuration status... >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> lvm is configured for vdsm >> >> >> >> >>>>>>>>>>> Current revision of multipath.conf detected, >> preserving >> >> >> >> >>>>>>>>>>> Managed volume database is already configured >> >> >> >> >>>>>>>>>>> abrt is already configured for vdsm >> >> >> >> >>>>>>>>>>> libvirt is already configured for vdsm >> >> >> >> >>>>>>>>>>> SUCCESS: ssl configured to false. No conflicts. >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Running configure... >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Done configuring modules to VDSM. >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Restarted vdsmd, supervdsmd, libvirtd... >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> [abawer@dhcp-0-191 ~]$ service vdsmd status >> >> >> >> >>>>>>>>>>> Redirecting to /bin/systemctl status vdsmd.service >> >> >> >> >>>>>>>>>>> ● vdsmd.service - Virtual Desktop Server Manager >> >> >> >> >>>>>>>>>>> Loaded: loaded >> >> (/usr/lib/systemd/system/vdsmd.service; >> >> >> >> >>>>>>>>>>> enabled; >> >> >> >> >>>>>>>> vendor >> >> >> >> >>>>>>>>>>> preset: enabled) >> >> >> >> >>>>>>>>>>> Active: active (running) since Tue 2019-07-16 >> >> 09:11:22 >> >> >> >> >>>>>>>>>>> EDT; 8s ago >> >> >> >> >>>>>>>>>>> Process: 6963 >> >> >> >> >>>>>>>>>>> ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh >> >> >> >> >>>>>>>>>>> --post-stop (code=exited, status=0/SUCCESS) >> >> >> >> >>>>>>>>>>> Process: 6969 >> >> >> >> >>>>>>>>>>> ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh >> >> >> >> >>>>>>>>>>> --pre-start (code=exited, status=0/SUCCESS) >> >> >> >> >>>>>>>>>>> Main PID: 7014 (vdsmd) >> >> >> >> >>>>>>>>>>> Tasks: 38 (limit: 24006) >> >> >> >> >>>>>>>>>>> Memory: 43.4M >> >> >> >> >>>>>>>>>>> CGroup: /system.slice/vdsmd.service >> >> >> >> >>>>>>>>>>> └─7014 /usr/libexec/platform-python >> >> >> >> >>>>>>>>>>> /usr/share/vdsm/vdsmd >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Jul 16 09:11:21 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running prepare_transient_repository >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running syslog_available >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running nwfilter >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running dummybr >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running tune_system >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running test_space >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsmd_init_common.sh[6969]: >> >> >> >> >>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>> Running test_lo >> >> >> >> >>>>>>>>>>> Jul 16 09:11:22 dhcp-0-191.tlv.redhat.com >> systemd[1]: >> >> >> Started >> >> >> >> >>>>>>>> Virtual >> >> >> >> >>>>>>>>>>> Desktop Server Manager. >> >> >> >> >>>>>>>>>>> Jul 16 09:11:23 dhcp-0-191.tlv.redhat.com >> vdsm[7014]: >> >> WARN >> >> >> >> >>>>>>>>>>> MOM not >> >> >> >> >>>>>>>>>>> available. >> >> >> >> >>>>>>>>>>> Jul 16 09:11:23 dhcp-0-191.tlv.redhat.com >> vdsm[7014]: >> >> WARN >> >> >> >> >>>>>>>>>>> MOM not >> >> >> >> >>>>>>>>>>> available, KSM stats will be missing. >> >> >> >> >>>>>>>>>>> [abawer@dhcp-0-191 ~]$ service supervdsmd status >> >> >> >> >>>>>>>>>>> Redirecting to /bin/systemctl status >> supervdsmd.service >> >> >> >> >>>>>>>>>>> ● supervdsmd.service - Auxiliary vdsm service for >> running >> >> >> >> >>>>>>>>>>> helper >> >> >> >> >>>>>>>>>> functions >> >> >> >> >>>>>>>>>>> as root >> >> >> >> >>>>>>>>>>> Loaded: loaded >> >> >> >> >>>>>>>>>>> (/usr/lib/systemd/system/supervdsmd.service; >> >> >> >> >>>>>>>> static; >> >> >> >> >>>>>>>>>>> vendor preset: enabled) >> >> >> >> >>>>>>>>>>> Active: active (running) since Tue 2019-07-16 >> >> 09:11:19 >> >> >> >> >>>>>>>>>>> EDT; 17s >> >> >> >> >>>>>>>> ago >> >> >> >> >>>>>>>>>>> Main PID: 6968 (supervdsmd) >> >> >> >> >>>>>>>>>>> Tasks: 5 (limit: 24006) >> >> >> >> >>>>>>>>>>> Memory: 20.9M >> >> >> >> >>>>>>>>>>> CGroup: /system.slice/supervdsmd.service >> >> >> >> >>>>>>>>>>> └─6968 /usr/libexec/platform-python >> >> >> >> >>>>>>>> /usr/share/vdsm/supervdsmd >> >> >> >> >>>>>>>>>>> --sockfile /var/run/vdsm/svdsm.sock >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Jul 16 09:11:19 dhcp-0-191.tlv.redhat.com >> systemd[1]: >> >> >> Stopped >> >> >> >> >>>>>>>> Auxiliary >> >> >> >> >>>>>>>>>>> vdsm service for running helper functions as root. >> >> >> >> >>>>>>>>>>> Jul 16 09:11:19 dhcp-0-191.tlv.redhat.com >> systemd[1]: >> >> >> Started >> >> >> >> >>>>>>>> Auxiliary >> >> >> >> >>>>>>>>>>> vdsm service for running helper functions as root. >> >> >> >> >>>>>>>>>>> [abawer@dhcp-0-191 ~]$ service libvirtd status >> >> >> >> >>>>>>>>>>> Redirecting to /bin/systemctl status libvirtd.service >> >> >> >> >>>>>>>>>>> ● libvirtd.service - Virtualization daemon >> >> >> >> >>>>>>>>>>> Loaded: loaded >> >> >> (/usr/lib/systemd/system/libvirtd.service; >> >> >> >> >>>>>>>>>>> enabled; >> >> >> >> >>>>>>>>>>> vendor preset: enabled) >> >> >> >> >>>>>>>>>>> Drop-In: /etc/systemd/system/libvirtd.service.d >> >> >> >> >>>>>>>>>>> └─unlimited-core.conf >> >> >> >> >>>>>>>>>>> Active: active (running) since Tue 2019-07-16 >> >> 09:11:04 >> >> >> >> >>>>>>>>>>> EDT; 38s >> >> >> >> >>>>>>>> ago >> >> >> >> >>>>>>>>>>> Docs: man:libvirtd(8) >> >> >> >> >>>>>>>>>>> https://libvirt.org >> >> >> >> >>>>>>>>>>> Main PID: 6448 (libvirtd) >> >> >> >> >>>>>>>>>>> Tasks: 17 (limit: 32768) >> >> >> >> >>>>>>>>>>> Memory: 12.5M >> >> >> >> >>>>>>>>>>> CGroup: /system.slice/libvirtd.service >> >> >> >> >>>>>>>>>>> └─6448 /usr/sbin/libvirtd --listen >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> Jul 16 09:11:04 dhcp-0-191.tlv.redhat.com >> systemd[1]: >> >> >> Stopped >> >> >> >> >>>>>>>>>>> Virtualization daemon. >> >> >> >> >>>>>>>>>>> Jul 16 09:11:04 dhcp-0-191.tlv.redhat.com >> systemd[1]: >> >> >> Starting >> >> >> >> >>>>>>>>>>> Virtualization daemon... >> >> >> >> >>>>>>>>>>> Jul 16 09:11:04 dhcp-0-191.tlv.redhat.com >> systemd[1]: >> >> >> Started >> >> >> >> >>>>>>>>>>> Virtualization daemon. >> >> >> >> >>>>>>>>>>> Jul 16 09:11:09 dhcp-0-191.tlv.redhat.com >> >> libvirtd[6448]: >> >> >> >> >>>>>>>>>>> libvirt >> >> >> >> >>>>>>>>>> version: >> >> >> >> >>>>>>>>>>> 5.0.0, package: 7.module+el8+2887+effa3c42 (Red Hat, >> >> Inc. < >> >> >> >> >>>>>>>>>>> http://bugzilla.redhat.> >> >> >> >> >>>>>>>>>>> Jul 16 09:11:09 dhcp-0-191.tlv.redhat.com >> >> libvirtd[6448]: >> >> >> >> >>>>>>>>>>> hostname: >> >> >> >> >>>>>>>>>>> dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>> Jul 16 09:11:09 dhcp-0-191.tlv.redhat.com >> >> libvirtd[6448]: >> >> >> >> >>>>>>>>>>> End of >> >> >> >> >>>>>>>> file >> >> >> >> >>>>>>>>>> while >> >> >> >> >>>>>>>>>>> reading data: Input/output error >> >> >> >> >>>>>>>>>>> Jul 16 09:11:19 dhcp-0-191.tlv.redhat.com >> >> libvirtd[6448]: >> >> >> >> >>>>>>>>>>> End of >> >> >> >> >>>>>>>> file >> >> >> >> >>>>>>>>>> while >> >> >> >> >>>>>>>>>>> reading data: Input/output error >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> [abawer@dhcp-0-191 ~]$ echo '{"networks": >> {"ovirtmgmt": >> >> >> >> {"nic": >> >> >> >> >>>>>>>>>> "enp0s3", >> >> >> >> >>>>>>>>>>> "bootproto": "dhcp", "defaultRoute": true}}, >> "bondings": >> >> {}, >> >> >> >> >>>>>>>> "options": >> >> >> >> >>>>>>>>>>> {"connectivityCheck": false}}' | vdsm-client >> --insecure >> >> -f - >> >> >> >> >>>>>>>>>>> Host >> >> >> >> >>>>>>>>>>> setupNetworks >> >> >> >> >>>>>>>>>>> { >> >> >> >> >>>>>>>>>>> "code": 0, >> >> >> >> >>>>>>>>>>> "message": "Done" >> >> >> >> >>>>>>>>>>> } >> >> >> >> >>>>>>>>>>> >> >> >> >> >>>>>>>>>>> [abawer@dhcp-0-191 ~]$ >> >> >> >> >>>>>>>>>> Looks fine, great. If networking works fine after >> this >> >> >> change >> >> >> >> >>>>>>>>>> don't >> >> >> >> >>>>>>>>>> forget to run >> >> >> >> >>>>>>>>>> >> >> >> >> >>>>>>>>>> vdsm-client Host setSafeNetworkConfig >> >> >> >> >>>>>>>>>> >> >> >> >> >>>>>>>>>> before reboot to save the configuration. >> >> >> >> >>>>>>>>>> >> >> >> >> >>>>>>>>>> Can you activate the host in Engine now? >> >> >> >> >>>>>>>>>> >> >> >> >> >>>>>>>>>>>> - Are there any details reported about the error in >> >> >> vdsm.log? >> >> >> >> >>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>> seems like the vdsm in non responsive for rpc >> >> although >> >> >> >> >>>>>>>> according to >> >> >> >> >>>>>>>>>>>>>>> vdsm.log it seems the connections are accepted >> during >> >> >> >> >>>>>>>> vdsm-client >> >> >> >> >>>>>>>>>>>>>>> execution. >> >> >> >> >>>>>>>>>>>>>> Just to be sure: Do you have current master? >> >> >> >> >>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>> commit 8d8b74dfbab8514437c1ce3edd05b9bdda834129 >> >> >> >> >>>>>>>>>>>>> (github/master) >> >> >> >> >>>>>>>>>>>>> Author: Nir Soffer <nsoffer(a)redhat.com> >> >> >> >> >>>>>>>>>>>>> Date: Mon Jul 15 03:15:52 2019 +0300 >> >> >> >> >>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>> On top of it i have some local py3 fixes which are >> >> only on >> >> >> >> >>>>>>>>>>>>> storage >> >> >> >> >>>>>>>>>>>> component >> >> >> >> >>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>> OK, should be fine. >> >> >> >> >>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>> Will ask, Thanks. >> >> >> >> >>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>> On Mon, Jul 15, 2019 at 6:28 PM Amit Bawer < >> >> >> >> >>>>>>>> abawer(a)redhat.com> >> >> >> >> >>>>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>>>>>>>> Thanks, but now it hangs for --insecure >> execution >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> echo '{"networks": {"ovirtmgmt": {"nic": >> "ens3", >> >> >> >> >>>>>>>> "bootproto": >> >> >> >> >>>>>>>>>>>> "dhcp", >> >> >> >> >>>>>>>>>>>>>>>>>> "defaultRoute": true}}, "bondings": {}, >> "options": >> >> >> >> >>>>>>>>>>>>>> {"connectivityCheck": >> >> >> >> >>>>>>>>>>>>>>>>>> false}}' | vdsm-client --insecure -f - Host >> >> >> >> >>>>>>>>>>>>>>>>>> setupNetworks >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> Ctrl+C dumps >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> No subscription with >> >> >> >> >>>>>>>>>>>>>>>>>> caf3d1fa-3331-44af-8d54-a65bd5d7d042 >> >> >> >> >>>>>>>> id >> >> >> >> >>>>>>>>>>>>>>>>>> Traceback (most recent call last): >> >> >> >> >>>>>>>>>>>>>>>>>> File "/usr/bin/vdsm-client", line 25, in >> >> <module> >> >> >> >> >>>>>>>>>>>>>>>>>> client.main() >> >> >> >> >>>>>>>>>>>>>>>>>> File >> >> >> >> >>>>>>>> "/usr/lib/python3.6/site-packages/vdsmclient/client.py", >> >> >> >> >>>>>>>>>>>> line >> >> >> >> >>>>>>>>>>>>>>>> 185, >> >> >> >> >>>>>>>>>>>>>>>>>> in main >> >> >> >> >>>>>>>>>>>>>>>>>> result = command(**request_params) >> >> >> >> >>>>>>>>>>>>>>>>>> File >> >> >> >> >>>>>>>>>>>>>>>>>> >> "/usr/lib/python3.6/site-packages/vdsm/client.py", >> >> >> >> >>>>>>>> line >> >> >> >> >>>>>>>>>>>> 289, >> >> >> >> >>>>>>>>>>>>>> in >> >> >> >> >>>>>>>>>>>>>>>>>> _call >> >> >> >> >>>>>>>>>>>>>>>>>> req, timeout=timeout, >> flow_id=self._flow_id) >> >> >> >> >>>>>>>>>>>>>>>>>> File >> >> >> >> >>>>>>>>>>>> >> >> >> "/usr/lib/python3.6/site-packages/yajsonrpc/jsonrpcclient.py", >> >> >> >> >>>>>>>>>>>>>>>> line >> >> >> >> >>>>>>>>>>>>>>>>>> 91, in call >> >> >> >> >>>>>>>>>>>>>>>>>> call.wait(kwargs.get('timeout', CALL_TIMEOUT)) >> >> >> >> >>>>>>>>>>>>>>>>>> File >> >> >> >> >>>>>>>>>>>> >> >> >> "/usr/lib/python3.6/site-packages/yajsonrpc/jsonrpcclient.py", >> >> >> >> >>>>>>>>>>>>>>>> line >> >> >> >> >>>>>>>>>>>>>>>>>> 290, in wait >> >> >> >> >>>>>>>>>>>>>>>>>> self._ev.wait(timeout) >> >> >> >> >>>>>>>>>>>>>>>>>> File "/usr/lib64/python3.6/threading.py", >> line >> >> >> >> >>>>>>>>>>>>>>>>>> 551, in >> >> >> >> >>>>>>>> wait >> >> >> >> >>>>>>>>>>>>>>>>>> signaled = self._cond.wait(timeout) >> >> >> >> >>>>>>>>>>>>>>>>>> File "/usr/lib64/python3.6/threading.py", >> line >> >> >> >> >>>>>>>>>>>>>>>>>> 299, in >> >> >> >> >>>>>>>> wait >> >> >> >> >>>>>>>>>>>>>>>>>> gotit = waiter.acquire(True, timeout) >> >> >> >> >>>>>>>>>>>>>>>>>> KeyboardInterrupt >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>> On Mon, Jul 15, 2019 at 6:15 PM Milan Zamazal >> < >> >> >> >> >>>>>>>>>>>> mzamazal(a)redhat.com> >> >> >> >> >>>>>>>>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>>>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>> On Mon, Jul 15, 2019 at 5:50 PM Milan >> Zamazal < >> >> >> >> >>>>>>>>>>>>>> mzamazal(a)redhat.com> >> >> >> >> >>>>>>>>>>>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> Amit Bawer <abawer(a)redhat.com> writes: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> I followed your RHEL8 vdsm guide, was very >> >> useful >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> for >> >> >> >> >>>>>>>>>>>>>> installing >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsm on >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> RHEL8. >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Though I had to build MOM locally and it >> >> doesn't >> >> >> >> >>>>>>>> seem to >> >> >> >> >>>>>>>>>>>> fully >> >> >> >> >>>>>>>>>>>>>>>> work >> >> >> >> >>>>>>>>>>>>>>>>>>> on >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> RHEL8 yet. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> I don't think MoM is required for >> anything, you >> >> >> >> >>>>>>>>>>>>>>>>>>>>> should >> >> >> >> >>>>>>>> be >> >> >> >> >>>>>>>>>>>> able to >> >> >> >> >>>>>>>>>>>>>>>> run >> >> >> >> >>>>>>>>>>>>>>>>>>>>> Vdsm happily without it and `vdsm' package >> >> >> currently >> >> >> >> >>>>>>>>>> doesn't >> >> >> >> >>>>>>>>>>>>>> depend >> >> >> >> >>>>>>>>>>>>>>>> on >> >> >> >> >>>>>>>>>>>>>>>>>>>>> it on RHEL 8. A fix was posted for one >> issue >> >> >> today: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> https://gerrit.ovirt.org/101804. If you >> have >> >> any >> >> >> >> >>>>>>>> other >> >> >> >> >>>>>>>>>>>> troubles >> >> >> >> >>>>>>>>>>>>>>>> with >> >> >> >> >>>>>>>>>>>>>>>>>>>>> MoM, please report them to Andrej Krejčíř < >> >> >> >> >>>>>>>>>>>> akrejcir(a)redhat.com>. >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Next step is to test attach NFS domain, >> have >> >> to >> >> >> set >> >> >> >> >>>>>>>> up an >> >> >> >> >>>>>>>>>>>>>> engine >> >> >> >> >>>>>>>>>>>>>>>>>>> first >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> since it seems that vdsm-client is not the >> >> >> >> >>>>>>>>>> straightforward >> >> >> >> >>>>>>>>>>>>>> choice >> >> >> >> >>>>>>>>>>>>>>>> for >> >> >> >> >>>>>>>>>>>>>>>>>>>>> this >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> operation. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> Please note that since host deploy etc. is >> not >> >> >> fully >> >> >> >> >>>>>>>>>> working >> >> >> >> >>>>>>>>>>>> yet >> >> >> >> >>>>>>>>>>>>>>>> it's a >> >> >> >> >>>>>>>>>>>>>>>>>>>>> bit tricky to attach a RHEL 8 host to >> Engine. >> >> But >> >> >> >> >>>>>>>>>>>>>>>>>>>>> it's >> >> >> >> >>>>>>>>>>>> doable. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - A host is added to Engine. Its >> installation >> >> will >> >> >> >> >>>>>>>> fail, >> >> >> >> >>>>>>>>>> but >> >> >> >> >>>>>>>>>>>>>> Engine >> >> >> >> >>>>>>>>>>>>>>>>>>>>> will know about the host. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - Vdsm can be installed and run manually >> on the >> >> >> host, >> >> >> >> >>>>>>>>>> you've >> >> >> >> >>>>>>>>>>>>>> already >> >> >> >> >>>>>>>>>>>>>>>>>>>>> done that. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - You need to set up `ovirtmgmt' network in >> >> order >> >> >> to >> >> >> >> >>>>>>>> talk >> >> >> >> >>>>>>>>>> with >> >> >> >> >>>>>>>>>>>>>>>> Engine. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> Here is what I've used on the host, based >> on >> >> >> advice >> >> >> >> >>>>>>>> from >> >> >> >> >>>>>>>>>>>>>> network >> >> >> >> >>>>>>>>>>>>>>>>>>> guys: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> echo '{"networks": {"ovirtmgmt": {"nic": >> >> "ens3", >> >> >> >> >>>>>>>>>>>> "bootproto": >> >> >> >> >>>>>>>>>>>>>>>>>>> "dhcp", >> >> >> >> >>>>>>>>>>>>>>>>>>>>> "defaultRoute": true}}, "bondings": {}, >> >> "options": >> >> >> >> >>>>>>>>>>>>>>>>>>> {"connectivityCheck": >> >> >> >> >>>>>>>>>>>>>>>>>>>>> false}}' | vdsm-client -f - Host >> setupNetworks >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>> gives me >> >> >> >> >>>>>>>>>>>>>>>>>>>> �� vdsm-client: Connection to >> localhost:54321 >> >> with >> >> >> >> >>>>>>>>>> use_tls=True, >> >> >> >> >>>>>>>>>>>>>>>>>>> timeout=60 >> >> >> >> >>>>>>>>>>>>>>>>>>>> failed: [Errno 13] Permission denied >> >> >> >> >>>>>>>>>>>>>>>>>>>> for either local user or root user >> >> >> >> >>>>>>>>>>>>>>>>>>> I think I experienced something similar when >> I >> >> >> >> >>>>>>>>>>>>>>>>>>> installed >> >> >> >> >>>>>>>> the >> >> >> >> >>>>>>>>>>>>>>>>>>> certificates to /etc/pki/vdsm from another >> host >> >> and >> >> >> >> >>>>>>>> forgot to >> >> >> >> >>>>>>>>>>>> change >> >> >> >> >>>>>>>>>>>>>>>>>>> their owners to vdsm:kvm. You may also try >> to >> >> >> disable >> >> >> >> >>>>>>>> ssl in >> >> >> >> >>>>>>>>>>>>>> vdsm.conf >> >> >> >> >>>>>>>>>>>>>>>>>>> (don't forget to run `vdsm-tool configure' >> >> >> afterwards) >> >> >> >> >>>>>>>> and run >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsm-client with --insecure option. >> >> >> >> >>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm-client Host setSafeNetworkConfig >> >> >> >> >>>>>>>>>>>>>>>>>>>>> reboot >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> ("ens3" above is my default network >> >> interface >> >> >> >> >>>>>>>>>>>>>>>>>>>>> on the >> >> >> >> >>>>>>>>>> host.) >> >> >> >> >>>>>>>>>>>>>>>>>>>>> Beware the first command (or other >> commands) >> >> may >> >> >> >> >>>>>>>>>> disconnect >> >> >> >> >>>>>>>>>>>> you >> >> >> >> >>>>>>>>>>>>>>>> from >> >> >> >> >>>>>>>>>>>>>>>>>>>>> the host and leave the host disconnected, >> so be >> >> >> sure >> >> >> >> >>>>>>>> to >> >> >> >> >>>>>>>>>>>> perform >> >> >> >> >>>>>>>>>>>>>>>> the >> >> >> >> >>>>>>>>>>>>>>>>>>>>> commands from a console in case you decide >> to >> >> >> >> >>>>>>>> configure >> >> >> >> >>>>>>>>>>>>>> networking >> >> >> >> >>>>>>>>>>>>>>>>>>>>> this way. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - In case you use TLS communication with >> >> Engine, >> >> >> it >> >> >> >> >>>>>>>> may be >> >> >> >> >>>>>>>>>>>>>>>> necessary to >> >> >> >> >>>>>>>>>>>>>>>>>>>>> set up the certificates manually (while >> Engine >> >> >> enroll >> >> >> >> >>>>>>>>>>>>>> certificate >> >> >> >> >>>>>>>>>>>>>>>>>>>>> operation seemed to report success in the >> UI, >> >> the >> >> >> >> >>>>>>>>>>>> certificates >> >> >> >> >>>>>>>>>>>>>>>>>>> weren't >> >> >> >> >>>>>>>>>>>>>>>>>>>>> installed for me). That means (courtesy to >> >> Marcin >> >> >> >> >>>>>>>>>> Sobczyk >> >> >> >> >>>>>>>>>>>> for >> >> >> >> >>>>>>>>>>>>>>>>>>>>> providing these tips): >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - Enable legacy crypto policies: >> >> >> >> >>>>>>>> update-crypto-policies >> >> >> >> >>>>>>>>>>>> --set >> >> >> >> >>>>>>>>>>>>>>>> LEGACY >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - On the host side, copy /etc/pki/vdsm from >> >> some >> >> >> host >> >> >> >> >>>>>>>>>>>> already >> >> >> >> >>>>>>>>>>>>>>>>>>>>> successfully connected to the same Engine. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> - On the Engine side, copy >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> /etc/pki/ovirt-engine/requests/HOSTNAME.com.req >> >> >> for >> >> >> >> >>>>>>>>>> your >> >> >> >> >>>>>>>>>>>> host >> >> >> >> >>>>>>>>>>>>>>>> named >> >> >> >> >>>>>>>>>>>>>>>>>>>>> HOSTNAME from an already connected host. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> When not using TLS, no further special >> >> >> >> >>>>>>>>>>>>>>>>>>>>> arrangements >> >> >> >> >>>>>>>>>> should >> >> >> >> >>>>>>>>>>>> be >> >> >> >> >>>>>>>>>>>>>>>>>>>>> necessary. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> Thank you for info, please tell me when you >> >> have >> >> >> >> >>>>>>>> anything >> >> >> >> >>>>>>>>>> new >> >> >> >> >>>>>>>>>>>> or >> >> >> >> >>>>>>>>>>>>>> you >> >> >> >> >>>>>>>>>>>>>>>>>>>>> need some help. >> >> >> >> >>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> [root@dhcp-0-191 ~]# uname -rn >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> dhcp-0-191.tlv.redhat.com >> >> 4.18.0-80.el8.x86_64 >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> [root@dhcp-0-191 ~]# systemctl status >> vdsmd >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> ● vdsmd.service - Virtual Desktop Server >> >> Manager >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Loaded: loaded >> >> >> >> >>>>>>>> (/usr/lib/systemd/system/vdsmd.service; >> >> >> >> >>>>>>>>>>>>>> enabled; >> >> >> >> >>>>>>>>>>>>>>>>>>> vendor >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> preset: enabled) >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Active: active (running) since Mon >> >> >> 2019-07-15 >> >> >> >> >>>>>>>> 09:02:06 >> >> >> >> >>>>>>>>>>>> EDT; >> >> >> >> >>>>>>>>>>>>>>>> 36min >> >> >> >> >>>>>>>>>>>>>>>>>>> ago >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Process: 1863 >> >> >> >> >>>>>>>>>>>>>>>> >> ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> --pre-start (code=exited, >> status=0/SUCCESS) >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Main PID: 1978 (vdsmd) >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Tasks: 38 (limit: 11516) >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Memory: 63.6M >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> CGroup: /system.slice/vdsmd.service >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> └─1978 >> >> /usr/libexec/platform-python >> >> >> >> >>>>>>>>>>>>>>>> /usr/share/vdsm/vdsmd >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:05 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running prepare_transient_repository >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:05 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running syslog_available >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:05 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running nwfilter >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:06 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running dummybr >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:06 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running tune_system >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:06 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running test_space >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:06 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>>>>>>>>>>>>> vdsmd_init_common.sh[1863]: >> >> >> >> >>>>>>>>>>>>>>>>>>>>> vdsm: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Running test_lo >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:06 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> systemd[1]: >> >> >> >> >>>>>>>>>>>> Started >> >> >> >> >>>>>>>>>>>>>>>>>>> Virtual >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Desktop Server Manager. >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:08 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsm[1978]: >> >> >> >> >>>>>>>>>> WARN >> >> >> >> >>>>>>>>>>>> MOM >> >> >> >> >>>>>>>>>>>>>>>> not >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> available. >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> Jul 15 09:02:08 dhcp-0-191.tlv.redhat.com >> >> >> >> >>>>>>>> vdsm[1978]: >> >> >> >> >>>>>>>>>> WARN >> >> >> >> >>>>>>>>>>>> MOM >> >> >> >> >>>>>>>>>>>>>>>> not >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> available, KSM stats will be missing. >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> >> >> >> >> >>>>>>>>>>>>>>>>>>>>>> On Mon, Jul 15, 2019 at 4:11 PM Milan >> Zamazal >> >> < >> >> >> >> >>>>>>>>>>>>>>>> mzamazal(a)redhat.com> >> >> >> >> >>>>>>>>>>>>>>>>>>>>> wrote: >> >> >> >> >>>>>>>>>>>>>>>>>>>>>>> Hi Amit, how is it going with your work >> on >> >> PoC >> >> >> >> >>>>>>>> NFS? Do >> >> >> >> >>>>>>>>>> you >> >> >> >> >>>>>>>>>>>>>> need >> >> >> >> >>>>>>>>>>>>>>>>>>> help >> >> >> >> >>>>>>>>>>>>>>>>>>>>>>> with anything? Is there anything to >> >> experiment >> >> >> >> >>>>>>>> with? >> >> >> >> >> >> >> >> >> >> > >

4 13

What is involved in adding new CPU support?
by Matt Mossholder 31 Jul '19

31 Jul '19

Hi everyone, I am interested in adding Ryzen/Ryzen 2 / Ryzen 3 CPU support to OVirt. I've seen a few references on the net to people adding in EPYC support by updating a PostgresSQL DB table (e.g. https://lists.ovirt.org/archives/list/users@ovirt.org/thread/T3XL6NU7SUPYLY… ). Would this really be all that is needed? If so, how do I determine the correct string to add to the table? If EYPC is "7:AMD EPYC:svm,nx,model_EPYC:EPYC:x86_64;", would Ryzen be something like "7:AMD RYZEN:svm,nx,model_RYZEN:RYZEN:x86_64;"? --Matt

3 2

getStats exception in Engine
by Ales Musil 31 Jul '19

31 Jul '19

Hi, yesterday we have found out that there is exception thrown in getStats. The host that was hitting this stayed in connecting state infinitely. This is caused by recent mom version upgrade in vdsm spec. Mom statistic for 'ksmCpu' is reported as double instead of integer. I have posted workaround [1] for the vdsm until the proper fix is provided. Thanks. Regards, Ales [1] https://gerrit.ovirt.org/c/102293/ -- Ales Musil Associate Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

2 1

Failure to run engine-setup
by Eyal Shenitzky 30 Jul '19

30 Jul '19

Hi All, I am failing to run engine-setup due to the following issue: [ INFO ] Generating post install configuration file '/home/eshenitz/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' [ ERROR ] Failed to execute stage 'Misc configuration': a bytes-like object is required, not 'str' [ INFO ] Rolling back database schema In the setup log I can see - 2019-07-30 10:41:31,418+0300 DEBUG otopi.transaction transaction._prepare:61 preparing 'File transaction for '/home/eshenitz/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-s etup-ovirt-post.conf'' 2019-07-30 10:41:31,418+0300 DEBUG otopi.filetransaction filetransaction.prepare:184 file '/home/eshenitz/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.con f' missing 2019-07-30 10:41:31,419+0300 DEBUG otopi.transaction transaction._prepare:66 exception during prepare phase Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/transaction.py", line 62, in _prepare element.prepare() File "/usr/lib/python3.6/site-packages/otopi/filetransaction.py", line 253, in prepare os.write(fd, self._content) TypeError: a bytes-like object is required, not 'str' 2019-07-30 10:41:31,420+0300 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/home/eshenitz/ovirt-engine/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core/postinstall.py", line 98, in _misc otopicons.CoreEnv.MODIFIED_FILES File "/usr/lib/python3.6/site-packages/otopi/transaction.py", line 106, in append self._prepare(element=element) File "/usr/lib/python3.6/site-packages/otopi/transaction.py", line 62, in _prepare element.prepare() File "/usr/lib/python3.6/site-packages/otopi/filetransaction.py", line 253, in prepare os.write(fd, self._content) TypeError: a bytes-like object is required, not 'str' 2019-07-30 10:41:31,421+0300 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': a bytes-like object is required, not 'str' 2019-07-30 10:41:31,421+0300 DEBUG otopi.transaction transaction.abort:119 aborting 'CinderLib Database Transaction' Does anyone encounter it? Thanks, -- Regards, Eyal Shenitzky

3 2

ovirt-engine has been tagged (ovirt-engine-4.3.6)
by Tal Nisan 30 Jul '19

30 Jul '19

1 0

vdsm has been tagged (v4.30.25)
by Milan Zamazal 30 Jul '19

30 Jul '19

1 0

Jenkins CI: "Testing system error"
by Amit Bawer 29 Jul '19

29 Jul '19

Lately we are experiencing check-patch issues where CI check-patch results with "Testing system error".[1] Is there a planned action to resolve those issues? [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8995/artifact/ci_bu… Thanks.

2 3

[OST] flaky storage test?
by Michal Skrivanek 26 Jul '19

26 Jul '19

Hi, want to report a random failure I got in live_storage_migration test[1] as far as I can tell. I found stuck libvirt/qemu in vdsm logs[2], seemingly on storage access, no idea why. It passed afterwards in [3] with same binaries Thanks, michal [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159 [2] cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159/artifact/expor… [3] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5162

2 2

Re: Failed engine-setup role test
by Yedidyah Bar David 25 Jul '19

25 Jul '19

Adding devel, so that I can link from https://gerrit.ovirt.org/98595 . On Mon, Mar 18, 2019 at 1:21 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > Il dom 17 mar 2019, 11:41 Yedidyah Bar David <didi(a)redhat.com> ha scritto: > >> On Fri, Mar 15, 2019 at 7:27 PM Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> Hi, >>> I was trying to setup engine on my systems using ansible >>> >>> my playbook: >>> --- >>> - name: Setup oVirt >>> hosts: ovirt4.home >>> vars_files: >>> # Contains encrypted `ovirt_engine_setup_admin_password` variable >>> using ansible-vault >>> - password.yml >>> vars: >>> ovirt_engine_setup_version: '4.3' >>> ovirt_engine_setup_product_type: oVirt >>> roles: >>> - ovirt.engine-setup >>> >> >> I think this happens when you run engine-setup and supply an ovn user but >> no password. >> >> The bottom-of-the-stack failure reason is calling .decode on None, which >> was done for supporting also python3. Fixing this can be done e.g. by >> https://gerrit.ovirt.org/98595 . Didn't test and not sure that's enough. >> >> We might decide to fix by changing the logic upper in the stack, though, >> or by fixing the role/playbook to supply also a password. >> >> At a minimum, someone needs to decide what we want the role to do wrt to >> ovn. Do we want it to be set up automatically? Using engine admin >> user/password? If so, please open a bug on the role. >> >> > > > I will open the bug. in the meantime I confirm that adding ovn password to > the vault fixes the problem > OK. Did you? > > > > > > >>> >>> Using 1.1.9 >>> >>> >>> >>> Got this error: >>> TASK [ovirt.engine-setup : Run engine-setup with answerfile] >>> ****************************************************************************************************************************************************** >>> fatal: [ovirt4.home]: FAILED! => {"changed": true, "cmd": >>> ["engine-setup", "--accept-defaults", >>> "--config-append=/tmp/answerfile-20190315180843Z.txt"], "delta": >>> "0:09:54.716435", "end": "2019-03-15 18:18:44.658774", "msg": "non-zero >>> return code", "rc": 1, "start": "2019-03-15 18:08:49.942339", "stderr": "", >>> "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ INFO ] >>> Stage: Environment setup\n Configuration files: >>> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', >>> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', >>> '/tmp/answerfile-20190315180843Z.txt']\n Log file: >>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20190315180850-ufar83.log\n >>> Version: otopi-1.8.1 (otopi-1.8.1-1.el7)\n[ INFO ] Stage: >>> Environment packages setup\n[ INFO ] Stage: Programs detection\n[ INFO ] >>> Stage: Environment setup (late)\n[ INFO ] Stage: Environment >>> customization\n \n --== PRODUCT OPTIONS ==--\n \n >>> Set up Cinderlib integration\n (Currently in tech >>> preview)\n (Yes, No) [No]: \n Configure Engine on this >>> host (Yes, No) [Yes]: \n Configure Image I/O Proxy on this host >>> (Yes, No) [Yes]: \n Configure WebSocket Proxy on this host (Yes, >>> No) [Yes]: \n Configure VM Console Proxy on this host (Yes, No) >>> [Yes]: \n \n --== PACKAGES ==--\n \n[ INFO ] >>> Checking for product updates...\n[ INFO ] No product updates found\n >>> \n --== NETWORK CONFIGURATION ==--\n \n Host >>> fully qualified DNS name of this server [ovirt4.home]: \n[WARNING] Failed >>> to resolve ovirt4.home using DNS, it can be resolved only locally\n[ INFO >>> ] firewalld will be configured as firewall manager.\n \n >>> --== DATABASE CONFIGURATION ==--\n \n Where is the Engine >>> database located? (Local, Remote) [Local]: \n Setup can configure >>> the local postgresql server automatically for the engine to run. This may >>> conflict with existing applications.\n Would you like Setup to >>> automatically configure postgresql and create Engine database, or prefer to >>> perform that manually? (Automatic, Manual) [Automatic]: \n \n >>> --== OVIRT ENGINE CONFIGURATION ==--\n \n Application >>> mode (Virt, Gluster, Both) [Both]: \n \n --== STORAGE >>> CONFIGURATION ==--\n \n Default SAN wipe after delete >>> (Yes, No) [No]: \n \n --== PKI CONFIGURATION ==--\n >>> \n Organization name for certificate [home]: \n \n >>> --== APACHE CONFIGURATION ==--\n \n Setup can configure >>> the default page of the web server to present the application home page. >>> This may conflict with existing applications.\n Do you wish to set >>> the application as the default page of the web server? (Yes, No) [Yes]: \n >>> Setup can configure apache to use SSL using a certificate issued >>> from the internal CA.\n Do you wish Setup to configure that, or >>> prefer to perform that manually? (Automatic, Manual) [Automatic]: \n >>> \n --== SYSTEM CONFIGURATION ==--\n \n \n >>> --== MISC CONFIGURATION ==--\n \n Please choose Data >>> Warehouse sampling scale:\n (1) Basic\n (2) Full\n >>> (1, 2)[1]: \n \n --== END OF CONFIGURATION ==--\n >>> \n[ INFO ] Stage: Setup validation\n[WARNING] Less than 16384MB of memory >>> is available\n \n --== CONFIGURATION PREVIEW ==--\n >>> \n Application mode : both\n >>> Default SAN wipe after delete : False\n Firewall >>> manager : firewalld\n Update Firewall >>> : True\n Host FQDN >>> : ovirt4.home\n Set up Cinderlib integration : >>> False\n Configure local Engine database : True\n >>> Set application as default page : True\n Configure Apache >>> SSL : True\n Engine database secured >>> connection : False\n Engine database user name >>> : engine\n Engine database name : engine\n >>> Engine database host : localhost\n Engine >>> database port : 5432\n Engine database host >>> name validation : False\n Engine installation >>> : True\n PKI organization : home\n >>> Set up ovirt-provider-ovn : True\n Configure >>> WebSocket Proxy : True\n DWH installation >>> : True\n DWH database secured connection : >>> False\n DWH database host : localhost\n >>> DWH database user name : ovirt_engine_history\n >>> DWH database name : ovirt_engine_history\n >>> DWH database port : 5432\n DWH database host >>> name validation : False\n Configure local DWH database >>> : True\n Configure Image I/O Proxy : True\n >>> Configure VMConsole Proxy : True\n \n >>> Please confirm installation settings (OK, Cancel) [OK]: \n[ INFO ] Stage: >>> Transaction setup\n[ INFO ] Stopping engine service\n[ INFO ] Stopping >>> ovirt-fence-kdump-listener service\n[ INFO ] Stopping dwh service\n[ INFO >>> ] Stopping Image I/O Proxy service\n[ INFO ] Stopping vmconsole-proxy >>> service\n[ INFO ] Stopping websocket-proxy service\n[ INFO ] Stage: Misc >>> configuration (early)\n[ INFO ] Stage: Package installation\n[ INFO ] >>> Stage: Misc configuration\n[ INFO ] Upgrading CA\n[ INFO ] Initializing >>> PostgreSQL\n[ INFO ] Creating PostgreSQL 'engine' database\n[ INFO ] >>> Configuring PostgreSQL\n[ INFO ] Creating PostgreSQL >>> 'ovirt_engine_history' database\n[ INFO ] Configuring PostgreSQL\n[ INFO >>> ] Creating CA\n[ INFO ] Creating/refreshing DWH database schema\n[ INFO ] >>> Configuring Image I/O Proxy\n[ INFO ] Setting up ovirt-vmconsole proxy >>> helper PKI artifacts\n[ INFO ] Setting up ovirt-vmconsole SSH PKI >>> artifacts\n[ INFO ] Configuring WebSocket Proxy\n[ INFO ] >>> Creating/refreshing Engine database schema\n[ INFO ] Creating/refreshing >>> Engine 'internal' domain database schema\n[ INFO ] Creating default mac >>> pool range\n[ INFO ] Adding default OVN provider to database\n[ ERROR ] >>> Failed to execute stage 'Misc configuration': 'NoneType' object has no >>> attribute 'decode'\n[ INFO ] Yum Performing yum transaction rollback\n[ >>> INFO ] Rolling back DWH database schema\n[ INFO ] Clearing DWH database >>> ovirt_engine_history\n[ INFO ] Rolling back database schema\n[ INFO ] >>> Clearing Engine database engine\n[ INFO ] Stage: Clean up\n Log >>> file is located at >>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20190315180850-ufar83.log\n[ >>> INFO ] Generating answer file >>> '/var/lib/ovirt-engine/setup/answers/20190315181844-setup.conf'\n[ INFO ] >>> Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution >>> of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ >>> INFO ] Stage: Environment setup", " Configuration files: >>> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', >>> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', >>> '/tmp/answerfile-20190315180843Z.txt']", " Log file: >>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20190315180850-ufar83.log", >>> " Version: otopi-1.8.1 (otopi-1.8.1-1.el7)", "[ INFO ] Stage: >>> Environment packages setup", "[ INFO ] Stage: Programs detection", "[ >>> INFO ] Stage: Environment setup (late)", "[ INFO ] Stage: Environment >>> customization", " ", " --== PRODUCT OPTIONS ==--", " >>> ", " Set up Cinderlib integration", " (Currently in >>> tech preview)", " (Yes, No) [No]: ", " Configure Engine >>> on this host (Yes, No) [Yes]: ", " Configure Image I/O Proxy on >>> this host (Yes, No) [Yes]: ", " Configure WebSocket Proxy on this >>> host (Yes, No) [Yes]: ", " Configure VM Console Proxy on this host >>> (Yes, No) [Yes]: ", " ", " --== PACKAGES ==--", " >>> ", "[ INFO ] Checking for product updates...", "[ INFO ] No product >>> updates found", " ", " --== NETWORK CONFIGURATION ==--", >>> " ", " Host fully qualified DNS name of this server >>> [ovirt4.home]: ", "[WARNING] Failed to resolve ovirt4.home using DNS, it >>> can be resolved only locally", "[ INFO ] firewalld will be configured as >>> firewall manager.", " ", " --== DATABASE CONFIGURATION >>> ==--", " ", " Where is the Engine database located? >>> (Local, Remote) [Local]: ", " Setup can configure the local >>> postgresql server automatically for the engine to run. This may conflict >>> with existing applications.", " Would you like Setup to >>> automatically configure postgresql and create Engine database, or prefer to >>> perform that manually? (Automatic, Manual) [Automatic]: ", " ", " >>> --== OVIRT ENGINE CONFIGURATION ==--", " ", " >>> Application mode (Virt, Gluster, Both) [Both]: ", " ", " >>> --== STORAGE CONFIGURATION ==--", " ", " Default SAN wipe >>> after delete (Yes, No) [No]: ", " ", " --== PKI >>> CONFIGURATION ==--", " ", " Organization name for >>> certificate [home]: ", " ", " --== APACHE CONFIGURATION >>> ==--", " ", " Setup can configure the default page of the >>> web server to present the application home page. This may conflict with >>> existing applications.", " Do you wish to set the application as >>> the default page of the web server? (Yes, No) [Yes]: ", " Setup >>> can configure apache to use SSL using a certificate issued from the >>> internal CA.", " Do you wish Setup to configure that, or prefer to >>> perform that manually? (Automatic, Manual) [Automatic]: ", " ", " >>> --== SYSTEM CONFIGURATION ==--", " ", " ", " >>> --== MISC CONFIGURATION ==--", " ", " Please choose Data >>> Warehouse sampling scale:", " (1) Basic", " (2) Full", " >>> (1, 2)[1]: ", " ", " --== END OF CONFIGURATION >>> ==--", " ", "[ INFO ] Stage: Setup validation", "[WARNING] Less >>> than 16384MB of memory is available", " ", " --== >>> CONFIGURATION PREVIEW ==--", " ", " Application mode >>> : both", " Default SAN wipe after delete >>> : False", " Firewall manager : >>> firewalld", " Update Firewall : True", " >>> Host FQDN : ovirt4.home", " >>> Set up Cinderlib integration : False", " Configure >>> local Engine database : True", " Set application as >>> default page : True", " Configure Apache SSL >>> : True", " Engine database secured connection : False", >>> " Engine database user name : engine", " >>> Engine database name : engine", " Engine >>> database host : localhost", " Engine database >>> port : 5432", " Engine database host name >>> validation : False", " Engine installation >>> : True", " PKI organization : home", " >>> Set up ovirt-provider-ovn : True", " Configure >>> WebSocket Proxy : True", " DWH installation >>> : True", " DWH database secured connection : >>> False", " DWH database host : localhost", " >>> DWH database user name : ovirt_engine_history", " >>> DWH database name : ovirt_engine_history", " >>> DWH database port : 5432", " DWH >>> database host name validation : False", " Configure local >>> DWH database : True", " Configure Image I/O Proxy >>> : True", " Configure VMConsole Proxy : >>> True", " ", " Please confirm installation settings (OK, >>> Cancel) [OK]: ", "[ INFO ] Stage: Transaction setup", "[ INFO ] Stopping >>> engine service", "[ INFO ] Stopping ovirt-fence-kdump-listener service", >>> "[ INFO ] Stopping dwh service", "[ INFO ] Stopping Image I/O Proxy >>> service", "[ INFO ] Stopping vmconsole-proxy service", "[ INFO ] Stopping >>> websocket-proxy service", "[ INFO ] Stage: Misc configuration (early)", "[ >>> INFO ] Stage: Package installation", "[ INFO ] Stage: Misc >>> configuration", "[ INFO ] Upgrading CA", "[ INFO ] Initializing >>> PostgreSQL", "[ INFO ] Creating PostgreSQL 'engine' database", "[ INFO ] >>> Configuring PostgreSQL", "[ INFO ] Creating PostgreSQL >>> 'ovirt_engine_history' database", "[ INFO ] Configuring PostgreSQL", "[ >>> INFO ] Creating CA", "[ INFO ] Creating/refreshing DWH database schema", >>> "[ INFO ] Configuring Image I/O Proxy", "[ INFO ] Setting up >>> ovirt-vmconsole proxy helper PKI artifacts", "[ INFO ] Setting up >>> ovirt-vmconsole SSH PKI artifacts", "[ INFO ] Configuring WebSocket >>> Proxy", "[ INFO ] Creating/refreshing Engine database schema", "[ INFO ] >>> Creating/refreshing Engine 'internal' domain database schema", "[ INFO ] >>> Creating default mac pool range", "[ INFO ] Adding default OVN provider to >>> database", "[ ERROR ] Failed to execute stage 'Misc configuration': >>> 'NoneType' object has no attribute 'decode'", "[ INFO ] Yum Performing yum >>> transaction rollback", "[ INFO ] Rolling back DWH database schema", "[ >>> INFO ] Clearing DWH database ovirt_engine_history", "[ INFO ] Rolling >>> back database schema", "[ INFO ] Clearing Engine database engine", "[ >>> INFO ] Stage: Clean up", " Log file is located at >>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20190315180850-ufar83.log", >>> "[ INFO ] Generating answer file >>> '/var/lib/ovirt-engine/setup/answers/20190315181844-setup.conf'", "[ INFO >>> ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] >>> Execution of setup failed"]} >>> >>> Attaching engine-setup logs >>> >>> I was running the playbook from my laptop, the engine host is a vm on >>> the same network. >>> >>> -- >>> >>> SANDRO BONAZZOLA >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://red.ht/sig> >>> >> >> >> -- >> Didi >> > -- Didi

2 1

CI failing
by Michal Skrivanek 24 Jul '19

24 Jul '19

it’s been on and off in the past ~2 weeks, it’s still failing way too often. Right now with: 10:12:25 failure: repodata/0b87a97f332e1a7bf059abebf295df6a785df123470cc371c2b6c1a7b8f87f95-primary.sqlite.bz2 from updates-testing: [Errno 256] No more mirrors to try. 10:12:25 http://download.fedoraproject.org/pub/fedora/linux/updates/testing/29/Every…: [Errno 14] HTTPS Error 404 - Not Found Thanks, michal

2 3

planned Jenkins restart
by Evgheni Dereveanchin 24 Jul '19

24 Jul '19

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 back online. -- Regards, Evgheni Dereveanchin

1 1

Why filetransaction needs to encode the content to utf-8?
by Yedidyah Bar David 23 Jul '19

23 Jul '19

Hi Nir and all, In [1] you added line 151, to encode the contents to utf-8. Do you remember why you needed that? What happens if I remove this line? I am working on [2]. It fails on that line, because the current content, if organization name is unicode, has a UTF-8 encoded string already, but is a python str (not unicode). Tried patching otopi [3], did a few attempts (some of them also pushed there, check the different patchsets), but none worked. So I am going to patch postinstall file generation instead [4], but I don't like this. Any hints are welcome. Thanks and best regards, [1] https://gerrit.ovirt.org/#/c/92435/1/src/otopi/filetransaction.py [2] https://bugzilla.redhat.com/show_bug.cgi?id=1729511 [3] https://gerrit.ovirt.org/102085 [4] https://gerrit.ovirt.org/102089 -- Didi

3 2

ioprocess-1.2.1 for ovirt 4.3.6
by Nir Soffer 23 Jul '19

23 Jul '19

This is a requirement for supporting 4k in ovirt 4.3.6. We have a build for RHEL: https://bugzilla.redhat.com/1728953 We need build for CentOS 7 - currently providing only: ioprocess-1.1.2-1.el7.x86_64.rpm Vdsm requires 1.2.1 for about 2 weeks, and OST builds pass, probably consuming 1.2.1 from ovirt repositories. https://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/x86_64/ But CI on 4.3 fails with: Error: Package: vdsm-python-4.30.24-48.gitcc1fe4e.el7.noarch (artifacts) Requires: python-ioprocess >= 1.2.1 Installed: python2-ioprocess-1.1.2-1.201903201036.gita80158c.el7.x86_64 (@tested) python-ioprocess = 1.1.2 Available: python-ioprocess-0.15.1-1.el7.noarch (epel-el7) python-ioprocess = 0.15.1-1.el7 Available: python-ioprocess-0.16.1-1.el7.noarch (centos-ovirt-common-candidate) python-ioprocess = 0.16.1-1.el7 Available: python2-ioprocess-1.1.2-1.el7.x86_64 (centos-ovirt42-testing-x86_64) python-ioprocess = 1.1.2 See https://gerrit.ovirt.org/c/101951/ So either CI on 4.3 is missing the repo providing this version, or this build needs to be elsewhere, probably in: https://cbs.centos.org/repos/virt7-ovirt-43-testing/x86_64/os/Packages/ Nir

4 5

What values should i give in this ovirt api to get the correct response
by smidhunraj＠gmail.com 22 Jul '19

22 Jul '19

I am following this link. https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html… I got response for GET /api/vms/4ef8b995-ae58-49d6-8980-ef0fa6688d92/snapshots/1b94ca4e-8c03-4166-8d29-2b831e24b90e/disks HTTP/1.1 Accept: application/xml Content-type: application/xml Identify disk id "Array ( [disk] => Array ( [0] => Array ( [actual_size] => 0 [alias] => GlanceDisk-8700235 [format] => cow [image_id] => a42bda58-7556-4ebe-a54d-03dc0a3b1f54 [propagate_errors] => false [provisioned_size] => 8589934592 [read_only] => false [shareable] => false [sparse] => true [status] => ok [storage_type] => image [wipe_after_delete] => false [snapshot] => Array ( [id] => 1b94ca4e-8c03-4166-8d29-2b831e24b90e ) [storage_domains] => Array ( [storage_domain] => Array ( [0] => Array ( [id] => ad6aea6d-ff90-457f-98eb-99380949e23a ) ) ) [name] => GlanceDisk-8700235 [description] => CentOS 7 Generic Cloud Image v1711 for x86_64 (8700235) [id] => dded245b-4a73-48b4-a1b4-ba98c37490ad ) What is the values that i have to give to the POST request in this api POST /api/vms/22222222-2222-2222-2222-222222222222/disks/ HTTP/1.1 Accept: application/xml Content-type: application/xml <disk id="11111111-1111-1111-1111-111111111111"> <snapshot id="11111111-1111-1111-1111-111111111111"/> <active>true</active> </disk> to replace 1)vms ===>> 22222222-2222-2222-2222-222222222222 2)disk id 11111111-1111-1111-1111-111111111111 3)snapshot id 11111111-1111-1111-1111-111111111111

2 1

Jenkins build fails to clone gerrit repo
by Vojtech Juranek 21 Jul '19

21 Jul '19

Hi, lots of Jenkin jobs fail as they cannot fetch git repo from gerrit: 17:35:32 Fetching upstream changes from https://gerrit.ovirt.org/vdsm 17:35:32 > git --version # timeout=10 17:35:32 > git fetch --tags --progress https://gerrit.ovirt.org/vdsm +refs/heads/*:refs/remotes/origin/* 17:36:38 ERROR: Error cloning remote repo 'origin' 17:36:38 hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/vdsm +refs/heads/*:refs/remotes/origin/*" returned status code 128: 17:36:38 stdout: 17:36:38 stderr: error: RPC failed; result=22, HTTP code = 502 17:36:38 fatal: The remote end hung up unexpectedly see e.g. [1, 2, 3] for more details, to name couple of examples. Can someone take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8277/console [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8285/console [3] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/8291/console

2 1

[Ovirt] [CQ weekly status] [19-07-2019]
by Dusan Fodor 19 Jul '19

19 Jul '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) Last failure was on 02-07 for ovirt-provider-ovm due to failed test: 098_ovirt_provider_ovn.use_ovn_provide. This was a code regression and which was fixed. *CQ-4.3*: GREEN (#1) Last failure was on 12-07 for ovirt-provider-ovm due to failed build-artifacts which was caused due to a mirror issue. *CQ-Master:* GREEN (#1) Last failure was on 16-07 for ovirt-engine due failure in build-artifacts, which was caused by gerrit issue, which is under investigation by Evgheni. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/YCNCKRK3G4EJX…

1 0

Doubt on Backing Up and Restoring Virtual Machines Using the Backup and Restore API:-
by smidhunraj＠gmail.com 19 Jul '19

19 Jul '19

Doubt on Backing Up and Restoring Virtual Machines Using the Backup and Restore API:- In this link https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html… in point 4 it is said that 4 .Attach the snapshot to the backup virtual machine and activate the disk: POST /api/vms/22222222-2222-2222-2222-222222222222/disks/ HTTP/1.1 Accept: application/xml Content-type: application/xml <disk id="11111111-1111-1111-1111-111111111111"> <snapshot id="11111111-1111-1111-1111-111111111111"/> <active>true</active> </disk> What does this 22222222-2222-2222-2222-222222222222 mean do we need to create a new virtual machine and attach the snapshot to that. Could you kindly explain it further

2 1

OST fails, cannot connect to repo
by Vojtech Juranek 18 Jul '19

18 Jul '19

Hi, OST fails with 09:47:03 https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/ epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:443; Connection refused" see e.g. [1] for full log. Stared to fail this morning. Can anyone take a look and fix it? Thanks in advance. Vojta [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5132/console

5 7

HC suite is failing for 3 weeks on vm_run
by Eyal Edri 15 Jul '19

15 Jul '19

FYI, Failing on vm_run test for 4.3: https://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.3/lastCom… same on master: https://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/last… -- Eyal edri He / Him / His 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)

2 2

[Ovirt] [CQ weekly status] [12-07-2019]
by Dafna Ron 12 Jul '19

12 Jul '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) Last failure was on 02-07 for ovirt-provider-ovm due to failed test: 098_ovirt_provider_ovn.use_ovn_provide. This was a code regression and was fixed by patch https://gerrit.ovirt.org/#/c/97072/ *CQ-4.3*: GREEN (#1) Last failure was on 12-07 for ovirt-provider-ovm due to failed build-artifacts which was caused due to a mirror issue. *CQ-Master:* RED (#1) Last failure was on 12-07 for ovirt-provider-ovm due to failed build-artifacts which was caused due to a mirror issue. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

CI fails to download rpms
by Vojtech Juranek 11 Jul '19

11 Jul '19

Hi, quite a lot of Ci runs fail because Ci fails to download mom-0.5.14-0.0.master.fc29.noarch.rpm, fails with: Downloading Packages: 12:36:34 [MIRROR] mom-0.5.14-0.0.master.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 133628 but expected size is: 133676 12:36:34 [FAILED] mom-0.5.14-0.0.master.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success 12:36:34 Error: Error downloading packages: 12:36:34 Cannot download noarch/mom-0.5.14-0.0.master.fc29.noarch.rpm: All mirrors were tried for full log, see e.g. [1]. Any idea how to fix it? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/7809/console

2 1

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 10-07-2019 ] [ 004_basic_sanity.vdsm_recovery ]
by Dafna Ron 11 Jul '19

11 Jul '19

Hi, We have a failure on test 004_basic_sanity.vdsm_recovery on basic suite. the error seems to be an error in KSM (invalid arg) can you please have a look? Link and headline of suspected patches: cq identified this as the cause of failure: https://gerrit.ovirt.org/#/c/101603/ - localFsSD: Enable 4k block_size and alignments However, I can see some py3 patches merged at the same time: py3: storage: Fix bytes x string in lvm locking type validation - https://gerrit.ovirt.org/#/c/101124/ Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14963/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14963/artifac… (Relevant) error snippet from the log: <error> s/da0eeccb-5dd8-47e5-9009-8a848fe17ea5.ovirt-guest-agent.0',) {} MainProcess|vm/da0eeccb::DEBUG::2019-07-10 07:53:41,003::supervdsm_server::106::SuperVdsm.ServerCallback::(wrapper) return prepareVmChannel with None MainProcess|jsonrpc/1::DEBUG::2019-07-10 07:54:05,580::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({u'pages_to_scan': 64, u'run': 1, u'sleep _millisecs': 89.25152465623417},) {} MainProcess|jsonrpc/1::ERROR::2019-07-10 07:54:05,581::supervdsm_server::103::SuperVdsm.ServerCallback::(wrapper) Error in ksmTune Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 101, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_api/ksm.py", line 45, in ksmTune f.write(str(v)) IOError: [Errno 22] Invalid argument MainProcess|jsonrpc/5::DEBUG::2019-07-10 07:56:33,211::supervdsm_server::99::SuperVdsm.ServerCallback::(wrapper) call rmAppropriateMultipathRules with ('da0eeccb-5dd8-47e5-9009-8a848fe17ea5',) {} </error>

2 3

Successful 'vdsm-client Host getStats' call on py3
by Marcin Sobczyk 10 Jul '19

10 Jul '19

Hi, I'm currently working on making yajsonrpc/stomp implementation py3-compatible so we can have basic communication with vdsm running on py3. Today for the first time I was able to run vdsm [1] with py3 on fc29 and do a successful 'vdsm-client Host getStats' call. Since these patches are needed for other teams to continue with their work on py3, I'd kindly request those of you who are interested to review them: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:p… [1] with minor tweak to 'storage.hsm' module

5 11

Access to images in block domain from more VMs
by Tomáš Golembiovský 10 Jul '19

10 Jul '19

Hi, we have a large gap in handling ISO files in data domains and especially on block domains. None of the flows that work with ISOs works (well, one sort of does): 1) Change CD for running VM [1] 2) Attaching boot disk in Run Once -- this works but I wonder if it's by accident, because engine issues spurious teardown on images [2] 3) Guest tools during VM import [3] 4) Automatic attach of guest tools to Windows VMs Before virt can fix all those we need input from storage on how we should handle the images on block domains. The specialty of ISO image is that it makes sense to have it attached to multiple VMs. And that also means something should control whether image needs attaching or whether the image is already attached to the host. Similarly the image should be (attempted to) detached only when there is no longer any VM on the host that uses it. Hence my question to storage -- is there already some framework from storage for handling this? Does it make more sense to do this on engine side or should each host handle it on it's own? To me it seems preferable to handle this on engine side as that is where the requests for attach/detach normally come from (disks in VM import are an exception). It could possibly mean less race conditions (but I may be totally wrong here). Also having it on VDSM side would probably mean changes to the API for 1) and 2). Any input appreciated. Tomas [1] https://bugzilla.redhat.com/show_bug.cgi?id=1589763 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1721455 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1721455 -- Tomáš Golembiovský <tgolembi(a)redhat.com>

3 5

ovirt-engine has been tagged (ovirt-engine-4.3.5.4)
by Tal Nisan 09 Jul '19

09 Jul '19

1 0

vdsm has been tagged (v4.30.24)
by Milan Zamazal 09 Jul '19

09 Jul '19

1 0

OST fail to install hosts: requires: device-mapper = 7:1.02.149-10.el7_6.8 installed: device-mapper-1.02.149-10.el7_6.7.x86_64
by Nir Soffer 08 Jul '19

08 Jul '19

I had 3 failures with OST master: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… First 2 builds are mostly logging fixes in vdsm and removing dead code, unrelated to the failures. Last build is from master, same patch passed OST today here: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… Looks like some required packages are missing. + yum -y install ovirt-host Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.8.x86_64 (alocalsync) Requires: device-mapper = 7:1.02.149-10.el7_6.8 Installed: 7:device-mapper-1.02.149-10.el7_6.7.x86_64 (installed) device-mapper = 7:1.02.149-10.el7_6.7 Error: Package: systemd-python-219-62.el7_6.7.x86_64 (alocalsync) Requires: systemd-libs = 219-62.el7_6.7 Installed: systemd-libs-219-62.el7_6.6.x86_64 (installed) systemd-libs = 219-62.el7_6.6 Error: Package: systemd-python-219-62.el7_6.7.x86_64 (alocalsync) Requires: systemd = 219-62.el7_6.7 Installed: systemd-219-62.el7_6.6.x86_64 (installed) systemd = 219-62.el7_6.6 Error: Package: libgudev1-219-62.el7_6.7.x86_64 (alocalsync) Requires: systemd-libs = 219-62.el7_6.7 Installed: systemd-libs-219-62.el7_6.6.x86_64 (installed) systemd-libs = 219-62.el7_6.6

3 8

[Ovirt] [CQ weekly status] [05-07-2019]
by Dafna Ron 05 Jul '19

05 Jul '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) Last failure was on 02-07 for ovirt-provider-ovm due to failed test: 098_ovirt_provider_ovn.use_ovn_provide. This was a code regression and was fixed by patch https://gerrit.ovirt.org/#/c/97072/ *CQ-4.3*: RED (#1) We are failing because our ost image is centos 7.6 and we now have 7.7 packages. Galit will need to create a new image to fix the failing tests. *CQ-Master:* RED (#1) We are failing because our ost image is centos 7.6 and we now have 7.7 packages. Galit will need to create a new image to fix the failing tests. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

Proposing Andrej Krejcir as a maintainer of engine core
by Arik Hadas 02 Jul '19

02 Jul '19

Dear engine-core maintainers, I'd like to propose Andrej Krejcir as a maintainer of oVirt engine backend. Since Jul 2015, Andrej has been contributing to ovirt-engine, mostly in SLA areas (scheduling, quota, etc) and recently being more and more involved also in the VIRT areas. This results in ~200 patches to engine master alone. Personally, I reviewed some of Andrej's contributions and noticed reviews made by Andrej to others. I sincerely believe Andrej would be a good addition to the maintainers' group. Thanks in advance for your response!

7 6

ovirt-engine has been tagged (ovirt-engine-4.3.5.3)
by Tal Nisan 02 Jul '19

02 Jul '19

1 0

Storage test case needs to be fixed: 002_bootstrap.resize_and_refresh_storage_domain
by Dafna Ron 02 Jul '19

02 Jul '19

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/testRep… Can you please assign someone from the storage team to fix this test? Thanks, Dafna

4 14

[ANN] Incubating terraform-provider-ovirt
by Roy Golan 02 Jul '19

02 Jul '19

Hi all, Happy to announce the incubation of a terraform provider[1] for oVirt which is the the result of a community effort started by ESM-MSC institute [2] and then picked up by @imjoey [3] which is now the main maintainer of the project. Terraform with an ovirt provider makes it easy to declaratively create virtualized environments. One usage we will make of it is to create an installer for OKD 4 [4] which will lay an OKD cluster on top of oVirt resources. [1] https://github.com/oVirt/terraform-provider-ovirt [2] https://github.com/EMSL-MSC/terraform-provider-ovirt [3] https://github.com/imjoey/terraform-provider-ovirt [4] https://github.com/openshift/installer Roy

2 1

vdsm has been tagged (v4.30.23)
by Milan Zamazal 01 Jul '19

01 Jul '19

1 0

mom install error on fc29
by Miguel Duarte de Mora Barroso 01 Jul '19

01 Jul '19

Hi, I'm seeing the following error when I try to install ovirt-provider-ovn-driver (which requires vdsm): [MIRROR] mom-0.5.12-0.0.master.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 340 but expected size is: 133356 17:13:50 [FAILED] mom-0.5.12-0.0.master.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success 17:13:50 Error: Error downloading packages: 17:13:50 Cannot download noarch/mom-0.5.12-0.0.master.fc29.noarch.rpm: All mirrors were tried Any clue ?.. it can be seen in [0]. Thanks in advance, Miguel [0] - https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-check-patch/2309/…

3 2