- Users - oVirt List Archives

How can I set up a newly created virtual machine to use the qcow2 format disk by default?
by mask.zan＠gmail.com 01 Feb '19

01 Feb '19

How can I set up a newly created virtual machine to use the qcow2 format disk by default? My storage configuration is glusterfs non-ovirt managed

2 1

Profile selection in VM portal for users
by Jorick Astrego 01 Feb '19

01 Feb '19

Hi, Wish I was @FOSDEM :'( Next year... When accessing the selfservice VM portal for users we wish to disable/hide our admin management realm. Is there currently a way to do this? We are maybe a bit paranoid but informatie leakage can bite you in the ass. We want to hookup Keycloak for the user portal and use the current ipa authentication for the admins only.... Met vriendelijke groet, With kind regards, Jorick Astrego THE IDIOT COMPANY Staalsteden 4-3A 7547 TA Enschede The Netherlands +31 (0)53 20 30 275 info(a)theidiotcompany.eu WWW.THEIDIOTCOMPANY.EU

3 2

Storage Domain Ovirt 4.3 RC EPYC
by Darin Schmidt 01 Feb '19

01 Feb '19

Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'Vg' of null Please have your administrator check the UI logs Im trying to setup Ovirt 4.3 RC because its the only one that supports AMD EPYC. The issue Im having is that I creates a raid 5 array of 5 120GB SSDs using mdadm and mounted it at /VM. I put the Host into maintenance, select Configure Local Storage, and it fails telling me: New Local Storage Domain: Storage format is unsupported I formatted the array to ext4. This is a self hosted system. Anyone have any ideas? [root@ovirt VM]# uname -r 3.10.0-957.1.3.el7.x86_64 [root@ovirt VM]# cat /etc/centos-release CentOS Linux release 7.6.1810 (Core) [root@ovirt VM]# rpm -qa|grep ovirt ovirt-engine-backend-4.3.0.2-1.el7.noarch ovirt-imageio-common-1.4.6-1.el7.x86_64 ovirt-engine-setup-plugin-websocket-proxy-4.3.0.4-1.el7.noarch ovirt-ansible-vm-infra-1.1.12-1.el7.noarch ovirt-ansible-infra-1.1.11-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.0.4-1.el7.noarch libgovirt-0.3.4-1.el7.x86_64 ovirt-hosted-engine-setup-2.3.3-1.el7.noarch ovirt-iso-uploader-4.3.0-1.el7.noarch ovirt-engine-4.3.0.2-1.el7.noarch python2-ovirt-host-deploy-1.8.0-1.el7.noarch ovirt-ansible-repositories-1.1.4-1.el7.noarch python-ovirt-engine-sdk4-4.3.0-2.el7.x86_64 ovirt-engine-webadmin-portal-4.3.0.2-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch ovirt-vmconsole-proxy-1.0.6-2.el7.noarch ovirt-ansible-image-template-1.1.9-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-engine-dwh-4.3.0-1.el7.noarch ovirt-ansible-roles-1.1.6-1.el7.noarch ovirt-host-deploy-common-1.8.0-1.el7.noarch ovirt-engine-api-explorer-0.0.3-1.el7.noarch ovirt-engine-setup-base-4.3.0.4-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.0.4-1.el7.noarch cockpit-ovirt-dashboard-0.12.1-1.el7.noarch ovirt-engine-tools-backup-4.3.0.2-1.el7.noarch ovirt-engine-restapi-4.3.0.2-1.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.8-1.el7.noarch ovirt-engine-websocket-proxy-4.3.0.4-1.el7.noarch ovirt-hosted-engine-ha-2.3.1-1.el7.noarch ovirt-ansible-cluster-upgrade-1.1.11-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-ui-extensions-1.0.2-1.el7.noarch ovirt-engine-setup-4.3.0.4-1.el7.noarch ovirt-imageio-daemon-1.4.6-1.el7.noarch ovirt-host-4.3.0-2.el7.x86_64 ovirt-vmconsole-1.0.6-2.el7.noarch ovirt-imageio-proxy-1.4.6-1.el7.noarch ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch ovirt-web-ui-1.5.0-1.el7.noarch ovirt-provider-ovn-1.2.19-1.el7.noarch ovirt-engine-dbscripts-4.3.0.2-1.el7.noarch ovirt-ansible-engine-setup-1.1.7-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.0.4-1.el7.noarch ovirt-provider-ovn-driver-1.2.19-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.8-1.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-host-deploy-java-1.8.0-1.el7.noarch ovirt-engine-tools-4.3.0.2-1.el7.noarch cockpit-machines-ovirt-176-4.el7.centos.noarch ovirt-engine-metrics-1.2.0.3-1.el7.noarch ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch ovirt-vmconsole-host-1.0.6-2.el7.noarch ovirt-ansible-manageiq-1.1.13-1.el7.noarch ovirt-engine-wildfly-14.0.1-3.el7.x86_64 ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.0.4-1.el7.noarch ovirt-host-dependencies-4.3.0-2.el7.x86_64 ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch ovirt-engine-dwh-setup-4.3.0-1.el7.noarch ovirt-ansible-v2v-conversion-host-1.9.1-1.el7.noarch python2-ovirt-engine-lib-4.3.0.4-1.el7.noarch ovirt-release43-pre-4.3.0-0.7.rc4.el7.noarch

3 5

Sanlock volume corrupted on deployment
by Strahil 31 Jan '19

31 Jan '19

4 9

Changing DNS servers
by Chris Adams 31 Jan '19

31 Jan '19

I am trying to change the DNS servers on the hosts on a 4.1 cluster. It appears that oVirt has "learned" them somewhere. They are in /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt (and of course /etc/resolv.conf), but that file gets rewritten on a reboot (so if I change it they just change back). I can't find anything in the web UI to set/change DNS, but obviously they're stored somewhere. I see /var/lib/vdsm/persistence/netconf.<number>/nets/ovirtmgmt has the config; is it safe to directly edit that file? -- Chris Adams <cma(a)cmadams.net>

2 2

[ANN] oVirt 4.3.0 Fifth Release Candidate is now available for testing
by Sandro Bonazzola 31 Jan '19

31 Jan '19

The oVirt Project is pleased to announce the availability of the Fifth Release Candidate of oVirt 4.3.0, as of January 31th, 2019 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first release candidate of the 4.3.0 version. This release brings more than 130 enhancements and more than 450 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS 7 - oVirt Appliance for Fedora 28 (tech preview) is being delayed due to build issues with the build system. Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

host NonResponsive after trying to update network MTUs
by Edward Berger 31 Jan '19

31 Jan '19

I have a problem host which also is the one I deployed a hyperconverged oVirt node-ng cluster from with the cockpit's hyperconverged installation wizard. When I realized after deploying that I hadn't set the MTUs correctly for the engine-mgmt, associated vlan and eno.2 device and also for my infiniband interface ib0, I went in and tried to set them to new values 9000 and 65520 it got into some kind of hung state. The engine task window shows a task in "executing" and a never ending spinning widget "Handing non responsive Host track00..." I can tried updating the hosts /etc/sysconfig/network-scripts by hand. I've tried every combination of the engines set host in maintenance mode , "sync networks" "refresh host capabilities" activating and rebooting, but I'm still stuck with an unresponsive host. I had another host that also failed but it allowed me to put it into maintenance mode and then remove it from the cluster and "add new" it back and it was happy. This one won't let me remove it because its serving the gluster volume mount point, even though I did give the mount options for the 2nd and 3rd backup volume servers. I'd appreciate any help restoring it to proper working order. I'm attaching the gzip'd engine log.

2 5

Failed to configure management network on host Local due to setup networks failure.
by rafonseca＠gmail.com 31 Jan '19

31 Jan '19

Friends, I have install oVirt but appears failed. And interfaces stay not available (LLPD) and not sync. I try install on CentOS and Scientific Linux same problems

2 1

ovirt-sdk_external network add
by ada per 31 Jan '19

31 Jan '19

Hello everyone, I have the following script, i ve been looking in ovirt-sdk but i cannot seem to find the proper way of adding an external provider network under ovirt-ovn I manage to add logical networks and vlans but no luck in external provider. Any advice is appreciated network = networks_service.add( network=types.Network( name='ext_net', description='Testing network', data_center=types.DataCenter( name='Default' ), usages=[types.NetworkUsage.VM], external_provider='ovirt-provider-ovn', -->i know this part is wrong what is it supposed to be called? ),

2 10

Changing CPU type in oVirt Cluster 4.2
by Juhani Rautiainen 31 Jan '19

31 Jan '19

Hi! I made two node oVirt cluster with self hosted engine. It's running top of oVirt Node 4.2. Hardware is built on AMD Epyc processors. I just noticed that "Clusters"-view warns that I have AMD Opteron G3 as CPU type and it will not supported in the future. Didn't check this during installation so it probably came automatically. But question is how can I change this? I get warning 'Error while executing action: Cannot change Cluster CPU to higher CPU type when there are active Hosts with lower CPU type.'. I saw old thread from 2016 where it was suggested that you change value straight to db. Put that seems bit dangerous. Is there any other way to solve this problem? Thanks, Juhani -- Juhani Rautiainen jrauti(a)iki.fi

1 0

Deploying single instance - error
by Leo David 31 Jan '19

31 Jan '19

Hello Everyone, Using version 4.2.8, ( ovirt-node-ng-installer-4.2.0-2019012606.el7.iso ) for deploying one node instance by following from within CockpitUI seems not to be possible. Here's the generated inventory ( i've specified "jbod" in the wizard ): #gdeploy configuration generated by cockpit-gluster plugin [hosts] 192.168.80.191 [script1:192.168.80.191] action=execute ignore_script_errors=no file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 192.168.80.191 [disktype] jbod [service1] action=enable service=chronyd [service2] action=restart service=chronyd [shell2] action=execute command=vdsm-tool configure --force [script3] action=execute file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh ignore_script_errors=no [pv1:192.168.80.191] action=create devices=sdb ignore_pv_errors=no [vg1:192.168.80.191] action=create vgname=gluster_vg_sdb pvname=sdb ignore_vg_errors=no [lv1:192.168.80.191] action=create lvname=gluster_lv_engine ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/engine size=230GB lvtype=thick [selinux] yes [service3] action=restart service=glusterd slice_setup=yes [firewalld] action=add ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp,54322/tcp services=glusterfs [script2] action=execute file=/usr/share/gdeploy/scripts/disable-gluster-hooks.sh [shell3] action=execute command=usermod -a -G gluster qemu [volume1] action=create volname=engine transport=tcp key=storage.owner-uid,storage.owner-gid,features.shard,performance.low-prio-threads,performance.strict-o-direct,network.remote-dio,network.ping-timeout,user.cifs,nfs.disable,performance.quick-read,performance.read-ahead,performance.io-cache,cluster.eager-lock value=36,36,on,32,on,off,30,off,on,off,off,off,enable brick_dirs=192.168.80.191:/gluster_bricks/engine/engine ignore_volume_errors=no It does not get to finish, throwing the following error: PLAY [gluster_servers] ********************************************************* TASK [Create volume group on the disks] **************************************** changed: [192.168.80.191] => (item={u'brick': u'/dev/sdb', u'vg': u'gluster_vg_sdb'}) PLAY RECAP ********************************************************************* 192.168.80.191 : ok=1 changed=1 unreachable=0 failed=0 *Error: Section diskcount not found in the configuration file* Any thoughts ? -- Best regards, Leo David

5 10

Re: Error in SeaBIOS
by Eyal Edri 31 Jan '19

31 Jan '19

On Thu, Jan 31, 2019, 05:45 LIONS TECNOLOGIA <lionstecnologiati(a)gmail.com wrote: > Good night! > > I would like to have a help, I am starting this journey in virtualization > and I am having difficulty, I installed the ovirt but when I install a > virtual machine to test, it happens that it is black screen as described in > the attachment. > Anyone who has a little more experience could help? > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-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/infra@ovirt.org/message/PCLWGIWZPBXOX… >

1 0

VDO volume - storage domain size
by Leo David 31 Jan '19

31 Jan '19

Hello Everyone, I'm I trying to benefit of vdo capabilities, but it seems that I don;t have too much luck with this. I have both created a vdo based gluster volume usign both following methods: - at hyperconverged wizard cluster setup by enabling compression per device - after installation, by creating a new gluster volume and enabling compression In both cases, I end up with a real device size gluster volume/storage domain, although the vdo's appear in node's cockpit UI as being 10 times then physical device. ie: 3 nodes, each having 1 x 900GB ssd device, turns into 9t device vdo device per host, but the storage domain (gluster replica 3 ) ends up as being 900GB . Am I missing something , or maybe doing something wrong? Thank you very much ! Leo Best regards, Leo David

2 3

Roles and Permissions and Inheritance
by Brian Wilson 30 Jan '19

30 Jan '19

Is there a way to prevent Roles Assigned to Groups on Objects to only apply to where it is set? Basically looking for a way to do what we had done in VMWare which involved using the do not propagate permission setting. be able Seems to me that right now there is no way to set this so if i give access to something at the top level of a DC those accesses wlll overide if i then explcitly set another role and permission on an object underneath Lets take as a concrete example the ovirtmgmt network. I do not want users in the engine to be able to place VMs on this (but i want the Superusers to be able to still) How can i accomplish this with the way roles and permissions work with Ovirt? thanks! Brian

3 4

Ovirt configuration
by matteofedeli97＠gmail.com 30 Jan '19

30 Jan '19

Hi at all, I'm installing and configuring a ovirt system in hyperconverged mode and I have some doubt about storage. server 1: 1TB, 1TB server 2: 1TB, 1TB server 3: 1TB, 1TB With this hdd configuration I want on the first drive install ovirt node, vmstore and engine volume, on the second another volume for data. The first in Replica 3 and the second distribuited... It's possible? During installation of ovirt node in the automatic partitioning should I select both hard disk? In the cockpit wizard in this step, https://www.ovirt.org/images/uarwo42-gdeploy-3.png?1519899774, to recover the device name i use pvdisplay -m?

3 5

vSphere Admin is trying to setup an oVirt-Cluster...
by ralph＠gottschalkson.eu 30 Jan '19

30 Jan '19

and is failing .. of course. I get access to 3 HP DL380 G7 with a lot of RAM and a lot of HDDs an 10 GBE NICs. Which VLANs I have to create? The HDDs have not to be in a RAID, they should be single instances for GlusterFS, so that GlusterFS Handles the "Bricks (=Single HHDs?)"? Or use a SAN shared Device, which is also there for simplyfienig the (first) setup What to do with the downloaded oVirt-ISO Image? In vSphere I install ESXi on the nodes, Connect the NICs to the right VLANs. Install VCSA as VM, adding the nodes and so on.. I there an good Instruction out there which tanslates VMWare terms and concepts into oVirts terms so that I can follow the step-by-step instuction? Or ist the setup done by an (magic) Ansible script?

2 1

4.3.0 rc2 cannot mount glusterfs volumes on ovirt node ng
by Jorick Astrego 30 Jan '19

30 Jan '19

Hi, We're having problems mounting the preexisting 3.12 glusterfs storage domains in ovirt node ng 4.3.0 rc2. Getting There are no iptables blocks on the storage network, the ip's are pingable bothe ways. I can telnet to the glusterfs ports and I see no messages in the logs of the glusterfs servers. When I try the mount command manually it hangs for ever: /usr/bin/mount -t glusterfs -o backup-volfile-servers=*.*.*.*:*.*.*.* *.*.*.*:/sdd8 /mnt/temp I haven't submitted a bug yet.... from supervdsm.log MainProcess|jsonrpc/2::DEBUG::2019-01-25 13:42:45,282::supervdsm_server::100::SuperVdsm.ServerCallback::(wrapper) call volumeInfo with (u'sdd8', u'*.*.*.*') {} MainProcess|jsonrpc/2::DEBUG::2019-01-25 13:42:45,282::commands::198::root::(execCmd) /usr/bin/taskset --cpu-list 0-63 /usr/sbin/gluster --mode=script volume info --remote-host=*.*.*.* sdd8 --xml (cwd None) MainProcess|jsonrpc/2::DEBUG::2019-01-25 13:44:45,399::commands::219::root::(execCmd) FAILED: <err> = ''; <rc> = 1 MainProcess|jsonrpc/2::DEBUG::2019-01-25 13:44:45,399::logutils::319::root::(_report_stats) ThreadedHandler is ok in the last 120 seconds (max pending: 2) MainProcess|jsonrpc/2::ERROR::2019-01-25 13:44:45,399::supervdsm_server::104::SuperVdsm.ServerCallback::(wrapper) Error in volumeInfo Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 102, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/gluster/cli.py", line 529, in volumeInfo xmltree = _execGlusterXml(command) File "/usr/lib/python2.7/site-packages/vdsm/gluster/cli.py", line 131, in _execGlusterXml return _getTree(rc, out, err) File "/usr/lib/python2.7/site-packages/vdsm/gluster/cli.py", line 112, in _getTree raise ge.GlusterCmdExecFailedException(rc, out, err) GlusterCmdExecFailedException: Command execution failed error: E r r o r : R e q u e s t t i m e d o u t return code: 1 MainProcess|jsonrpc/2::DEBUG::2019-01-25 13:44:45,400::supervdsm_server::100::SuperVdsm.ServerCallback::(wrapper) call mount with (<vdsm.supervdsm_server._SuperVdsm object at 0x7f6eb8d0a2d0>, u'*.*.*.*:/sdd8', u'/rhev/data-center/mnt/glusterSD/*.*.*.*:_sdd8') {'vfstype': u'glusterfs', 'mntOpts': u'backup-volfile-servers=*.*.*.*:*.*.*.*', 'cgroup': 'vdsm-glusterfs'} MainProcess|jsonrpc/2::DEBUG::2019-01-25 13:44:45,400::commands::198::root::(execCmd) /usr/bin/taskset --cpu-list 0-63 /usr/bin/systemd-run --scope --slice=vdsm-glusterfs /usr/bin/mount -t glusterfs -o backup-volfile-servers=*.*.*.*:*.*.*.* *.*.*.*:/sdd8 /rhev/data-center/mnt/glusterSD/*.*.*.*:_sdd8 (cwd None) MainProcess|jsonrpc/0::DEBUG::2019-01-25 13:45:02,884::commands::219::root::(execCmd) FAILED: <err> = 'Running scope as unit run-38676.scope.\nMount failed. Please check the log file for more details.\n'; <rc> = 1 MainProcess|jsonrpc/0::ERROR::2019-01-25 13:45:02,884::supervdsm_server::104::SuperVdsm.ServerCallback::(wrapper) Error in mount Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 102, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 144, in mount cgroup=cgroup) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 277, in _mount _runcmd(cmd) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 305, in _runcmd raise MountError(rc, b";".join((out, err))) MountError: (1, ';Running scope as unit run-38676.scope.\nMount failed. Please check the log file for more details.\n') MainProcess|jsonrpc/0::DEBUG::2019-01-25 13:45:02,894::supervdsm_server::100::SuperVdsm.ServerCallback::(wrapper) call volumeInfo with (u'ssd9', u'*.*.*.*') {} MainProcess|jsonrpc/0::DEBUG::2019-01-25 13:45:02,894::commands::198::root::(execCmd) /usr/bin/taskset --cpu-list 0-63 /usr/sbin/gluster --mode=script volume info --remote-host=*.*.*.* ssd9 --xml (cwd None) from vdsm.log 2019-01-25 13:46:03,519+0100 WARN (vdsm.Scheduler) [Executor] Worker blocked: <Worker name=jsonrpc/2 running <Task <JsonRpcTask {'params': {u'connectionParams': [{u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'6b6b7899-c82b-4417-b453-0b3b0ac11deb', u'connection': u'*.*.*.*:ssd4', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'b036005a-d44d-4689-a8c3-13e1bbf55af7', u'connection': u'*.*.*.*:ssd5', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'40d191b0-b7f8-48f9-bf6f-327275f51fef', u'connection': u'*.*.*.*:ssd6', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'26fbd2d6-6f25-4520-ab7f-15e9001f07b9', u'connection': u'*.*.*.*:/hdd2', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'f11fed97-513a-4a10-b85c-2afe68f42608', u'connection': u'*.*.*.*:/ssd3', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'f20b8691-528e-4e38-89ad-1e27684dee8b', u'connection': u'*.*.*.*:/sdd8', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'188e71dc-3d81-43d3-b930-238a4c6711e6', u'connection': u'*.*.*.*:/ssd9', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}], u'storagepoolID': u'00000001-0001-0001-0001-000000000043', u'domainType': 7}, 'jsonrpc': '2.0', 'method': u'StoragePool.connectStorageServer', 'id': u'581e2ad3-0682-4d44-95b4-bdc088b45f66'} at 0x7f9be815c850> timeout=60, duration=1260.00 at 0x7f9be815ca10> task#=98 at 0x7f9be83bb750>, traceback: File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap self.__bootstrap_inner() File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File: "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 195, in run ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run self._execute_task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ self._callable() File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 262, in __call__ self._handler(self._ctx, self._req) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 305, in _serveRequest response = self._handle_request(req, ctx) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod result = fn(*methodArgs) File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1103, in connectStorageServer connectionParams) File: "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line 72, in wrapper result = ctask.prepare(func, *args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in wrapper return m(self, *a, **kw) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1179, in prepare result = self._run(func, *args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File: "<string>", line 2, in connectStorageServer File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2410, in connectStorageServer conObj.connect() from messages: Jan 25 13:49:07 node9 vdsm[31968]: WARN Worker blocked: <Worker name=jsonrpc/3 running <Task <JsonRpcTask {'params': {u'connectionParams': [{u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'6b6b7899-c82b-4417-b453-0b3b0ac11deb', u'connection': u'192.168.99.15:ssd4', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'b036005a-d44d-4689-a8c3-13e1bbf55af7', u'connection': u'*.*.*.*:ssd5', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'40d191b0-b7f8-48f9-bf6f-327275f51fef', u'connection': u'*.*.*.*:ssd6', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'26fbd2d6-6f25-4520-ab7f-15e9001f07b9', u'connection': u'*.*.*.*:/hdd2', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'f11fed97-513a-4a10-b85c-2afe68f42608', u'connection': u'*.*.*.*:/ssd3', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'f20b8691-528e-4e38-89ad-1e27684dee8b', u'connection': u'*.*.*.*:/sdd8', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}, {u'mnt_options': u'backup-volfile-servers=*.*.*.*:*.*.*.*', u'id': u'188e71dc-3d81-43d3-b930-238a4c6711e6', u'connection': u'*.*.*.*:/ssd9', u'iqn': u'', u'user': u'', u'tpgt': u'1', u'ipv6_enabled': u'false', u'vfs_type': u'glusterfs', u'password': '********', u'port': u''}], u'storagepoolID': u'00000001-0001-0001-0001-000000000043', u'domainType': 7}, 'jsonrpc': '2.0', 'method': u'StoragePool.connectStorageServer', 'id': u'918f4d06-ca89-4ec0-a396-3407f1bdb8f9'} at 0x7f9be82ff250> timeout=60, duration=840.00 at 0x7f9be82ffa50> task#=93 at 0x7f9be83bba10>, traceback:#012File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap#012 self.__bootstrap_inner()#012File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner#012 self.run()#012File: "/usr/lib64/python2.7/threading.py", line 765, in run#012 self.__target(*self.__args, **self.__kwargs)#012File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 195, in run#012 ret = func(*args, **kwargs)#012File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run#012 self._execute_task()#012File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task#012 task()#012File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__#012 self._callable()#012File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 262, in __call__#012 self._handler(self._ctx, self._req)#012File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 305, in _serveRequest#012 response = self._handle_request(req, ctx)#012File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request#012 res = method(**params)#012File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod#012 result = fn(*methodArgs)#012File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1103, in connectStorageServer#012 connectionParams)#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line 72, in wrapper#012 result = ctask.prepare(func, *args, **kwargs)#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in wrapper#012 return m(self, *a, **kw)#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1179, in prepare#012 result = self._run(func, *args, **kwargs)#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run#012 return fn(*args, **kargs)#012File: "<string>", line 2, in connectStorageServer#012File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method#012 ret = func(*args, **kwargs)#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2410, in connectStorageServer#012 conObj.connect()#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 172, in connect#012 self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP)#012File: "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 207, in mount#012 cgroup=cgroup)#012File: "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__#012 return callMethod()#012File: "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda>#012 **kwargs)#012File: "<string>", line 2, in mount#012File: "/usr/lib64/python2.7/multiprocessing/managers.py", line 759, in _callmethod#012 kind, result = conn.recv() Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

5 8

Administration Portal High Availability
by ernestclyde＠sav25.com 30 Jan '19

30 Jan '19

Hello, Currently i am finding some Documentation or "how to" setup High Availability of oVirt Engine's Administration Portal.

3 3

Host Only Network
by Brian Wilson 29 Jan '19

29 Jan '19

What is the proper way to provide networks without an egress of the host? In VMware i would take a portgroup and just not associate it with a vnic. In ovirt that doesnt seem possible as the network doesnt seem to function unless i move to a physical nic under the "Setup Host Networks" options. The Goal here is to provide a network for VMs to use on the single host only no traffic would need to leave the host but would need to have VLan IDs and segmentation through them on the host

4 4

Single Node Deployment - Self-Hosted-Engine
by Brian Wilson 29 Jan '19

29 Jan '19

I have a question regarding installing a single node and then running the self-hosted engine on it. I would like to keep this as simple as possible and am running into an issue with where to tell the installer to place the engine. It asks me to choose a shared storage technology(gfs,nfs, iscsi) and i dont want to rely on anything outside of this single box to provide storage. I would like to add another volume (LVM) as a local storage domain to be used for this as well as all other VMs to be run on this all in one box. Is there some secret sauce to getting this installer to choose a local location rather than a shared one?

4 6

[ANN] oVirt 4.3.0 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 29 Jan '19

29 Jan '19

The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 4.3.0, as of January 29th, 2019 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first release candidate of the 4.3.0 version. This release brings more than 130 enhancements and more than 450 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS 7 - oVirt Node NG is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Appliance for Fedora 28 (tech preview) is being delayed due to build issues with the build system. Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Planned infra outage - Saturday February 2
by Evgheni Dereveanchin 29 Jan '19

29 Jan '19

Hi everyone, There's a maintenance window planned for this Saturday, February 2 2019 to upgrade network equipment in the PHX datacenter. The change will be implemented during afternoon hours and several oVirt infra services may be unreachable for short periods of time, specifically: * package repositories * Jenkins CI * glance image repo If you have problems accessing project resources during this period or see CI failures please re-try in a couple of hours. The project website and Gerrit code review are not affected by this outage and will continue to function normally. -- Regards, Evgheni Dereveanchin

1 0

Clearing asynchronous task Unknown
by nicolas＠devels.es 29 Jan '19

29 Jan '19

Hi, We're running oVirt 4.1.9 (I know there's a new version, we can't upgrade until [1] is implemented). The thing is that since some days we're having an event that floods our event list: Clearing asynchronous task Unknown that started at Tue Jan 22 14:33:17 WET 2019 The event shows up every minute. We tried restarting the ovirt-engine, but after some time it starts flooding again. No pending tasks in the task list. How can I check what is happening and how to solve it? Thanks. [1]: https://github.com/oVirt/ovirt-web-ui/issues/490

2 2

[ANN] oVirt 4.2.8 async update is now available
by Sandro Bonazzola 29 Jan '19

29 Jan '19

The oVirt Team has just released a new version of the following packages: - ovirt-engine-metrics-1.1.8.1 The async release addresses the following bugs: Bug 1631808 <https://bugzilla.redhat.com/show_bug.cgi?id=1631808> - Ensure ovirt-engine-metrics in oVirt 4.2 doesn't have compatibility issues if fluentd doesn't exist on host This fix allows to have 4.3 nodes with 4.2 engine to ease upgrade. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

oVirt SHE 4.2.8 and CentOS 7.6
by Vrgotic, Marko 29 Jan '19

29 Jan '19

Hi all, Looking at 4.2.8 and How Support version is EL 7.5. Does that mean that is not recommended to upgrade already running SHE to higher than EL 7.5, or it means not to deploy it on EL version lower than 7.5? Thank you. Marko Vrgotic

2 3

Re: converting oVirt host to be able to hosts to a Self-Hosted Environment
by Simone Tiraboschi 28 Jan '19

28 Jan '19

On Mon, Jan 28, 2019 at 1:31 PM Jarosław Prokopowski <jprokopowski(a)gmail.com> wrote: > Thanks Simone > > I forgot to mention that this is to have second node that is able to host > the self-hosted engine for HA purposes. > There is already one node that hosts the self-hosted engine and I want to > have second one. > Will it work in this case? > No, in this case it's by far easier: you should just set that host into maintenance mode from the engine and remember to switch on the hosted-engine deployment flag when you go to reinstall the host. > > > > On Mon, Jan 28, 2019 at 1:25 PM Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >> >> >> On Mon, Jan 28, 2019 at 12:21 PM Jarosław Prokopowski < >> jprokopowski(a)gmail.com> wrote: >> >>> Hi Guys, >>> >>> Is there a way to convert existing oVirt node (CentOS) to be able to >>> host a Self-Hosted Environment? >>> If so how can I do that? >>> >> >> Hi, the best option is with backup and restore. >> Basically you should take a backup of your current engine with >> engine-backup >> and then deploy hosted-engine with hosted-engine --deploy >> --restore-from-file=mybackup.tar.gz >> >> >>> >>> Thanks >>> Jaroson >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZVY4SD5RTNV6V… >>> >>

1 0

converting oVirt host to be able to hosts to a Self-Hosted Environment
by Jarosław Prokopowski 28 Jan '19

28 Jan '19

Hi Guys, Is there a way to convert existing oVirt node (CentOS) to be able to host a Self-Hosted Environment? If so how can I do that? Thanks Jaroson

2 1

Ovirt snapshot issues
by Alex K 28 Jan '19

28 Jan '19

Hi all, I have ovirt 4.2.7, self-hosted on top gluster, with two servers. I have a specific VM which has encountered some snapshot issues. The engine lists 4 snapshots and when trying to delete one of them I get "General command validation failure". The VM was being backed up periodically by a python script which was creating a snapshot -> clone -> export -> delete clone -> delete snapshot. There were times where the VM was complaining of some illegal snapshots following such backup procedures and I had to delete such illegal snapshots references from the engine DB (following some steps found online), otherwise I would not be able to start the VM if it was shut down. Seems though that this is not a clean process and leaves the underlying image of the VM in an inconsistent state in regards to its snapshots as when checking the backing chain of the image file I get: *b46d8efe-885b-4a68-94ca-e8f437566bee* (active VM)* ->* *b7673dca-6e10-4a0f-9885-1c91b86616af ->* *4f636d91-a66c-4d68-8720-d2736a3765df ->* 6826cb76-6930-4b53-a9f5-fdeb0e8012ac -> 61eea475-1135-42f4-b8d1-da6112946bac -> *604d84c3-8d5f-4bb6-a2b5-0aea79104e43 ->* 1e75898c-9790-4163-ad41-847cfe84db40 -> *cf8707f2-bf1f-4827-8dc2-d7e6ffcc3d43 ->* 3f54c98e-07ca-4810-82d8-cbf3964c7ce5 (raw image) The bold ones are the ones shown at engine GUI. The VM runs normally without issues. I was thinking if I could use qemu-img commit to consolidate and remove the snapshots that are not referenced from engine anymore. Any ideas from your side? Thanx, Alex

2 5

Nvidia Grid K2 and Ovirt GPU Passtrough
by jarheadx＠hotmail.de 28 Jan '19

28 Jan '19

Hello, i have tried every documentation that i found to bring GPU Passtrough with a Nvidia Grid K2 to ovirt, but i failed. I am confident that it has to run with my hardware, but i have no ideas anymore. Maybe the community can help me. Actually my VM (Win7 and Win10) crashes or hangs on startup. I have done theese steps: 1. lspci -nnk ......... 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL [GRID K2] [10de:11bf] (rev a1) Subsystem: NVIDIA Corporation Device [10de:100a] Kernel driver in use: pci-stub Kernel modules: nouveau 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104GL [GRID K2] [10de:11bf] (rev a1) Subsystem: NVIDIA Corporation Device [10de:100a] Kernel driver in use: pci-stub Kernel modules: nouveau ......... 2. /etc/default/grub ......... GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=cl/root rd.lvm.lv=cl/swap rhgb quiet pci-stub.ids=10de:11bf rdblacklist=nouveau amd_iommu=on" ........ 3. Added Line "options vfio-pci ids=10de:11bf" to nano /etc/modprobe.d/vfio.conf dmesg | grep -i vfio -> [ 11.202767] VFIO - User Level meta-driver version: 0.3 [ 11.315368] vfio_pci: add [10de:11bf[ffff:ffff]] class 0x000000/00000000 [ 1032.582778] vfio_ecap_init: 0000:07:00.0 hiding ecap 0x19@0x900 [ 1046.232009] vfio-pci 0000:07:00.0: irq 61 for MSI/MSI-X ------------------------------------------------------------------------- After assigning the GPU to the VM, the OS hangs on startup Any ideas? Best Regards Reza

3 3

Using oVirt for Desktop Virtualization
by jarheadx＠hotmail.de 28 Jan '19

28 Jan '19

Hey guys, i want to use ovirt as my desktop enviroement. Therefore i bought a GRID K2 for GPU Passtrough. But i have still lags on video streaming for example HD Videos. I used Spice, VNC and Remote Desktop but i guess they are not good on video compression over WAN or LAN. Is there any other Remote App which allows me to use ovirt as my Virtual Desktop with smooth and reliable video output? Many Thanks Volrath

2 1

Nvidia Grid K2 and Ovirt VGPU
by jarheadx＠hotmail.de 27 Jan '19

27 Jan '19

Hello, sry for my bad english. I have just bought the NVIDIA Grid K2 and want to passtrough the vGPU to several VMS. But i am not able to manage this. I need the driver for Guest and Host, but can not download it. On the official Site of Nvidia there are only drivers for XenServer and VMWare. This Nvidia-Site tells that there is support for Ovirt (RHEV) and K2 (https://docs.nvidia.com/grid/4.6/grid-vgpu-release-notes-red-hat-el-kvm/ind… ) Can someone please tell me what is going on? Is there any possibility to run Grid K2 in Ovirt with vGpu (or Host Device Passtrough?) Furthermore if I do "vdsm-client Host hostdevListByCaps" on the Host , i do not get any mdev markers like described here: https://www.ovirt.org/documentation/install-guide/appe-Preparing_a_Host_for… Many Thanks Volrath

2 2

Re: ovirt 4.2 HCI rollout
by Dominik Holler 26 Jan '19

26 Jan '19

On Tue, 22 Jan 2019 11:15:12 +0000 Markus Schaufler <markus.schaufler(a)digit-all.at> wrote: > Thanks for your reply, > > getent ahosts ovirt-hci.res01.ads.ooe.local | cut -d' ' -f1 | uniq > 10.1.31.20 > > attached you'll find the logs. > Thanks, to my eyes this looks like a bug. I tried to isolate the relevant lines in the attached playbook. Markus, would you be so kind to check if ovirt-4.2.8 is working for you? > ________________________________ > Von: Dominik Holler <dholler(a)redhat.com> > Gesendet: Montag, 21. Jänner 2019 17:52:35 > An: Markus Schaufler > Cc: users(a)ovirt.org; Simone Tiraboschi > Betreff: Re: [ovirt-users] ovirt 4.2 HCI rollout > > Would you please share the related ovirt-host-deploy-ansible-*.log > stored on the host in /var/log/ovirt-hosted-engine-setup ? > > Would you please also share the output of > getent ahosts YOUR_HOSED_ENGNE_FQDN | cut -d' ' -f1 | uniq > if executed on this host? > > > On Mon, 21 Jan 2019 13:37:53 -0000 > "Markus Schaufler" <markus.schaufler(a)digit-all.at> wrote: > > > Hi, > > > > I'm trying a (nested) ovirt 4.2.7 HCI rollout on 3 centos VM's by > > following > > https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… > > gluster deployment was successful but at HE deployment "stage 5" I > > got following error: > > > > [ INFO ] TASK [Reconfigure OVN central address] > > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes > > an option with an undefined variable. The error was: 'dict object' > > has no attribute 'stdout_lines'\n\nThe error appears to have been > > in > > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': > > line 522, column 5, but may\nbe elsewhere in the file depending on > > the exact syntax problem.\n\nThe offending line appears to be:\n\n > > # > > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > > - name: Reconfigure OVN central address\n ^ here\n"} > > > > > > /var/log/messages: > > Jan 21 14:09:56 HCI01 journal: ovirt-ha-agent > > ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR > > Engine VM stopped on localhost Jan 21 14:10:01 HCI01 systemd: > > Started Session 22 of user root. Jan 21 14:10:02 HCI01 systemd: > > Started Session c306 of user root. Jan 21 14:10:03 HCI01 systemd: > > Started Session c307 of user root. Jan 21 14:10:06 HCI01 > > vdsm[3650]: WARN executor state: count=5 workers=set([<Worker > > name=periodic/4 waiting task#=141 at 0x7fd2d4316910>, <Worker > > name=periodic/1 running <Task discardable <Operation > > action=<vdsm.virt.sampling.VMBulkstatsMonitor object at > > 0x7fd2d4679490> at 0x7fd2d4679710> timeout=7.5, duration=7 at > > 0x7fd2d4679490> 0x7fd33c1e0ed0> disca rded task#=413 at > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>, <Worker > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>name=periodic/3 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>waiting task#=414 at > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>, > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10><Worker > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>name=periodic/5 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>waiting > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>task#=0 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>at > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>, > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650><Worker > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>name > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>=periodic/2 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>waiting > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>task#=412 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>at > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>]) > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>device > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>vnet0 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>left > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>promiscuous > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>mode > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> > > [1548076206.9177] device (vnet0): state change: disconnected -> > > unmanaged (reason 'unmanaged', sys-iface-state: 'remo ved') Jan 21 > > 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9180] > > device (vnet0): released from master device ovirtmgmt Jan 21 > > 14:10:06 HCI01 lldpad: recvfrom(Event interface): No buffer space > > available Jan 21 14:10:06 HCI01 libvirtd: 2019-01-21 > > 13:10:06.925+0000: 2651: error : qemuMonitorIORead:609 : Unable to > > read from monitor: Connection reset by peer Jan 21 14:10:07 HCI01 > > kvm: 0 guests now active Jan 21 14:10:07 HCI01 systemd-machined: > > Machine qemu-3-HostedEngine terminated. Jan 21 14:10:07 HCI01 > > libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : > > qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 > > 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: > > warning : qemuGetProcessInfo:1406 : cannot parse process status > > data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: > > 2704: warning : qemuGetProcessInfo:1406 : cannot parse process > > status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 > > 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot > > parse process status data Jan 21 14:10:07 HCI01 libvirtd: > > 2019-01-21 13:10:07.126+0000: 2704: error : > > virNetDevTapInterfaceStats:764 : internal error: /proc/net/dev: > > Interface not found Jan 21 14:10:07 HCI01 firewalld[24040]: > > WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out > > -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vnet 0' > > failed: iptables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out > > vnet0 -g FP-vnet0' failed: iptables v 1.4.21: goto 'FP-vnet0' is > > not a chain#012#012Try `iptables -h' or 'iptables --help' for more > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev > > --physdev-in vnet0 -g FJ-vnet0' failed: iptables v1. 4.21: goto > > 'FJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' > > failed: iptable s v1.4.21: goto 'HJ-vnet0' is not a > > chain#012#012Try `iptables -h' or 'iptables --help' for more > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FP-vnet0' failed: > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -X FP-vnet0' failed: iptables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FJ-vnet0' failed: > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -X FJ-vnet0' failed: iptables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HJ-vnet0' failed: > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -X HJ-vnet0' failed: iptables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vne t0' > > failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > physdev --physdev-out vnet0 -g FP-vnet0' failed: ip6tables v1.4.21: > > goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: > > ip6tables v 1.4.21: goto 'FJ-vnet0' is not a chain#012#012Try > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > --physdev-in vnet0 -g HJ-vnet0' failed: ip6tab les v1.4.21: goto > > 'HJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -F FP-vnet0' failed: ip6tables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FP-vnet0' failed: > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ip6tables -w2 -w -F FJ-vnet0' failed: ip6tables: No > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -X FJ-vnet0' failed: ip6tables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HJ-vnet0' failed: > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ip6tables -w2 -w -X HJ-vnet0' failed: ip6tables: No > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' > > failed: Illegal target name 'libvirt-J-vnet0'. Jan 21 14:10:07 > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > libvirt-P-vnet0' failed: Illegal target name 'libvirt-P-vnet0'. Jan > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j > > libvirt-J-vnet0' failed: Illegal targe t name 'libvirt-J-vnet0'. > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > libvirt-P-vnet0' failed: Illegal targ et name 'libvirt-P-vnet0'. > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ebtables --concurrent -t nat -L libvirt-J-vnet0' failed: > > Chain 'libvirt-J-vnet0' doesn't exis t. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -L libvirt-P-vnet0' failed: Chain > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -F libvirt-J-vnet0' failed: Chain > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -X libvirt-J-vnet0' failed: Chain > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -F libvirt-P-vnet0' failed: Chain > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -X libvirt-P-vnet0' failed: Chain > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out > > vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not > > a chain#012#012Try `iptables -h' or 'iptables --help' for more > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m > > physdev --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: > > goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or > > 'iptables --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > iptables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev > > --physdev-in vnet0 -g HI-vnet0' failed: iptables v1.4.21: goto > > 'HI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > failed: iptables: Bad rule (does a matching rule exist in that > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FO-vnet0' failed: > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -X FO-vnet0' failed: iptables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FI-vnet0' failed: > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -X FI-vnet0' failed: iptables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HI-vnet0' failed: > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > -w -X HI-vnet0' failed: iptables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' > > failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > physdev --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: > > goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > ip6tables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > --physdev-in vnet0 -g HI-vnet0' failed: ip6tables v1.4.21: goto > > 'HI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > --help' for more information. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > failed: ip6tables: Bad rule (does a matching rule exist in that > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FO-vnet0' failed: > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ip6tables -w2 -w -X FO-vnet0' failed: ip6tables: No > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -F FI-vnet0' failed: ip6tables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FI-vnet0' failed: > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ip6tables -w2 -w -F HI-vnet0' failed: ip6tables: No > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > -w -X HI-vnet0' failed: ip6tables: No chain/target/match by that > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D > > POSTROUTING -o vnet0 -j libvirt-O-vnet0' failed: Illegal target > > name 'libvirt-O-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: > > WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L > > libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet0' failed: > > Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > --concurrent -t nat -X libvirt-O-vnet0' failed: Chain > > 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 vdsm[3650]: > > WARN > > File: /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.ovirt-guest-agent.0 > > already removed Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting > > to remove a non existing network: > > ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 > > HCI01 vdsm[3650]: WARN Attempting to remove a non existing net > > user: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 > > 14:10:07 HCI01 vdsm[3650]: WARN > > File: /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.org.qemu.guest_agent.0 > > already removed > > > > any ideas on that? > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ List > > Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMMX5CY6VHFWW… >

3 2

Re: Nvidia Grid K2 and Ovirt VGPU
by Michal Skrivanek 26 Jan '19

26 Jan '19

> On 11 Jan 2019, at 18:11, R A <jarheadx(a)hotmail.de> wrote: > > Hello Michal, > > many thanks for your response. > > Are you sure that there is no vGPU support? Please check lines below Hi Reza, it’s nvidia’s doc, you would have to talk to them if you have more questions. All I understand from that doc (it’s just little more below on the same page) is that they explicitly say that K1 and K2 do not support vGPU. This might be a licensing limitation or temporary or anything else, I don’t know. Thanks, michal > > <image.png> > > > and here: > > <image.png> > > The NVIDIA Grid K2 is GRID capaable. > > Many thanks! > Reza > > Von: Michal Skrivanek <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> > Gesendet: Freitag, 11. Januar 2019 12:04 > An: jarheadx(a)hotmail.de <mailto:jarheadx@hotmail.de> > Cc: users(a)ovirt.org <mailto:users@ovirt.org> > Betreff: Re: [ovirt-users] Nvidia Grid K2 and Ovirt VGPU > > > On 10 Jan 2019, at 02:14, jarheadx(a)hotmail.de <mailto:jarheadx@hotmail.de> wrote: > > > > Hello, > > > > sry for my bad english. > > > > I have just bought the NVIDIA Grid K2 and want to passtrough the vGPU to several VMS. But i am not able to manage this. > > I need the driver for Guest and Host, but can not download it. On the official Site of Nvidia there are only drivers for XenServer and VMWare. > > > > This Nvidia-Site tells that there is support for Ovirt (RHEV) and K2 ( <applewebdata://881AA05A-2E7C-4482-AEBB-52EA439E3294>https://docs.nvidia.com/grid/4.6/grid-vgpu-release-notes-red-hat-el-kvm/ind… <https://docs.nvidia.com/grid/4.6/grid-vgpu-release-notes-red-hat-el-kvm/ind…> ) > > The page says K1 and K2 do not support vGPU so you could only do Host > Device Passthrough of the whole GPU > > > > > Can someone please tell me what is going on? Is there any possibility to run Grid K2 in Ovirt with vGpu (or Host Device Passtrough?) > > > > Furthermore if I do "vdsm-client Host hostdevListByCaps" on the Host , i do not get any mdev markers like described here:https://www.ovirt.org/documentation/install-guide/appe-Preparing_a_Hos… <https://www.ovirt.org/documentation/install-guide/appe-Preparing_a_Host_for…> > > That’s only for vgpu which it doesn’t support, so you do not see any mdev > > > > > Many Thanks > > Volrath > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > > To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> > > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FBIEV6OCU4VDK… <https://lists.ovirt.org/archives/list/users@ovirt.org/message/FBIEV6OCU4VDK…>

3 2

Cluster upgrade with ansible only upgrades one host then stops
by Jayme 25 Jan '19

25 Jan '19

I have a three node HCI setup, running 4.2.7 and want to upgrade to 4.2.8. When I use ansible to perform the host updates for some reason it fully updates one host then stops without error, it does not continue upgrading the remaining two hosts. If I run it again it will proceed to upgrade the next host. Is there something wrong with the ansible plays I am using or perhaps the command I'm using to run ansible needing to specify all hosts to run against. I don't understand why it's not upgrading all hosts in one single run. Here is the complete ansible output of the last run, in this example it fully updated and rebooted host0 with no errors but did not proceed to upgrade host1 or host2: $ cat ovirt-upgrade # ansible-playbook --ask-vault-pass upgrade.yml Vault password: PLAY [oVirt Cluster Upgrade] ************************************************************************************************************************************************************************************************************************************************************************************************* TASK [oVirt.cluster-upgrade : set_fact] ************************************************************************************************************************************************************************************************************************************************************************************** ok: [localhost] TASK [oVirt.cluster-upgrade : Login to oVirt] ******************************************************************************************************************************************************************************************************************************************************************************** ok: [localhost] TASK [oVirt.cluster-upgrade : Get hosts] ************************************************************************************************************************************************************************************************************************************************************************************* ok: [localhost] TASK [oVirt.cluster-upgrade : Check if there are hosts to be updated] ******************************************************************************************************************************************************************************************************************************************************** skipping: [localhost] TASK [oVirt.cluster-upgrade : include_tasks] ********************************************************************************************************************************************************************************************************************************************************************************* included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/cluster_policy.yml for localhost TASK [oVirt.cluster-upgrade : Get cluster facts] ***************************************************************************************************************************************************************************************************************************************************************************** ok: [localhost] TASK [oVirt.cluster-upgrade : Get name of the original scheduling policy] **************************************************************************************************************************************************************************************************************************************************** ok: [localhost] TASK [oVirt.cluster-upgrade : Remember the cluster scheduling policy] ******************************************************************************************************************************************************************************************************************************************************** ok: [localhost] TASK [oVirt.cluster-upgrade : Remember the cluster scheduling policy properties] ********************************************************************************************************************************************************************************************************************************************* ok: [localhost] TASK [oVirt.cluster-upgrade : Get API facts] ********************************************************************************************************************************************************************************************************************************************************************************* ok: [localhost] TASK [oVirt.cluster-upgrade : Set in cluster upgrade policy] ***************************************************************************************************************************************************************************************************************************************************************** changed: [localhost] TASK [oVirt.cluster-upgrade : Get list of VMs in cluster] ******************************************************************************************************************************************************************************************************************************************************************** ok: [localhost] [ INFO ] Configuring WebSocket Proxy skipping: [localhost] => (item=vm1) skipping: [localhost] => (item=vm2) skipping: [localhost] => (item=vm3) TASK [oVirt.cluster-upgrade : Create list of VM names which was shutted down] ************************************************************************************************************************************************************************************************************************************************ skipping: [localhost] TASK [oVirt.cluster-upgrade : include_tasks] ********************************************************************************************************************************************************************************************************************************************************************************* included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 235034116096, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/771c67eb-56e6-4736-8c67-668502d4ecf5', u'spm': {u'priority': 5, u'status': u'none'}, u'id': u'771c67eb-56e6-4736-8c67-668502d4ecf5', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host0.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:ac5566ae1e1a'}, u'port': 54321, u'hardware_information': {u'serial_number': u'70833W1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0030-3810-8033-B7C04F335731', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:TiiMiaHi++kqhmurXdlQjtwbb3Q1oIBi5ab2alKujyI'}, u'address': u' host0.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host0', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host0/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host0/swap rd.lvm.lv=onn_host0/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 250759610368, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/fb1e62d5-1dc1-4ccc-8b2b-cf48f7077d0d', u'spm': {u'priority': 5, u'status': u'none'}, u'id': u'fb1e62d5-1dc1-4ccc-8b2b-cf48f7077d0d', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host1.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:2f5ea98fcec4'}, u'port': 54321, u'hardware_information': {u'serial_number': u'FYRTGX1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0059-5210-8054-C6C04F475831', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:HGU2WhIlPfxgXHXHOE8IYT4/NGAQeUBRe0QA34qQ+nc'}, u'address': u' host1.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host1', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host1/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host1/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rd.lvm.lv=onn_host1/swap rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 232492367872, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/fd0752d8-2d41-45b0-887a-0ffacbb8a237', u'spm': {u'priority': 5, u'status': u'spm'}, u'id': u'fd0752d8-2d41-45b0-887a-0ffacbb8a237', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host2.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:369c9881d24e'}, u'port': 54321, u'hardware_information': {u'serial_number': u'D9733W1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0039-3710-8033-C4C04F335731', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:cSgSzFFQaziGHDeKH1CIfXd8YbheGTaft3XBgyr4YgQ'}, u'address': u' host2.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host2', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host2/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host2/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rd.lvm.lv=onn_host2/swap rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) TASK [oVirt.cluster-upgrade : Upgrade host] ********************************************************************************************************************************************************************************************************************************************************************************** skipping: [localhost] => (item=vm1) skipping: [localhost] => (item=vm2) skipping: [localhost] => (item=vm3) skipping: [localhost] => (item=vm4) TASK [oVirt.cluster-upgrade : Create list of VM names which was shutted down] ************************************************************************************************************************************************************************************************************************************************ skipping: [localhost] TASK [oVirt.cluster-upgrade : include_tasks] ********************************************************************************************************************************************************************************************************************************************************************************* included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 235034116096, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/771c67eb-56e6-4736-8c67-668502d4ecf5', u'spm': {u'priority': 5, u'status': u'none'}, u'id': u'771c67eb-56e6-4736-8c67-668502d4ecf5', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host0.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:ac5566ae1e1a'}, u'port': 54321, u'hardware_information': {u'serial_number': u'70833W1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0030-3810-8033-B7C04F335731', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:TiiMiaHi++kqhmurXdlQjtwbb3Q1oIBi5ab2alKujyI'}, u'address': u' host0.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host0', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host0/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host0/swap rd.lvm.lv=onn_host0/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 250759610368, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/fb1e62d5-1dc1-4ccc-8b2b-cf48f7077d0d', u'spm': {u'priority': 5, u'status': u'none'}, u'id': u'fb1e62d5-1dc1-4ccc-8b2b-cf48f7077d0d', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host1.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:2f5ea98fcec4'}, u'port': 54321, u'hardware_information': {u'serial_number': u'FYRTGX1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0059-5210-8054-C6C04F475831', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:HGU2WhIlPfxgXHXHOE8IYT4/NGAQeUBRe0QA34qQ+nc'}, u'address': u' host1.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host1', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host1/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host1/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rd.lvm.lv=onn_host1/swap rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 232492367872, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/fd0752d8-2d41-45b0-887a-0ffacbb8a237', u'spm': {u'priority': 5, u'status': u'spm'}, u'id': u'fd0752d8-2d41-45b0-887a-0ffacbb8a237', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host2.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:369c9881d24e'}, u'port': 54321, u'hardware_information': {u'serial_number': u'D9733W1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0039-3710-8033-C4C04F335731', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:cSgSzFFQaziGHDeKH1CIfXd8YbheGTaft3XBgyr4YgQ'}, u'address': u' host2.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host2', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host2/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host2/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rd.lvm.lv=onn_host2/swap rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) TASK [oVirt.cluster-upgrade : Upgrade host] ********************************************************************************************************************************************************************************************************************************************************************************** skipping: [localhost] => (item=vm1) skipping: [localhost] => (item=vm2) skipping: [localhost] => (item=vm3) TASK [oVirt.cluster-upgrade : Create list of VM names which was shutted down] ************************************************************************************************************************************************************************************************************************************************ skipping: [localhost] TASK [oVirt.cluster-upgrade : include_tasks] ********************************************************************************************************************************************************************************************************************************************************************************* included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 235034116096, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/771c67eb-56e6-4736-8c67-668502d4ecf5', u'spm': {u'priority': 5, u'status': u'none'}, u'id': u'771c67eb-56e6-4736-8c67-668502d4ecf5', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host0.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:ac5566ae1e1a'}, u'port': 54321, u'hardware_information': {u'serial_number': u'70833W1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0030-3810-8033-B7C04F335731', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:TiiMiaHi++kqhmurXdlQjtwbb3Q1oIBi5ab2alKujyI'}, u'address': u' host0.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host0', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host0/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host0/swap rd.lvm.lv=onn_host0/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 250759610368, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/fb1e62d5-1dc1-4ccc-8b2b-cf48f7077d0d', u'spm': {u'priority': 5, u'status': u'none'}, u'id': u'fb1e62d5-1dc1-4ccc-8b2b-cf48f7077d0d', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host1.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:2f5ea98fcec4'}, u'port': 54321, u'hardware_information': {u'serial_number': u'FYRTGX1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0059-5210-8054-C6C04F475831', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:HGU2WhIlPfxgXHXHOE8IYT4/NGAQeUBRe0QA34qQ+nc'}, u'address': u' host1.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host1', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host1/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host1/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rd.lvm.lv=onn_host1/swap rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) included: /usr/share/ansible/roles/ovirt.cluster-upgrade/tasks/upgrade.yml for localhost => (item={u'comment': u'', u'update_available': True, u'protocol': u'stomp', u'affinity_labels': [], u'hooks': [], u'max_scheduling_memory': 232492367872, u'cluster': {u'href': u'/ovirt-engine/api/clusters/a45fe964-9989-11e8-b3f7-00163e4bf18a', u'id': u'a45fe964-9989-11e8-b3f7-00163e4bf18a'}, u'href': u'/ovirt-engine/api/hosts/fd0752d8-2d41-45b0-887a-0ffacbb8a237', u'spm': {u'priority': 5, u'status': u'spm'}, u'id': u'fd0752d8-2d41-45b0-887a-0ffacbb8a237', u'external_status': u'ok', u'statistics': [], u'certificate': {u'organization': u'xxxxxxxx.com', u'subject': u'O=xxxxxxxx.com,CN=host2.xxxxxxxx.com'}, u'nics': [], u'iscsi': {u'initiator': u'iqn.1994-05.com.redhat:369c9881d24e'}, u'port': 54321, u'hardware_information': {u'serial_number': u'D9733W1', u'product_name': u'PowerEdge R720', u'uuid': u'4C4C4544-0039-3710-8033-C4C04F335731', u'supported_rng_sources': [u'hwrng', u'random'], u'manufacturer': u'Dell Inc.'}, u'version': {u'full_version': u'vdsm-4.20.43-1.el7', u'revision': 0, u'build': 43, u'minor': 20, u'major': 4}, u'memory': 270258929664, u'ksm': {u'enabled': False}, u'se_linux': {u'mode': u'permissive'}, u'type': u'ovirt_node', u'storage_connection_extensions': [], u'status': u'up', u'tags': [], u'katello_errata': [], u'external_network_provider_configurations': [], u'ssh': {u'port': 22, u'fingerprint': u'SHA256:cSgSzFFQaziGHDeKH1CIfXd8YbheGTaft3XBgyr4YgQ'}, u'address': u' host2.xxxxxxxx.com', u'numa_nodes': [], u'device_passthrough': {u'enabled': False}, u'unmanaged_networks': [], u'permissions': [], u'numa_supported': True, u'libvirt_version': {u'full_version': u'libvirt-3.9.0-14.el7_5.8', u'revision': 0, u'build': 0, u'minor': 9, u'major': 3}, u'power_management': {u'kdump_detection': True, u'enabled': True, u'pm_proxies': [{u'type': u'cluster'}, {u'type': u'dc'}], u'automatic_pm_enabled': True}, u'name': u'host2', u'devices': [], u'summary': {u'active': 4, u'migrating': 0, u'total': 4}, u'auto_numa_status': u'enable', u'transparent_huge_pages': {u'enabled': True}, u'network_attachments': [], u'os': {u'version': {u'full_version': u'7 - 5.1804.5.el7.centos', u'major': 7}, u'type': u'RHEL', u'custom_kernel_cmdline': u'', u'reported_kernel_cmdline': u'BOOT_IMAGE=/ovirt-node-ng-4.2.7.1-0.20181114.0+1/vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/onn_host2/ovirt-node-ng-4.2.7.1-0.20181114.0+1 ro crashkernel=auto rd.lvm.lv=onn_host2/ovirt-node-ng-4.2.7.1-0.20181114.0+1 rd.lvm.lv=onn_host2/swap rhgb quiet LANG=en_CA.UTF-8 img.bootid=ovirt-node-ng-4.2.7.1-0.20181114.0+1'}, u'cpu': {u'speed': 1200.0, u'name': u'Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz', u'topology': {u'cores': 8, u'threads': 1, u'sockets': 2}}, u'kdump_status': u'disabled'}) TASK [oVirt.cluster-upgrade : Upgrade host] ********************************************************************************************************************************************************************************************************************************************************************************** changed: [localhost] TASK [oVirt.cluster-upgrade : Upgrade host] ********************************************************************************************************************************************************************************************************************************************************************************** changed: [localhost] TASK [oVirt.cluster-upgrade : Upgrade host] ********************************************************************************************************************************************************************************************************************************************************************************** changed: [localhost] TASK [oVirt.cluster-upgrade : Set original cluster policy] ******************************************************************************************************************************************************************************************************************************************************************* changed: [localhost] TASK [oVirt.cluster-upgrade : Start again stopped VMs] *********************************************************************************************************************************************************************************************************************************************************************** TASK [oVirt.cluster-upgrade : Start again pin to host VMs] ******************************************************************************************************************************************************************************************************************************************************************* TASK [oVirt.cluster-upgrade : Logout from oVirt] ***************************************************************************************************************************************************************************************************************************************************************************** ok: [localhost] PLAY RECAP ******************************************************************************************************************************************************************************************************************************************************************************************************************* localhost : ok=21 changed=5 unreachable=0 failed=0

2 2

Unable to get the proper console of vm
by Shikhar Verma 25 Jan '19

25 Jan '19

Hi, I have created the virtual machine from ovirt manager but when I am trying to get the console of the vm to do the installation of it but it is only giving two two line and even i have tried as run once and selected CD ROM as first priority and attached the ISO of centos7 SeaBIOS (version 1.11.0-2.e17) Machine UUID ------- Also, from manager, newly launched vm is showing green.. And from the host machine, it is showing this error Jan 21 19:23:24 servera libvirtd: 2019-01-21 13:53:24.286+0000: 12800: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected I am using the latest version version of ovirt-engine & host as well. Please respond. Thanks Shikhar

3 4

Re: Unable to deatch/remove ISO DOMAIN
by Strahil 25 Jan '19

25 Jan '19

1 0

Ovirt 4.2.8 allows to remove a gluster volume without detaching the storage domain
by Strahil Nikolov 25 Jan '19

25 Jan '19

Hello Community, As I'm still experimenting with my ovirt lab , I have managed somehow to remove my gluster volume ('gluster volume list' confirms it) whithout detaching the storage domain. This sounds to me as bug, am I right ? Steps to reproduce:1. Create a replica 3 arbiter 1 gluster volume2. Create a storage domain of it3. Go to Volumes and select the name of the volume4. Press remove and confirm . The tasks fails , but the volume is now gone in gluster . I guess , I have to do some cleanup in the DB in order to fix that. Best Regards,Strahil Nikolov

3 3

ovirt.org HTML Issue?
by zachary.winter＠vcwise.com 25 Jan '19

25 Jan '19

Hello all, I wasn't sure where to post this or email this (I promised I looked around), but the web page for the following web page in the manual appears to have HTML issues towards the end of the page: https://www.ovirt.org/documentation/admin-guide/chap-Pools.html Should I notify someone else that it ought to be fixed?

2 1

How to replace vMware infrastructure with oVirt
by Mannish Kumar 25 Jan '19

25 Jan '19

Hi, I have two Esxi hosts managed by VMware vCenter Server. I want to create a similar infrastructure with oVirt. I know that oVirt is similar to VMware vCenter Server but not sure what to replace the Esxi hosts with in oVirt Environment. I am looking to build oVirt with Self-Hosted Engine.It would be great help if someone could help me to build this.

3 2

Re: [Gluster-users] Отн: Gluster performance issues - need advise
by Strahil Nikolov 25 Jan '19

25 Jan '19

Dear Darrell, I found the issue and now I can reach the maximum of the network with a fuse client.Here is a short overview:1. I noticed that working with a new gluster volume is reaching my network speed - I was quite excited.2. Then I have destroyed my gluster volume and created a new one and started adding features from ovirt Once I have added features.shard on -> I hit the same performance from before. Increasing the shard size to 16MB didn't help at all. For my case where I have 2 Virtualization hosts with single data gluster volume - sharding is not neccessary, but for larger setups it will be a problem. As this looks to me as a bug - can someone tell me where I can report it ? Thanks to all who guided me in this journey of GlusterFS ! I have learned so much , as my prior knowledge was only in Ceph. Best Regards,Strahil Nikolov В четвъртък, 24 януари 2019 г., 17:53:50 ч. Гринуич+2, Darrell Budic <budic(a)onholyground.com> написа: Strahil- The fuse client is what it is, it’s limited by operating in user land and waiting for the gluster servers to acknowledge all the writes. I noted you're using ovirt, you should look into enabling the libgfapi engine setting to run your VMs with libgf natively. You can’t test directly from the host with that, but you can run your tests inside the VMs. I saw significant throughput and latency improvements that way. It’s still somewhat beta, so you’ll probably need to search the overt-users mailing list to find info on enabling it. Good luck! On Jan 24, 2019, at 4:32 AM, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: Dear Amar, Community, it seems the issue is in the fuse client itself. Here is the latest update:1. I have added the following:server.event-threads: 4 client.event-threads: 4 performance.stat-prefetch: onperformance.strict-o-direct: off Results: no change 2. Allowed nfs and connected ovirt1 to the gluster volume:nfs.disable: off Results: Drastic improvement in performance as follows: [root@ovirt1 data]# dd if=/dev/zero of=largeio bs=1M count=5000 status=progress 5000+0 records in 5000+0 records out 5242880000 bytes (5.2 GB) copied, 53.0443 s, 98.8 MB/s So I would be happy if anyone guide me in order to fix the situation as the fuse client is the best way to use glusterfs, and it seems the glusterfs-server is not the guilty one. Thanks in advance for your guidance.I have learned so much. Best Regards,Strahil Nikolov От: Strahil <hunter86_bg(a)yahoo.com> До: Amar Tumballi Suryanarayan <atumball(a)redhat.com> Копие: Gluster-users <gluster-users(a)gluster.org> Изпратен: сряда, 23 януари 2019 г. 18:44 Тема: Re: [Gluster-users] Gluster performance issues - need advise Dear Amar, Thanks for your email. Actually my concerns were on both topics.Would you recommend any perf options that will be suitable ? After mentioning the network usage, I just checked it and it seems duringthe test session, ovirt1 (both client and host) is using no more than 455Mbit/s which is half the network bandwidth. I'm still in the middle of nowhere, so any ideas are welcome. Best Regards,Strahil Nikolov On Jan 23, 2019 17:49, Amar Tumballi Suryanarayan <atumball(a)redhat.com> wrote: I didn't understand the issue properly. Mostly I missed something. Are you concerned the performance is 49MB/s with and without perf options? or are you expecting it to be 123MB/s as over the n/w you get that speed? If it is the first problem, then you are actually having 'performance.write-behind on' in both options, and it is the only perf xlator which comes into action during the test you ran. If it is the second, then please be informed that gluster does client side replication, which means, n/w would be split in half for write operations (like write(), creat() etc), so the number you are getting is almost the maximum with 1GbE. Regards,Amar On Wed, Jan 23, 2019 at 8:38 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: Hello Community, recently I have built a new lab based on oVirt and CentOS 7. During deployment I had some hicups, but now the engine is up and running - but gluster is causing me trouble. Symptoms: Slow VM install from DVD, poor write performance. The latter has been tested via: dd if=/dev/zero of=/rhev/data-center/mnt/glusterSD/ovirt1.localdomain:_data bs=1M count=1000 status=progress The reported speed is 60MB/s which is way too low for my setup. My lab design: https://drive.google.com/file/d/1SiW21ASPXHRAEuE_jZ50R3FoO-NcnFqT/view?usp=… Gluster version is 3.12.15 So far I have done: 1. Added 'server.allow-insecure on' (with 'option rpc-auth-allow-insecure on' in glusterd.vol) Volume info after that change: Volume Name: data Type: Replicate Volume ID: 9b06a1e9-8102-4cd7-bc56-84960a1efaa2 Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: ovirt1.localdomain:/gluster_bricks/data/data Brick2: ovirt2.localdomain:/gluster_bricks/data/data Brick3: ovirt3.localdomain:/gluster_bricks/data/data (arbiter) Options Reconfigured: performance.client-io-threads: off nfs.disable: on transport.address-family: inet performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.low-prio-threads: 32 network.remote-dio: off cluster.eager-lock: enable cluster.quorum-type: auto cluster.server-quorum-type: server cluster.data-self-heal-algorithm: full cluster.locking-scheme: granular cluster.shd-max-threads: 8 cluster.shd-wait-qlength: 10000 features.shard: on user.cifs: off storage.owner-uid: 36 storage.owner-gid: 36 network.ping-timeout: 30 performance.strict-o-direct: on cluster.granular-entry-heal: enable server.allow-insecure: on Seems no positive or negative effect so far. 2. Tested with tmpfs on all bricks -> ovirt1 mounted gluster volume -> max 60MB/s (bs=1M without 'oflag=direct') [root@ovirt1 data]# dd if=/dev/zero of=large_io bs=1M count=4000 status=progress 4177526784 bytes (4.2 GB) copied, 70.843409 s, 59.0 MB/s 4000+0 records in 4000+0 records out 4194304000 bytes (4.2 GB) copied, 71.1407 s, 59.0 MB/s [root@ovirt1 data]# rm -f large_io [root@ovirt1 data]# gluster volume profile data info Brick: ovirt1.localdomain:/gluster_bricks/data/data --------------------------------------------------- Cumulative Stats: Block Size: 131072b+ No. of Reads: 8 No. of Writes: 44968 %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop --------- ----------- ----------- ----------- ------------ ---- 0.00 0.00 us 0.00 us 0.00 us 3 FORGET 0.00 0.00 us 0.00 us 0.00 us 35 RELEASE 0.00 0.00 us 0.00 us 0.00 us 28 RELEASEDIR 0.00 78.00 us 78.00 us 78.00 us 1 FSTAT 0.00 35.67 us 26.00 us 73.00 us 6 FLUSH 0.00 324.00 us 324.00 us 324.00 us 1 XATTROP 0.00 45.80 us 38.00 us 54.00 us 10 STAT 0.00 227.67 us 216.00 us 242.00 us 3 CREATE 0.00 113.38 us 68.00 us 381.00 us 8 READ 0.00 39.82 us 1.00 us 148.00 us 28 OPENDIR 0.00 67.54 us 10.00 us 283.00 us 24 GETXATTR 0.00 59.97 us 45.00 us 113.00 us 32 OPEN 0.00 24.41 us 13.00 us 89.00 us 161 INODELK 0.00 43.43 us 28.00 us 214.00 us 93 STATFS 0.00 246.35 us 11.00 us 1155.00 us 20 READDIR 0.00 283.00 us 233.00 us 353.00 us 18 READDIRP 0.00 153.23 us 122.00 us 259.00 us 87 MKNOD 0.01 99.77 us 10.00 us 258.00 us 442 LOOKUP 0.31 49.22 us 27.00 us 540.00 us 45620 FXATTROP 0.77 124.24 us 87.00 us 604.00 us 44968 WRITE 0.93 15767.71 us 15.00 us 305833.00 us 431 ENTRYLK 1.99 160711.39 us 3332.00 us 406037.00 us 90 UNLINK 96.00 5167.82 us 18.00 us 55972.00 us 135349 FINODELK Duration: 380 seconds Data Read: 1048576 bytes Data Written: 5894045696 bytes Interval 0 Stats: Block Size: 131072b+ No. of Reads: 8 No. of Writes: 44968 %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop --------- ----------- ----------- ----------- ------------ ---- 0.00 0.00 us 0.00 us 0.00 us 3 FORGET 0.00 0.00 us 0.00 us 0.00 us 35 RELEASE 0.00 0.00 us 0.00 us 0.00 us 28 RELEASEDIR 0.00 78.00 us 78.00 us 78.00 us 1 FSTAT 0.00 35.67 us 26.00 us 73.00 us 6 FLUSH 0.00 324.00 us 324.00 us 324.00 us 1 XATTROP 0.00 45.80 us 38.00 us 54.00 us 10 STAT 0.00 227.67 us 216.00 us 242.00 us 3 CREATE 0.00 113.38 us 68.00 us 381.00 us 8 READ 0.00 39.82 us 1.00 us 148.00 us 28 OPENDIR 0.00 67.54 us 10.00 us 283.00 us 24 GETXATTR 0.00 59.97 us 45.00 us 113.00 us 32 OPEN 0.00 24.41 us 13.00 us 89.00 us 161 INODELK 0.00 43.43 us 28.00 us 214.00 us 93 STATFS 0.00 246.35 us 11.00 us 1155.00 us 20 READDIR 0.00 283.00 us 233.00 us 353.00 us 18 READDIRP 0.00 153.23 us 122.00 us 259.00 us 87 MKNOD 0.01 99.77 us 10.00 us 258.00 us 442 LOOKUP 0.31 49.22 us 27.00 us 540.00 us 45620 FXATTROP 0.77 124.24 us 87.00 us 604.00 us 44968 WRITE 0.93 15767.71 us 15.00 us 305833.00 us 431 ENTRYLK 1.99 160711.39 us 3332.00 us 406037.00 us 90 UNLINK 96.00 5167.82 us 18.00 us 55972.00 us 135349 FINODELK Duration: 380 seconds Data Read: 1048576 bytes Data Written: 5894045696 bytes Brick: ovirt3.localdomain:/gluster_bricks/data/data --------------------------------------------------- Cumulative Stats: Block Size: 1b+ No. of Reads: 0 No. of Writes: 39328 %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop --------- ----------- ----------- ----------- ------------ ---- 0.00 0.00 us 0.00 us 0.00 us 2 FORGET 0.00 0.00 us 0.00 us 0.00 us 12 RELEASE 0.00 0.00 us 0.00 us 0.00 us 17 RELEASEDIR 0.00 101.00 us 101.00 us 101.00 us 1 FSTAT 0.00 51.50 us 20.00 us 81.00 us 4 FLUSH 0.01 219.50 us 188.00 us 251.00 us 2 CREATE 0.01 43.45 us 11.00 us 90.00 us 11 GETXATTR 0.01 62.30 us 38.00 us 119.00 us 10 OPEN 0.01 50.59 us 1.00 us 102.00 us 17 OPENDIR 0.01 24.60 us 12.00 us 64.00 us 40 INODELK 0.02 176.30 us 10.00 us 765.00 us 10 READDIR 0.07 63.08 us 39.00 us 133.00 us 78 UNLINK 0.13 27.35 us 10.00 us 91.00 us 333 ENTRYLK 0.13 126.89 us 99.00 us 179.00 us 76 MKNOD 0.42 116.70 us 8.00 us 8661.00 us 261 LOOKUP 28.73 51.79 us 22.00 us 2574.00 us 39822 FXATTROP 29.52 53.87 us 16.00 us 3290.00 us 39328 WRITE 40.92 24.71 us 10.00 us 3224.00 us 118864 FINODELK Duration: 189 seconds Data Read: 0 bytes Data Written: 39328 bytes Interval 0 Stats: Block Size: 1b+ No. of Reads: 0 No. of Writes: 39328 %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop --------- ----------- ----------- ----------- ------------ ---- 0.00 0.00 us 0.00 us 0.00 us 2 FORGET 0.00 0.00 us 0.00 us 0.00 us 12 RELEASE 0.00 0.00 us 0.00 us 0.00 us 17 RELEASEDIR 0.00 101.00 us 101.00 us 101.00 us 1 FSTAT 0.00 51.50 us 20.00 us 81.00 us 4 FLUSH 0.01 219.50 us 188.00 us 251.00 us 2 CREATE 0.01 43.45 us 11.00 us 90.00 us 11 GETXATTR 0.01 62.30 us 38.00 us 119.00 us 10 OPEN 0.01 50.59 us 1.00 us 102.00 us 17 OPENDIR 0.01 24.60 us 12.00 us 64.00 us 40 INODELK 0.02 176.30 us 10.00 us 765.00 us 10 READDIR 0.07 63.08 us 39.00 us 133.00 us 78 UNLINK 0.13 27.35 us 10.00 us 91.00 us 333 ENTRYLK 0.13 126.89 us 99.00 us 179.00 us 76 MKNOD 0.42 116.70 us 8.00 us 8661.00 us 261 LOOKUP 28.73 51.79 us 22.00 us 2574.00 us 39822 FXATTROP 29.52 53.87 us 16.00 us 3290.00 us 39328 WRITE 40.92 24.71 us 10.00 us 3224.00 us 118864 FINODELK Duration: 189 seconds Data Read: 0 bytes Data Written: 39328 bytes Brick: ovirt2.localdomain:/gluster_bricks/data/data --------------------------------------------------- Cumulative Stats: Block Size: 512b+ 131072b+ No. of Reads: 0 0 No. of Writes: 36 76758 %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop --------- ----------- ----------- ----------- ------------ ---- 0.00 0.00 us 0.00 us 0.00 us 6 FORGET 0.00 0.00 us 0.00 us 0.00 us 87 RELEASE 0.00 0.00 us 0.00 us 0.00 us 96 RELEASEDIR 0.00 100.50 us 80.00 us 121.00 us 2 REMOVEXATTR 0.00 101.00 us 101.00 us 101.00 us 2 SETXATTR 0.00 36.18 us 22.00 us 62.00 us 11 FLUSH 0.00 57.44 us 42.00 us 77.00 us 9 FTRUNCATE 0.00 82.56 us 59.00 us 138.00 us 9 FSTAT 0.00 89.42 us 67.00 us 161.00 us 12 SETATTR 0.00 272.40 us 235.00 us 296.00 us 5 CREATE 0.01 154.28 us 88.00 us 320.00 us 18 XATTROP 0.01 45.29 us 1.00 us 319.00 us 96 OPENDIR 0.01 86.69 us 30.00 us 379.00 us 62 STAT 0.01 64.30 us 47.00 us 169.00 us 84 OPEN 0.02 107.34 us 23.00 us 273.00 us 73 READDIRP 0.02 4688.00 us 86.00 us 9290.00 us 2 TRUNCATE 0.02 59.29 us 13.00 us 394.00 us 165 GETXATTR 0.03 128.51 us 27.00 us 338.00 us 96 FSYNC 0.03 240.75 us 14.00 us 1943.00 us 52 READDIR 0.04 65.59 us 26.00 us 293.00 us 279 STATFS 0.06 180.77 us 118.00 us 306.00 us 148 MKNOD 0.14 37.98 us 17.00 us 192.00 us 1598 INODELK 0.67 91.68 us 12.00 us 1141.00 us 3186 LOOKUP 10.10 55.92 us 28.00 us 1658.00 us 78608 FXATTROP 11.89 6814.76 us 18.00 us 301246.00 us 760 ENTRYLK 19.44 36.55 us 14.00 us 2353.00 us 231535 FINODELK 25.21 142.92 us 62.00 us 593.00 us 76794 WRITE 32.28 91283.68 us 28.00 us 316658.00 us 154 UNLINK Duration: 1206 seconds Data Read: 0 bytes Data Written: 10060843008 bytes Interval 0 Stats: Block Size: 512b+ 131072b+ No. of Reads: 0 0 No. of Writes: 36 76758 %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop --------- ----------- ----------- ----------- ------------ ---- 0.00 0.00 us 0.00 us 0.00 us 6 FORGET 0.00 0.00 us 0.00 us 0.00 us 87 RELEASE 0.00 0.00 us 0.00 us 0.00 us 96 RELEASEDIR 0.00 100.50 us 80.00 us 121.00 us 2 REMOVEXATTR 0.00 101.00 us 101.00 us 101.00 us 2 SETXATTR 0.00 36.18 us 22.00 us 62.00 us 11 FLUSH 0.00 57.44 us 42.00 us 77.00 us 9 FTRUNCATE 0.00 82.56 us 59.00 us 138.00 us 9 FSTAT 0.00 89.42 us 67.00 us 161.00 us 12 SETATTR 0.00 272.40 us 235.00 us 296.00 us 5 CREATE 0.01 154.28 us 88.00 us 320.00 us 18 XATTROP 0.01 45.29 us 1.00 us 319.00 us 96 OPENDIR 0.01 86.69 us 30.00 us 379.00 us 62 STAT 0.01 64.30 us 47.00 us 169.00 us 84 OPEN 0.02 107.34 us 23.00 us 273.00 us 73 READDIRP 0.02 4688.00 us 86.00 us 9290.00 us 2 TRUNCATE 0.02 59.29 us 13.00 us 394.00 us 165 GETXATTR 0.03 128.51 us 27.00 us 338.00 us 96 FSYNC 0.03 240.75 us 14.00 us 1943.00 us 52 READDIR 0.04 65.59 us 26.00 us 293.00 us 279 STATFS 0.06 180.77 us 118.00 us 306.00 us 148 MKNOD 0.14 37.98 us 17.00 us 192.00 us 1598 INODELK 0.67 91.66 us 12.00 us 1141.00 us 3186 LOOKUP 10.10 55.92 us 28.00 us 1658.00 us 78608 FXATTROP 11.89 6814.76 us 18.00 us 301246.00 us 760 ENTRYLK 19.44 36.55 us 14.00 us 2353.00 us 231535 FINODELK 25.21 142.92 us 62.00 us 593.00 us 76794 WRITE 32.28 91283.68 us 28.00 us 316658.00 us 154 UNLINK Duration: 1206 seconds Data Read: 0 bytes Data Written: 10060843008 bytes This indicates to me that it's not a problem in Disk/LVM/FileSystem layout. Most probably I haven't created the volume properly or some option/feature is disabled ?!? Network shows OK for a gigabit: [root@ovirt1 data]# dd if=/dev/zero status=progress | nc ovirt2 9999 3569227264 bytes (3.6 GB) copied, 29.001052 s, 123 MB/s^C 7180980+0 records in 7180979+0 records out 3676661248 bytes (3.7 GB) copied, 29.8739 s, 123 MB/s I'm looking for any help... you can share your volume info also. Thanks in advance. Best Regards, Strahil Nikolov _______________________________________________ Gluster-users mailing list Gluster-users(a)gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users -- Amar Tumballi (amarts) Dear Amar, Thanks for your email. Actually my concerns were on both topics. Would you recommend any perf options that will be suitable ? After mentioning the network usage, I just checked it and it seems duringthe test session, ovirt1 (both client and host) is using no more than 455Mbit/s which is half the network bandwidth. I'm still in the middle of nowhere, so any ideas are welcome. Best Regards, Strahil Nikolov On Jan 23, 2019 17:49, Amar Tumballi Suryanarayan <atumball(a)redhat.com> wrote: > > I didn't understand the issue properly. Mostly I missed something. > > Are you concerned the performance is 49MB/s with and without perf options? or are you expecting it to be 123MB/s as over the n/w you get that speed? > > If it is the first problem, then you are actually having 'performance.write-behind on' in both options, and it is the only perf xlator which comes into action during the test you ran. > > If it is the second, then please be informed that gluster does client side replication, which means, n/w would be split in half for write operations (like write(), creat() etc), so the number you are getting is almost the maximum with 1GbE. > > Regards, > Amar > > On Wed, Jan 23, 2019 at 8:38 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Hello Community, >> >> recently I have built a new lab based on oVirt and CentOS 7. >> During deployment I had some hicups, but now the engine is up and running - but gluster is causing me trouble. >> >> Symptoms: Slow VM install from DVD, poor write performance. The latter has been tested via: >> dd if=/dev/zero of=/rhev/data-center/mnt/glusterSD/ovirt1.localdomain:_data bs=1M count=1000 status=progress >> >> The reported speed is 60MB/s which is way too low for my setup. >> >> My lab design: >> https://drive.google.com/file/d/1SiW21ASPXHRAEuE_jZ50R3FoO-NcnFqT/view?usp=… >> Gluster version is 3.12.15 >> >> So far I have done: >> >> 1. Added 'server.allow-insecure on' (with 'option rpc-auth-allow-insecure on' in glusterd.vol) >> Volume info after that change: >> >> Volume Name: data >> Type: Replicate >> Volume ID: 9b06a1e9-8102-4cd7-bc56-84960a1efaa2 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x (2 + 1) = 3 >> Transport-type: tcp >> Bricks: >> Brick1: ovirt1.localdomain:/gluster_bricks/data/data >> Brick2: ovirt2.localdomain:/gluster_bricks/data/data >> Brick3: ovirt3.localdomain:/gluster_bricks/data/data (arbiter) >> Options Reconfigured: >> performance.client-io-threads: off >> nfs.disable: on >> transport.address-family: inet >> performance.quick-read: off >> performance.read-ahead: off >> performance.io-cache: off >> performance.low-prio-threads: 32 >> network.remote-dio: off >> cluster.eager-lock: enable >> cluster.quorum-type: auto >> cluster.server-quorum-type: server >> cluster.data-self-heal-algorithm: full >> cluster.locking-scheme: granular >> cluster.shd-max-threads: 8 >> cluster.shd-wait-qlength: 10000 >> features.shard: on >> user.cifs: off >> storage.owner-uid: 36 >> storage.owner-gid: 36 >> network.ping-timeout: 30 >> performance.strict-o-direct: on >> cluster.granular-entry-heal: enable >> server.allow-insecure: on >> >> Seems no positive or negative effect so far. >> >> 2. Tested with tmpfs on all bricks -> ovirt1 mounted gluster volume -> max 60MB/s (bs=1M without 'oflag=direct') >> >> >> [root@ovirt1 data]# dd if=/dev/zero of=large_io bs=1M count=4000 status=progress >> 4177526784 bytes (4.2 GB) copied, 70.843409 s, 59.0 MB/s >> 4000+0 records in >> 4000+0 records out >> 4194304000 bytes (4.2 GB) copied, 71.1407 s, 59.0 MB/s >> [root@ovirt1 data]# rm -f large_io >> [root@ovirt1 data]# gluster volume profile data info >> Brick: ovirt1.localdomain:/gluster_bricks/data/data >> --------------------------------------------------- >> Cumulative Stats: >> Block Size: 131072b+ >> No. of Reads: 8 >> No. of Writes: 44968 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop >> --------- ----------- ----------- ----------- ------------ ---- >> 0.00 0.00 us 0.00 us 0.00 us 3 FORGET >> 0.00 0.00 us 0.00 us 0.00 us 35 RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 28 RELEASEDIR >> 0.00 78.00 us 78.00 us 78.00 us 1 FSTAT >> 0.00 35.67 us 26.00 us 73.00 us 6 FLUSH >> 0.00 324.00 us 324.00 us 324.00 us 1 XATTROP >> 0.00 45.80 us 38.00 us 54.00 us 10 STAT >> 0.00 227.67 us 216.00 us 242.00 us 3 CREATE >> 0.00 113.38 us 68.00 us 381.00 us 8 READ >> 0.00 39.82 us 1.00 us 148.00 us 28 OPENDIR >> 0.00 67.54 us 10.00 us 283.00 us 24 GETXATTR >> 0.00 59.97 us 45.00 us 113.00 us 32 OPEN >> 0.00 24.41 us 13.00 us 89.00 us 161 INODELK >> 0.00 43.43 us 28.00 us 214.00 us 93 STATFS >> 0.00 246.35 us 11.00 us 1155.00 us 20 READDIR >> 0.00 283.00 us 233.00 us 353.00 us 18 READDIRP >> 0.00 153.23 us 122.00 us 259.00 us 87 MKNOD >> 0.01 99.77 us 10.00 us 258.00 us 442 LOOKUP >> 0.31 49.22 us 27.00 us 540.00 us 45620 FXATTROP >> 0.77 124.24 us 87.00 us 604.00 us 44968 WRITE >> 0.93 15767.71 us 15.00 us 305833.00 us 431 ENTRYLK >> 1.99 160711.39 us 3332.00 us 406037.00 us 90 UNLINK >> 96.00 5167.82 us 18.00 us 55972.00 us 135349 FINODELK >> >> Duration: 380 seconds >> Data Read: 1048576 bytes >> Data Written: 5894045696 bytes >> >> Interval 0 Stats: >> Block Size: 131072b+ >> No. of Reads: 8 >> No. of Writes: 44968 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop >> --------- ----------- ----------- ----------- ------------ ---- >> 0.00 0.00 us 0.00 us 0.00 us 3 FORGET >> 0.00 0.00 us 0.00 us 0.00 us 35 RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 28 RELEASEDIR >> 0.00 78.00 us 78.00 us 78.00 us 1 FSTAT >> 0.00 35.67 us 26.00 us 73.00 us 6 FLUSH >> 0.00 324.00 us 324.00 us 324.00 us 1 XATTROP >> 0.00 45.80 us 38.00 us 54.00 us 10 STAT >> 0.00 227.67 us 216.00 us 242.00 us 3 CREATE >> 0.00 113.38 us 68.00 us 381.00 us 8 READ >> 0.00 39.82 us 1.00 us 148.00 us 28 OPENDIR >> 0.00 67.54 us 10.00 us 283.00 us 24 GETXATTR >> 0.00 59.97 us 45.00 us 113.00 us 32 OPEN >> 0.00 24.41 us 13.00 us 89.00 us 161 INODELK >> 0.00 43.43 us 28.00 us 214.00 us 93 STATFS >> 0.00 246.35 us 11.00 us 1155.00 us 20 READDIR >> 0.00 283.00 us 233.00 us 353.00 us 18 READDIRP >> 0.00 153.23 us 122.00 us 259.00 us 87 MKNOD >> 0.01 99.77 us 10.00 us 258.00 us 442 LOOKUP >> 0.31 49.22 us 27.00 us 540.00 us 45620 FXATTROP >> 0.77 124.24 us 87.00 us 604.00 us 44968 WRITE >> 0.93 15767.71 us 15.00 us 305833.00 us 431 ENTRYLK >> 1.99 160711.39 us 3332.00 us 406037.00 us 90 UNLINK >> 96.00 5167.82 us 18.00 us 55972.00 us 135349 FINODELK >> >> Duration: 380 seconds >> Data Read: 1048576 bytes >> Data Written: 5894045696 bytes >> >> Brick: ovirt3.localdomain:/gluster_bricks/data/data >> --------------------------------------------------- >> Cumulative Stats: >> Block Size: 1b+ >> No. of Reads: 0 >> No. of Writes: 39328 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop >> --------- ----------- ----------- ----------- ------------ ---- >> 0.00 0.00 us 0.00 us 0.00 us 2 FORGET >> 0.00 0.00 us 0.00 us 0.00 us 12 RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 17 RELEASEDIR >> 0.00 101.00 us 101.00 us 101.00 us 1 FSTAT >> 0.00 51.50 us 20.00 us 81.00 us 4 FLUSH >> 0.01 219.50 us 188.00 us 251.00 us 2 CREATE >> 0.01 43.45 us 11.00 us 90.00 us 11 GETXATTR >> 0.01 62.30 us 38.00 us 119.00 us 10 OPEN >> 0.01 50.59 us 1.00 us 102.00 us 17 OPENDIR >> 0.01 24.60 us 12.00 us 64.00 us 40 INODELK >> 0.02 176.30 us 10.00 us 765.00 us 10 READDIR >> 0.07 63.08 us 39.00 us 133.00 us 78 UNLINK >> 0.13 27.35 us 10.00 us 91.00 us 333 ENTRYLK >> 0.13 126.89 us 99.00 us 179.00 us 76 MKNOD >> 0.42 116.70 us 8.00 us 8661.00 us 261 LOOKUP >> 28.73 51.79 us 22.00 us 2574.00 us 39822 FXATTROP >> 29.52 53.87 us 16.00 us 3290.00 us 39328 WRITE >> 40.92 24.71 us 10.00 us 3224.00 us 118864 FINODELK >> >> Duration: 189 seconds >> Data Read: 0 bytes >> Data Written: 39328 bytes >> >> Interval 0 Stats: >> Block Size: 1b+ >> No. of Reads: 0 >> No. of Writes: 39328 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop >> --------- ----------- ----------- ----------- ------------ ---- >> 0.00 0.00 us 0.00 us 0.00 us 2 FORGET >> 0.00 0.00 us 0.00 us 0.00 us 12 RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 17 RELEASEDIR >> 0.00 101.00 us 101.00 us 101.00 us 1 FSTAT >> 0.00 51.50 us 20.00 us 81.00 us 4 FLUSH >> 0.01 219.50 us 188.00 us 251.00 us 2 CREATE >> 0.01 43.45 us 11.00 us 90.00 us 11 GETXATTR >> 0.01 62.30 us 38.00 us 119.00 us 10 OPEN >> 0.01 50.59 us 1.00 us 102.00 us 17 OPENDIR >> 0.01 24.60 us 12.00 us 64.00 us 40 INODELK >> 0.02 176.30 us 10.00 us 765.00 us 10 READDIR >> 0.07 63.08 us 39.00 us 133.00 us 78 UNLINK >> 0.13 27.35 us 10.00 us 91.00 us 333 ENTRYLK >> 0.13 126.89 us 99.00 us 179.00 us 76 MKNOD >> 0.42 116.70 us 8.00 us 8661.00 us 261 LOOKUP >> 28.73 51.79 us 22.00 us 2574.00 us 39822 FXATTROP >> 29.52 53.87 us 16.00 us 3290.00 us 39328 WRITE >> 40.92 24.71 us 10.00 us 3224.00 us 118864 FINODELK >> >> Duration: 189 seconds >> Data Read: 0 bytes >> Data Written: 39328 bytes >> >> Brick: ovirt2.localdomain:/gluster_bricks/data/data >> --------------------------------------------------- >> Cumulative Stats: >> Block Size: 512b+ 131072b+ >> No. of Reads: 0 0 >> No. of Writes: 36 76758 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop >> --------- ----------- ----------- ----------- ------------ ---- >> 0.00 0.00 us 0.00 us 0.00 us 6 FORGET >> 0.00 0.00 us 0.00 us 0.00 us 87 RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 96 RELEASEDIR >> 0.00 100.50 us 80.00 us 121.00 us 2 REMOVEXATTR >> 0.00 101.00 us 101.00 us 101.00 us 2 SETXATTR >> 0.00 36.18 us 22.00 us 62.00 us 11 FLUSH >> 0.00 57.44 us 42.00 us 77.00 us 9 FTRUNCATE >> 0.00 82.56 us 59.00 us 138.00 us 9 FSTAT >> 0.00 89.42 us 67.00 us 161.00 us 12 SETATTR >> 0.00 272.40 us 235.00 us 296.00 us 5 CREATE >> 0.01 154.28 us 88.00 us 320.00 us 18 XATTROP >> 0.01 45.29 us 1.00 us 319.00 us 96 OPENDIR >> 0.01 86.69 us 30.00 us 379.00 us 62 STAT >> 0.01 64.30 us 47.00 us 169.00 us 84 OPEN >> 0.02 107.34 us 23.00 us 273.00 us 73 READDIRP >> 0.02 4688.00 us 86.00 us 9290.00 us 2 TRUNCATE >> 0.02 59.29 us 13.00 us 394.00 us 165 GETXATTR >> 0.03 128.51 us 27.00 us 338.00 us 96 FSYNC >> 0.03 240.75 us 14.00 us 1943.00 us 52 READDIR >> 0.04 65.59 us 26.00 us 293.00 us 279 STATFS >> 0.06 180.77 us 118.00 us 306.00 us 148 MKNOD >> 0.14 37.98 us 17.00 us 192.00 us 1598 INODELK >> 0.67 91.68 us 12.00 us 1141.00 us 3186 LOOKUP >> 10.10 55.92 us 28.00 us 1658.00 us 78608 FXATTROP >> 11.89 6814.76 us 18.00 us 301246.00 us 760 ENTRYLK >> 19.44 36.55 us 14.00 us 2353.00 us 231535 FINODELK >> 25.21 142.92 us 62.00 us 593.00 us 76794 WRITE >> 32.28 91283.68 us 28.00 us 316658.00 us 154 UNLINK >> >> Duration: 1206 seconds >> Data Read: 0 bytes >> Data Written: 10060843008 bytes >> >> Interval 0 Stats: >> Block Size: 512b+ 131072b+ >> No. of Reads: 0 0 >> No. of Writes: 36 76758 >> %-latency Avg-latency Min-Latency Max-Latency No. of calls Fop >> --------- ----------- ----------- ----------- ------------ ---- >> 0.00 0.00 us 0.00 us 0.00 us 6 FORGET >> 0.00 0.00 us 0.00 us 0.00 us 87 RELEASE >> 0.00 0.00 us 0.00 us 0.00 us 96 RELEASEDIR >> 0.00 100.50 us 80.00 us 121.00 us 2 REMOVEXATTR >> 0.00 101.00 us 101.00 us 101.00 us 2 SETXATTR >> 0.00 36.18 us 22.00 us 62.00 us 11 FLUSH >> 0.00 57.44 us 42.00 us 77.00 us 9 FTRUNCATE >> 0.00 82.56 us 59.00 us 138.00 us 9 FSTAT >> 0.00 89.42 us 67.00 us 161.00 us 12 SETATTR >> 0.00 272.40 us 235.00 us 296.00 us 5 CREATE >> 0.01 154.28 us 88.00 us 320.00 us 18 XATTROP >> 0.01 45.29 us 1.00 us 319.00 us 96 OPENDIR >> 0.01 86.69 us 30.00 us 379.00 us 62 STAT >> 0.01 64.30 us 47.00 us 169.00 us 84 OPEN >> 0.02 107.34 us 23.00 us 273.00 us 73 READDIRP >> 0.02 4688.00 us 86.00 us 9290.00 us 2 TRUNCATE >> 0.02 59.29 us 13.00 us 394.00 us 165 GETXATTR >> 0.03 128.51 us 27.00 us 338.00 us 96 FSYNC >> 0.03 240.75 us 14.00 us 1943.00 us 52 READDIR >> 0.04 65.59 us 26.00 us 293.00 us 279 STATFS >> 0.06 180.77 us 118.00 us 306.00 us 148 MKNOD >> 0.14 37.98 us 17.00 us 192.00 us 1598 INODELK >> 0.67 91.66 us 12.00 us 1141.00 us 3186 LOOKUP >> 10.10 55.92 us 28.00 us 1658.00 us 78608 FXATTROP >> 11.89 6814.76 us 18.00 us 301246.00 us 760 ENTRYLK >> 19.44 36.55 us 14.00 us 2353.00 us 231535 FINODELK >> 25.21 142.92 us 62.00 us 593.00 us 76794 WRITE >> 32.28 91283.68 us 28.00 us 316658.00 us 154 UNLINK >> >> Duration: 1206 seconds >> Data Read: 0 bytes >> Data Written: 10060843008 bytes >> >> >> >> This indicates to me that it's not a problem in Disk/LVM/FileSystem layout. >> >> Most probably I haven't created the volume properly or some option/feature is disabled ?!? >> Network shows OK for a gigabit: >> [root@ovirt1 data]# dd if=/dev/zero status=progress | nc ovirt2 9999 >> 3569227264 bytes (3.6 GB) copied, 29.001052 s, 123 MB/s^C >> 7180980+0 records in >> 7180979+0 records out >> 3676661248 bytes (3.7 GB) copied, 29.8739 s, 123 MB/s >> >> >> I'm looking for any help... you can share your volume info also. >> >> Thanks in advance. >> >> Best Regards, >> Strahil Nikolov >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users(a)gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users > > > > -- > Amar Tumballi (amarts) _______________________________________________ Gluster-users mailing list Gluster-users(a)gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users

1 0

[ANN] oVirt 4.3.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 25 Jan '19

25 Jan '19

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 4.3.0, as of January 24th, 2018 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first release candidate of the 4.3.0 version. This release brings more than 130 enhancements and more than 450 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Node NG is already available for CentOS 7 - oVirt Node NG for Fedora 28 (tech preview) is being delayed due to build issues with the build system. Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 2

Re: Unable to deatch/remove ISO DOMAIN
by Strahil Nikolov 25 Jan '19

25 Jan '19

Hi Martin, this is my history (please keep in mind that it might get distorted due to mail client).Note: I didn't stop the ovirt-engine.service and this caused some errors to be logged - but the engine is still working without issues. As I said - this is my test lab and I was willing to play around :) Good Luck! ssh root@engine #Switch to postgre usersu - postgres #If you don't load this , there will be no path for psql , nor it will start at allsource /opt/rh/rh-postgresql95/enable #open the DB. psql engine #Commands in the DB:select id, storage_name from storage_domain_static; select storage_domain_id, ovf_disk_id from storage_domains_ovf_info where storag e_domain_id='fbe7bf1a-2f03-4311-89fa-5031eab638bf'; delete from storage_domain_dynamic where id = 'fbe7bf1a-2f03-4311-89fa-5031eab63 8bf'; delete from storage_domain_static where id = 'fbe7bf1a-2f03-4311-89fa-5031eab638 bf'; delete from base_disks where disk_id = '7a155ede-5317-4860-aa93-de1dc283213e';delete from base_disks where disk_id = '7dedd0e1-8ce8-444e-8a3d-117c46845bb0'; delete from storage_domains_ovf_info where storage_domain_id = 'fbe7bf1a-2f03-43 11-89fa-5031eab638bf'; delete from storage_pool_iso_map where storage_id = 'fbe7bf1a-2f03-4311-89fa-503 1eab638bf'; #I think this shows all tables:select table_schema ,table_name from information_schema.tables order by table_sc hema,table_name;#Maybe you don't need this one and you need to find the NFS volume:select * from gluster_volumes ;delete from gluster_volumes where id = '9b06a1e9-8102-4cd7-bc56-84960a1efaa2'; select table_schema ,table_name from information_schema.tables order by table_sc hema,table_name; # The previous delete failed as there was an entry in storage_server_connections.#In your case could be differentselect * from storage_server_connections;delete from storage_server_connections where id = '490ee1c7-ae29-45c0-bddd-61708 22c8490';delete from gluster_volumes where id = '9b06a1e9-8102-4cd7-bc56-84960a1efaa2'; Best Regards,Strahil Nikolov В петък, 25 януари 2019 г., 11:04:01 ч. Гринуич+2, Martin Humaj <mhumaj(a)gmail.com> написа: Hi StrahilI have tried to use the same ip and nfs export to replace the original, did not work properly. If you can guide me how to do it in engine DB i would appreciate it. This is a test system. thank you Martin On Fri, Jan 25, 2019 at 9:56 AM Strahil <hunter86_bg(a)yahoo.com> wrote: Can you create a temporary NFS server which to be accessed during the removal?I have managed to edit the engine's DB to get rid of cluster domain, but this is not recommended for production systems :)

1 0

Unable to deatch/remove ISO DOMAIN
by mhumaj＠gmail.com 25 Jan '19

25 Jan '19

Ovirt - 4.2.4.5-1.el7 Is there any way how to remove the nfs ISO domain in DB? We cannot get rid of it in GUI and we are not able to use it anymore. The problem is that NFS server which was responsible for DATA TYPE ISO domain was deleted. Even we are trying to change it in settings it will not allow us to do it. Error messages: Failed to activate Storage Domain oVirt-ISO (Data Center InnovationCenter) by admin@internal-authz VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: (u'61045461-10ff-4f7a-b464-67198c4a6c27',) tank you

1 0

Re: ovirt 4.2 HCI rollout
by Simone Tiraboschi 24 Jan '19

24 Jan '19

On Thu, Jan 24, 2019 at 3:20 PM Markus Schaufler < markus.schaufler(a)digit-all.at> wrote: > no... > > all logs in that folder are attached in the mail before. > OK, unfortunately in this case I can just suggest to retry and, when it reaches [ INFO ] TASK [Check engine VM health] try to connect to the engine VM via ssh and check what's happening there to ovirt-engine > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 15:16:52 > *An:* Markus Schaufler > *Cc:* Dominik Holler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 3:14 PM Markus Schaufler < > markus.schaufler(a)digit-all.at> wrote: > > The hosted engine is not running and cannot be started. > > > > Do you have on your first host a directory > like /var/log/ovirt-hosted-engine-setup/engine-logs-2019-01-21T22:47:03Z > with logs from the engine VM? > > > > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 14:45:59 > *An:* Markus Schaufler > *Cc:* Dominik Holler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 2:21 PM Markus Schaufler < > markus.schaufler(a)digit-all.at> wrote: > > Hi, > > > thanks for the replies. > > > I updated to 4.2.8 and tried again: > > > [ INFO ] TASK [Check engine VM health] > [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": > true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": > "0:00:00.165316", "end": "2019-01-24 14:12:06.899564", "rc": 0, "start": > "2019-01-24 14:12:06.734248", "stderr": "", "stderr_lines": [], "stdout": > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, > \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}"]} > > > > It's still the same issue: the host fail to properly check the status of > the engine over a dedicate health page. > > You should connect to ovirt-hci.res01.ads.ooe.local and check the status > of ovirt-engine service and /var/log/ovirt-engine/engine.log there. > > > > [ INFO ] TASK [Check VM status at virt level] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Fail if engine VM is not running] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Get VDSM's target engine VM stats] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Convert stats to JSON format] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address from VDSM stats] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Fail if the Engine has no IP address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Fail if Engine IP is different from engine's FQDN resolved > IP] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Reconfigure OVN central address] > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: 'dict object' has no > attribute 'stdout_lines'\n\nThe error appears to have been in > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': line > 518, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n # > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > - name: Reconfigure OVN central address\n ^ here\n"} > > > > attached you'll find the setup logs. > > > best regards, > > Markus Schaufler > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 11:56:50 > *An:* Dominik Holler > *Cc:* Markus Schaufler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 9:40 AM Dominik Holler <dholler(a)redhat.com> wrote: > > On Tue, 22 Jan 2019 11:15:12 +0000 > Markus Schaufler <markus.schaufler(a)digit-all.at> wrote: > > > Thanks for your reply, > > > > getent ahosts ovirt-hci.res01.ads.ooe.local | cut -d' ' -f1 | uniq > > 10.1.31.20 > > > > attached you'll find the logs. > > > > Thanks, to my eyes this looks like a bug. > I tried to isolate the relevant lines in the attached playbook. > > Markus, would you be so kind to check if ovirt-4.2.8 is working for you? > > > > OK, understood: the real error was just a few lines before what Dominik > pointed out: > > "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": > true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}", > "stdout_lines": [ > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, > \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}" > ] > }" > 2019-01-21 13:57:46,695+0100 ERROR ansible failed {'status': 'FAILED', > 'ansible_type': 'task', 'ansible_task': u'Check engine VM health', > 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, > \'stderr_lines\': [], u\'changed\': True, u\'end\': u\'2019-01-21 > 13:57:46.242423\', \'_ansible_no_log\': False, u\'stdout\': u\'{"1": > {"conf_on_shared_storage": true, "live-data": true, "extra": > "metadata_parse_version=1\\\\nmetadata_feature_version=1\\\\ntimestamp=5792 > (Mon Jan 21 13:57:4', 'ansible_host': u'localhost', 'ansible_playbook': > u'/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml'} > > and in particular it's here: > for some reason we got \"engine-status\": {\"reason\": \"failed > liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": > \"Up\"} > over 120 attempts: we have to check engine.log (it got collected as well > from the engine VM) to understand why the engine was failing to start. > > > > > > ________________________________ > > Von: Dominik Holler <dholler(a)redhat.com> > > Gesendet: Montag, 21. Jänner 2019 17:52:35 > > An: Markus Schaufler > > Cc: users(a)ovirt.org; Simone Tiraboschi > > Betreff: Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > Would you please share the related ovirt-host-deploy-ansible-*.log > > stored on the host in /var/log/ovirt-hosted-engine-setup ? > > > > Would you please also share the output of > > getent ahosts YOUR_HOSED_ENGNE_FQDN | cut -d' ' -f1 | uniq > > if executed on this host? > > > > > > On Mon, 21 Jan 2019 13:37:53 -0000 > > "Markus Schaufler" <markus.schaufler(a)digit-all.at> wrote: > > > > > Hi, > > > > > > I'm trying a (nested) ovirt 4.2.7 HCI rollout on 3 centos VM's by > > > following > > > > https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… > > > gluster deployment was successful but at HE deployment "stage 5" I > > > got following error: > > > > > > [ INFO ] TASK [Reconfigure OVN central address] > > > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes > > > an option with an undefined variable. The error was: 'dict object' > > > has no attribute 'stdout_lines'\n\nThe error appears to have been > > > in > > > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': > > > line 522, column 5, but may\nbe elsewhere in the file depending on > > > the exact syntax problem.\n\nThe offending line appears to be:\n\n > > > # > > > > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > > > - name: Reconfigure OVN central address\n ^ here\n"} > > > > > > > > > /var/log/messages: > > > Jan 21 14:09:56 HCI01 journal: ovirt-ha-agent > > > ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR > > > Engine VM stopped on localhost Jan 21 14:10:01 HCI01 systemd: > > > Started Session 22 of user root. Jan 21 14:10:02 HCI01 systemd: > > > Started Session c306 of user root. Jan 21 14:10:03 HCI01 systemd: > > > Started Session c307 of user root. Jan 21 14:10:06 HCI01 > > > vdsm[3650]: WARN executor state: count=5 workers=set([<Worker > > > name=periodic/4 waiting task#=141 at 0x7fd2d4316910>, <Worker > > > name=periodic/1 running <Task discardable <Operation > > > action=<vdsm.virt.sampling.VMBulkstatsMonitor object at > > > 0x7fd2d4679490> at 0x7fd2d4679710> timeout=7.5, duration=7 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> disca rded task#=413 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>, <Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>name=periodic/3 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>waiting task#=414 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>name=periodic/5 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>task#=0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>name > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>=periodic/2 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>task#=412 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>]) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>device > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>vnet0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>left > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>promiscuous > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>mode > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> > > > [1548076206.9177] device (vnet0): state change: disconnected -> > > > unmanaged (reason 'unmanaged', sys-iface-state: 'remo ved') Jan 21 > > > 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9180] > > > device (vnet0): released from master device ovirtmgmt Jan 21 > > > 14:10:06 HCI01 lldpad: recvfrom(Event interface): No buffer space > > > available Jan 21 14:10:06 HCI01 libvirtd: 2019-01-21 > > > 13:10:06.925+0000: 2651: error : qemuMonitorIORead:609 : Unable to > > > read from monitor: Connection reset by peer Jan 21 14:10:07 HCI01 > > > kvm: 0 guests now active Jan 21 14:10:07 HCI01 systemd-machined: > > > Machine qemu-3-HostedEngine terminated. Jan 21 14:10:07 HCI01 > > > libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : > > > qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 > > > 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: > > > warning : qemuGetProcessInfo:1406 : cannot parse process status > > > data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: > > > 2704: warning : qemuGetProcessInfo:1406 : cannot parse process > > > status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 > > > 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot > > > parse process status data Jan 21 14:10:07 HCI01 libvirtd: > > > 2019-01-21 13:10:07.126+0000: 2704: error : > > > virNetDevTapInterfaceStats:764 : internal error: /proc/net/dev: > > > Interface not found Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out > > > -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vnet 0' > > > failed: iptables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out > > > vnet0 -g FP-vnet0' failed: iptables v 1.4.21: goto 'FP-vnet0' is > > > not a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev > > > --physdev-in vnet0 -g FJ-vnet0' failed: iptables v1. 4.21: goto > > > 'FJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' > > > failed: iptable s v1.4.21: goto 'HJ-vnet0' is not a > > > chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FP-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FP-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vne t0' > > > failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FP-vnet0' failed: ip6tables v1.4.21: > > > goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: > > > ip6tables v 1.4.21: goto 'FJ-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HJ-vnet0' failed: ip6tab les v1.4.21: goto > > > 'HJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FP-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FP-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F FJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X FJ-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HJ-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X HJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' > > > failed: Illegal target name 'libvirt-J-vnet0'. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal target name 'libvirt-P-vnet0'. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j > > > libvirt-J-vnet0' failed: Illegal targe t name 'libvirt-J-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal targ et name 'libvirt-P-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -L libvirt-J-vnet0' failed: > > > Chain 'libvirt-J-vnet0' doesn't exis t. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -L libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out > > > vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not > > > a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or > > > 'iptables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > iptables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: iptables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: iptables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FO-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FO-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' > > > failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > ip6tables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: ip6tables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: ip6tables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FO-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X FO-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FI-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F HI-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X HI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D > > > POSTROUTING -o vnet0 -j libvirt-O-vnet0' failed: Illegal target > > > name 'libvirt-O-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L > > > libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet0' failed: > > > Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-O-vnet0' failed: Chain > > > 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 vdsm[3650]: > > > WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.ovirt-guest-agent.0 > > > already removed Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting > > > to remove a non existing network: > > > ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 > > > HCI01 vdsm[3650]: WARN Attempting to remove a non existing net > > > user: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 > > > 14:10:07 HCI01 vdsm[3650]: WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.org.qemu.guest_agent.0 > > > already removed > > > > > > any ideas on that? > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > > > To unsubscribe send an email to users-leave(a)ovirt.org > > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > Archives: > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMMX5CY6VHFWW… > > > >

1 0

Re: ovirt 4.2 HCI rollout
by Simone Tiraboschi 24 Jan '19

24 Jan '19

On Thu, Jan 24, 2019 at 3:14 PM Markus Schaufler < markus.schaufler(a)digit-all.at> wrote: > The hosted engine is not running and cannot be started. > > > Do you have on your first host a directory like /var/log/ovirt-hosted-engine-setup/engine-logs-2019-01-21T22:47:03Z with logs from the engine VM? > > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 14:45:59 > *An:* Markus Schaufler > *Cc:* Dominik Holler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 2:21 PM Markus Schaufler < > markus.schaufler(a)digit-all.at> wrote: > > Hi, > > > thanks for the replies. > > > I updated to 4.2.8 and tried again: > > > [ INFO ] TASK [Check engine VM health] > [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": > true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": > "0:00:00.165316", "end": "2019-01-24 14:12:06.899564", "rc": 0, "start": > "2019-01-24 14:12:06.734248", "stderr": "", "stderr_lines": [], "stdout": > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, > \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}"]} > > > > It's still the same issue: the host fail to properly check the status of > the engine over a dedicate health page. > > You should connect to ovirt-hci.res01.ads.ooe.local and check the status > of ovirt-engine service and /var/log/ovirt-engine/engine.log there. > > > > [ INFO ] TASK [Check VM status at virt level] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Fail if engine VM is not running] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Get VDSM's target engine VM stats] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Convert stats to JSON format] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address from VDSM stats] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Fail if the Engine has no IP address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Fail if Engine IP is different from engine's FQDN resolved > IP] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Reconfigure OVN central address] > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: 'dict object' has no > attribute 'stdout_lines'\n\nThe error appears to have been in > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': line > 518, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n # > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > - name: Reconfigure OVN central address\n ^ here\n"} > > > > attached you'll find the setup logs. > > > best regards, > > Markus Schaufler > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 11:56:50 > *An:* Dominik Holler > *Cc:* Markus Schaufler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 9:40 AM Dominik Holler <dholler(a)redhat.com> wrote: > > On Tue, 22 Jan 2019 11:15:12 +0000 > Markus Schaufler <markus.schaufler(a)digit-all.at> wrote: > > > Thanks for your reply, > > > > getent ahosts ovirt-hci.res01.ads.ooe.local | cut -d' ' -f1 | uniq > > 10.1.31.20 > > > > attached you'll find the logs. > > > > Thanks, to my eyes this looks like a bug. > I tried to isolate the relevant lines in the attached playbook. > > Markus, would you be so kind to check if ovirt-4.2.8 is working for you? > > > > OK, understood: the real error was just a few lines before what Dominik > pointed out: > > "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": > true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}", > "stdout_lines": [ > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, > \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}" > ] > }" > 2019-01-21 13:57:46,695+0100 ERROR ansible failed {'status': 'FAILED', > 'ansible_type': 'task', 'ansible_task': u'Check engine VM health', > 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, > \'stderr_lines\': [], u\'changed\': True, u\'end\': u\'2019-01-21 > 13:57:46.242423\', \'_ansible_no_log\': False, u\'stdout\': u\'{"1": > {"conf_on_shared_storage": true, "live-data": true, "extra": > "metadata_parse_version=1\\\\nmetadata_feature_version=1\\\\ntimestamp=5792 > (Mon Jan 21 13:57:4', 'ansible_host': u'localhost', 'ansible_playbook': > u'/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml'} > > and in particular it's here: > for some reason we got \"engine-status\": {\"reason\": \"failed > liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": > \"Up\"} > over 120 attempts: we have to check engine.log (it got collected as well > from the engine VM) to understand why the engine was failing to start. > > > > > > ________________________________ > > Von: Dominik Holler <dholler(a)redhat.com> > > Gesendet: Montag, 21. Jänner 2019 17:52:35 > > An: Markus Schaufler > > Cc: users(a)ovirt.org; Simone Tiraboschi > > Betreff: Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > Would you please share the related ovirt-host-deploy-ansible-*.log > > stored on the host in /var/log/ovirt-hosted-engine-setup ? > > > > Would you please also share the output of > > getent ahosts YOUR_HOSED_ENGNE_FQDN | cut -d' ' -f1 | uniq > > if executed on this host? > > > > > > On Mon, 21 Jan 2019 13:37:53 -0000 > > "Markus Schaufler" <markus.schaufler(a)digit-all.at> wrote: > > > > > Hi, > > > > > > I'm trying a (nested) ovirt 4.2.7 HCI rollout on 3 centos VM's by > > > following > > > > https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… > > > gluster deployment was successful but at HE deployment "stage 5" I > > > got following error: > > > > > > [ INFO ] TASK [Reconfigure OVN central address] > > > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes > > > an option with an undefined variable. The error was: 'dict object' > > > has no attribute 'stdout_lines'\n\nThe error appears to have been > > > in > > > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': > > > line 522, column 5, but may\nbe elsewhere in the file depending on > > > the exact syntax problem.\n\nThe offending line appears to be:\n\n > > > # > > > > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > > > - name: Reconfigure OVN central address\n ^ here\n"} > > > > > > > > > /var/log/messages: > > > Jan 21 14:09:56 HCI01 journal: ovirt-ha-agent > > > ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR > > > Engine VM stopped on localhost Jan 21 14:10:01 HCI01 systemd: > > > Started Session 22 of user root. Jan 21 14:10:02 HCI01 systemd: > > > Started Session c306 of user root. Jan 21 14:10:03 HCI01 systemd: > > > Started Session c307 of user root. Jan 21 14:10:06 HCI01 > > > vdsm[3650]: WARN executor state: count=5 workers=set([<Worker > > > name=periodic/4 waiting task#=141 at 0x7fd2d4316910>, <Worker > > > name=periodic/1 running <Task discardable <Operation > > > action=<vdsm.virt.sampling.VMBulkstatsMonitor object at > > > 0x7fd2d4679490> at 0x7fd2d4679710> timeout=7.5, duration=7 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> disca rded task#=413 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>, <Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>name=periodic/3 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>waiting task#=414 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>name=periodic/5 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>task#=0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>name > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>=periodic/2 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>task#=412 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>]) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>device > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>vnet0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>left > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>promiscuous > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>mode > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> > > > [1548076206.9177] device (vnet0): state change: disconnected -> > > > unmanaged (reason 'unmanaged', sys-iface-state: 'remo ved') Jan 21 > > > 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9180] > > > device (vnet0): released from master device ovirtmgmt Jan 21 > > > 14:10:06 HCI01 lldpad: recvfrom(Event interface): No buffer space > > > available Jan 21 14:10:06 HCI01 libvirtd: 2019-01-21 > > > 13:10:06.925+0000: 2651: error : qemuMonitorIORead:609 : Unable to > > > read from monitor: Connection reset by peer Jan 21 14:10:07 HCI01 > > > kvm: 0 guests now active Jan 21 14:10:07 HCI01 systemd-machined: > > > Machine qemu-3-HostedEngine terminated. Jan 21 14:10:07 HCI01 > > > libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : > > > qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 > > > 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: > > > warning : qemuGetProcessInfo:1406 : cannot parse process status > > > data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: > > > 2704: warning : qemuGetProcessInfo:1406 : cannot parse process > > > status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 > > > 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot > > > parse process status data Jan 21 14:10:07 HCI01 libvirtd: > > > 2019-01-21 13:10:07.126+0000: 2704: error : > > > virNetDevTapInterfaceStats:764 : internal error: /proc/net/dev: > > > Interface not found Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out > > > -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vnet 0' > > > failed: iptables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out > > > vnet0 -g FP-vnet0' failed: iptables v 1.4.21: goto 'FP-vnet0' is > > > not a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev > > > --physdev-in vnet0 -g FJ-vnet0' failed: iptables v1. 4.21: goto > > > 'FJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' > > > failed: iptable s v1.4.21: goto 'HJ-vnet0' is not a > > > chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FP-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FP-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vne t0' > > > failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FP-vnet0' failed: ip6tables v1.4.21: > > > goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: > > > ip6tables v 1.4.21: goto 'FJ-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HJ-vnet0' failed: ip6tab les v1.4.21: goto > > > 'HJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FP-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FP-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F FJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X FJ-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HJ-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X HJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' > > > failed: Illegal target name 'libvirt-J-vnet0'. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal target name 'libvirt-P-vnet0'. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j > > > libvirt-J-vnet0' failed: Illegal targe t name 'libvirt-J-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal targ et name 'libvirt-P-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -L libvirt-J-vnet0' failed: > > > Chain 'libvirt-J-vnet0' doesn't exis t. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -L libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out > > > vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not > > > a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or > > > 'iptables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > iptables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: iptables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: iptables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FO-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FO-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' > > > failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > ip6tables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: ip6tables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: ip6tables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FO-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X FO-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FI-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F HI-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X HI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D > > > POSTROUTING -o vnet0 -j libvirt-O-vnet0' failed: Illegal target > > > name 'libvirt-O-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L > > > libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet0' failed: > > > Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-O-vnet0' failed: Chain > > > 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 vdsm[3650]: > > > WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.ovirt-guest-agent.0 > > > already removed Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting > > > to remove a non existing network: > > > ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 > > > HCI01 vdsm[3650]: WARN Attempting to remove a non existing net > > > user: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 > > > 14:10:07 HCI01 vdsm[3650]: WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.org.qemu.guest_agent.0 > > > already removed > > > > > > any ideas on that? > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > > > To unsubscribe send an email to users-leave(a)ovirt.org > > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > Archives: > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMMX5CY6VHFWW… > > > >

2 1

Re: ovirt 4.2 HCI rollout
by Simone Tiraboschi 24 Jan '19

24 Jan '19

On Thu, Jan 24, 2019 at 2:21 PM Markus Schaufler < markus.schaufler(a)digit-all.at> wrote: > Hi, > > > thanks for the replies. > > > I updated to 4.2.8 and tried again: > > > [ INFO ] TASK [Check engine VM health] > [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": > true, "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": > "0:00:00.165316", "end": "2019-01-24 14:12:06.899564", "rc": 0, "start": > "2019-01-24 14:12:06.734248", "stderr": "", "stderr_lines": [], "stdout": > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}", "stdout_lines": ["{\"1\": {\"conf_on_shared_storage\": true, > \"live-data\": true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3049 > (Thu Jan 24 14:11:59 > 2019)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3049 (Thu Jan 24 > 14:11:59 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"0c1a3ddb\", > \"local_conf_timestamp\": 3049, \"host-ts\": 3049}, \"global_maintenance\": > false}"]} > It's still the same issue: the host fail to properly check the status of the engine over a dedicate health page. You should connect to ovirt-hci.res01.ads.ooe.local and check the status of ovirt-engine service and /var/log/ovirt-engine/engine.log there. > [ INFO ] TASK [Check VM status at virt level] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Fail if engine VM is not running] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Get VDSM's target engine VM stats] > [ INFO ] changed: [localhost] > [ INFO ] TASK [Convert stats to JSON format] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address from VDSM stats] > [ INFO ] ok: [localhost] > [ INFO ] TASK [Fail if the Engine has no IP address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Fail if Engine IP is different from engine's FQDN resolved > IP] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Get target engine VM IPv4 address] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [Reconfigure OVN central address] > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: 'dict object' has no > attribute 'stdout_lines'\n\nThe error appears to have been in > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': line > 518, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n # > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > - name: Reconfigure OVN central address\n ^ here\n"} > > > > attached you'll find the setup logs. > > > best regards, > > Markus Schaufler > ------------------------------ > *Von:* Simone Tiraboschi <stirabos(a)redhat.com> > *Gesendet:* Donnerstag, 24. Jänner 2019 11:56:50 > *An:* Dominik Holler > *Cc:* Markus Schaufler; users(a)ovirt.org > *Betreff:* Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > On Thu, Jan 24, 2019 at 9:40 AM Dominik Holler <dholler(a)redhat.com> wrote: > > On Tue, 22 Jan 2019 11:15:12 +0000 > Markus Schaufler <markus.schaufler(a)digit-all.at> wrote: > > > Thanks for your reply, > > > > getent ahosts ovirt-hci.res01.ads.ooe.local | cut -d' ' -f1 | uniq > > 10.1.31.20 > > > > attached you'll find the logs. > > > > Thanks, to my eyes this looks like a bug. > I tried to isolate the relevant lines in the attached playbook. > > Markus, would you be so kind to check if ovirt-4.2.8 is working for you? > > > > OK, understood: the real error was just a few lines before what Dominik > pointed out: > > "stdout": "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": > true, \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}", > "stdout_lines": [ > "{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, > \"extra\": > \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5792 > (Mon Jan 21 13:57:45 > 2019)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=5792 (Mon Jan 21 > 13:57:45 > 2019)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\", > \"hostname\": \"HCI01.res01.ads.ooe.local\", \"host-id\": 1, > \"engine-status\": {\"reason\": \"failed liveliness check\", \"health\": > \"bad\", \"vm\": \"up\", \"detail\": \"Up\"}, \"score\": 3000, \"stopped\": > false, \"maintenance\": false, \"crc32\": \"ba303717\", > \"local_conf_timestamp\": 5792, \"host-ts\": 5792}, \"global_maintenance\": > false}" > ] > }" > 2019-01-21 13:57:46,695+0100 ERROR ansible failed {'status': 'FAILED', > 'ansible_type': 'task', 'ansible_task': u'Check engine VM health', > 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, > \'stderr_lines\': [], u\'changed\': True, u\'end\': u\'2019-01-21 > 13:57:46.242423\', \'_ansible_no_log\': False, u\'stdout\': u\'{"1": > {"conf_on_shared_storage": true, "live-data": true, "extra": > "metadata_parse_version=1\\\\nmetadata_feature_version=1\\\\ntimestamp=5792 > (Mon Jan 21 13:57:4', 'ansible_host': u'localhost', 'ansible_playbook': > u'/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml'} > > and in particular it's here: > for some reason we got \"engine-status\": {\"reason\": \"failed > liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\": > \"Up\"} > over 120 attempts: we have to check engine.log (it got collected as well > from the engine VM) to understand why the engine was failing to start. > > > > > > ________________________________ > > Von: Dominik Holler <dholler(a)redhat.com> > > Gesendet: Montag, 21. Jänner 2019 17:52:35 > > An: Markus Schaufler > > Cc: users(a)ovirt.org; Simone Tiraboschi > > Betreff: Re: [ovirt-users] ovirt 4.2 HCI rollout > > > > Would you please share the related ovirt-host-deploy-ansible-*.log > > stored on the host in /var/log/ovirt-hosted-engine-setup ? > > > > Would you please also share the output of > > getent ahosts YOUR_HOSED_ENGNE_FQDN | cut -d' ' -f1 | uniq > > if executed on this host? > > > > > > On Mon, 21 Jan 2019 13:37:53 -0000 > > "Markus Schaufler" <markus.schaufler(a)digit-all.at> wrote: > > > > > Hi, > > > > > > I'm trying a (nested) ovirt 4.2.7 HCI rollout on 3 centos VM's by > > > following > > > > https://ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyper… > > > gluster deployment was successful but at HE deployment "stage 5" I > > > got following error: > > > > > > [ INFO ] TASK [Reconfigure OVN central address] > > > [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes > > > an option with an undefined variable. The error was: 'dict object' > > > has no attribute 'stdout_lines'\n\nThe error appears to have been > > > in > > > '/usr/share/ovirt-hosted-engine-setup/ansible/create_target_vm.yml': > > > line 522, column 5, but may\nbe elsewhere in the file depending on > > > the exact syntax problem.\n\nThe offending line appears to be:\n\n > > > # > > > > https://github.com/oVirt/ovirt-engine/blob/master/packaging/playbooks/roles… > > > - name: Reconfigure OVN central address\n ^ here\n"} > > > > > > > > > /var/log/messages: > > > Jan 21 14:09:56 HCI01 journal: ovirt-ha-agent > > > ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR > > > Engine VM stopped on localhost Jan 21 14:10:01 HCI01 systemd: > > > Started Session 22 of user root. Jan 21 14:10:02 HCI01 systemd: > > > Started Session c306 of user root. Jan 21 14:10:03 HCI01 systemd: > > > Started Session c307 of user root. Jan 21 14:10:06 HCI01 > > > vdsm[3650]: WARN executor state: count=5 workers=set([<Worker > > > name=periodic/4 waiting task#=141 at 0x7fd2d4316910>, <Worker > > > name=periodic/1 running <Task discardable <Operation > > > action=<vdsm.virt.sampling.VMBulkstatsMonitor object at > > > 0x7fd2d4679490> at 0x7fd2d4679710> timeout=7.5, duration=7 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> disca rded task#=413 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>, <Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>name=periodic/3 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>waiting task#=414 at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>name=periodic/5 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>task#=0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> 0x7fd2d5ed0510>0x7fd2d5ed0b10>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>, > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650><Worker > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>name > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>=periodic/2 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>waiting > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>task#=412 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>at > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>]) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>device > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>vnet0 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>left > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>promiscuous > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>mode > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>Jan > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>21 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>14:10:06 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>HCI01 > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>kernel: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>ovirtmgmt: > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>port > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>2(vnet0) > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>entered > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>disabled > > > 0x7fd2d4679490> 0x7fd33c1e0ed0> > 0x7fd2d5ed0510>0x7fd2d5ed0b10>0x7fd2d425f650>0x7fd2d5ed07d0>state > > > Jan 21 14:10:06 HCI01 NetworkManager[3666]: <info> > > > [1548076206.9177] device (vnet0): state change: disconnected -> > > > unmanaged (reason 'unmanaged', sys-iface-state: 'remo ved') Jan 21 > > > 14:10:06 HCI01 NetworkManager[3666]: <info> [1548076206.9180] > > > device (vnet0): released from master device ovirtmgmt Jan 21 > > > 14:10:06 HCI01 lldpad: recvfrom(Event interface): No buffer space > > > available Jan 21 14:10:06 HCI01 libvirtd: 2019-01-21 > > > 13:10:06.925+0000: 2651: error : qemuMonitorIORead:609 : Unable to > > > read from monitor: Connection reset by peer Jan 21 14:10:07 HCI01 > > > kvm: 0 guests now active Jan 21 14:10:07 HCI01 systemd-machined: > > > Machine qemu-3-HostedEngine terminated. Jan 21 14:10:07 HCI01 > > > libvirtd: 2019-01-21 13:10:07.125+0000: 2704: warning : > > > qemuGetProcessInfo:1406 : cannot parse process status data Jan 21 > > > 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: 2704: > > > warning : qemuGetProcessInfo:1406 : cannot parse process status > > > data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 13:10:07.125+0000: > > > 2704: warning : qemuGetProcessInfo:1406 : cannot parse process > > > status data Jan 21 14:10:07 HCI01 libvirtd: 2019-01-21 > > > 13:10:07.125+0000: 2704: warning : qemuGetProcessInfo:1406 : cannot > > > parse process status data Jan 21 14:10:07 HCI01 libvirtd: > > > 2019-01-21 13:10:07.126+0000: 2704: error : > > > virNetDevTapInterfaceStats:764 : internal error: /proc/net/dev: > > > Interface not found Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out > > > -m physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vnet 0' > > > failed: iptables v1.4.21: goto 'FP-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-out -m physdev --physdev-out > > > vnet0 -g FP-vnet0' failed: iptables v 1.4.21: goto 'FP-vnet0' is > > > not a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-in -m physdev > > > --physdev-in vnet0 -g FJ-vnet0' failed: iptables v1. 4.21: goto > > > 'FJ-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-host-in -m physdev --physdev-in vnet0 -g HJ-vnet0' > > > failed: iptable s v1.4.21: goto 'HJ-vnet0' is not a > > > chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FP-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FP-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HJ-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HJ-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FP-vne t0' > > > failed: ip6tables v1.4.21: goto 'FP-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FP-vnet0' failed: ip6tables v1.4.21: > > > goto 'FP-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FJ-vnet0' failed: > > > ip6tables v 1.4.21: goto 'FJ-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HJ-vnet0' failed: ip6tab les v1.4.21: goto > > > 'HJ-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FP-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FP-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F FJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X FJ-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F HJ-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X HJ-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -D PREROUTING -i vnet0 -j libvirt-J-vnet0' > > > failed: Illegal target name 'libvirt-J-vnet0'. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal target name 'libvirt-P-vnet0'. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D PREROUTING -i vnet0 -j > > > libvirt-J-vnet0' failed: Illegal targe t name 'libvirt-J-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -D POSTROUTING -o vnet0 -j > > > libvirt-P-vnet0' failed: Illegal targ et name 'libvirt-P-vnet0'. > > > Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -L libvirt-J-vnet0' failed: > > > Chain 'libvirt-J-vnet0' doesn't exis t. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -L libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-J-vnet0' failed: Chain > > > 'libvirt-J-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -F libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-P-vnet0' failed: Chain > > > 'libvirt-P-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-out -m physdev --physdev-is-bridged --physdev-out > > > vnet0 -g FO-vnet0' failed: iptables v1.4.21: goto 'FO-vnet0' is not > > > a chain#012#012Try `iptables -h' or 'iptables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: iptables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `iptables -h' or > > > 'iptables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > iptables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `iptables -h' or 'iptables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/iptables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: iptables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `iptables -h' or 'iptables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: iptables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FO-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FO-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F FI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X FI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/iptables -w2 -w -F HI-vnet0' failed: > > > iptables: No chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/iptables -w2 > > > -w -X HI-vnet0' failed: iptables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-is-bridged --physdev-out vnet0 -g FO-vnet0' > > > failed: ip6tables v1.4.21: goto 'FO-vnet0' is not a > > > chain#012#012Try `ip6tables -h' or 'ip6tables --help' for more > > > information. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -D libvirt-out -m > > > physdev --physdev-out vnet0 -g FO-vnet0' failed: ip6tables v1.4.21: > > > goto 'FO-vnet0' is not a chain#012#012Try `ip6tables -h' or > > > 'ip6tables --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in -m physdev --physdev-in vnet0 -g FI-vnet0' failed: > > > ip6tables v1.4.21: goto 'FI-vnet0' is not a chain#012#012Try > > > `ip6tables -h' or 'ip6tables --help' for more information. Jan 21 > > > 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -D libvirt-host-in -m physdev > > > --physdev-in vnet0 -g HI-vnet0' failed: ip6tables v1.4.21: goto > > > 'HI-vnet0' is not a chain#012#012Try `ip6tables -h' or 'ip6tables > > > --help' for more information. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -D libvirt-in-post -m physdev --physdev-in vnet0 -j ACCEPT' > > > failed: ip6tables: Bad rule (does a matching rule exist in that > > > chain?). Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -F FO-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -X FO-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -F FI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ip6tables -w2 -w -X FI-vnet0' failed: > > > ip6tables: No chain/target/match by that name. Jan 21 14:10:07 > > > HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ip6tables -w2 -w -F HI-vnet0' failed: ip6tables: No > > > chain/target/match by that name. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ip6tables -w2 > > > -w -X HI-vnet0' failed: ip6tables: No chain/target/match by that > > > name. Jan 21 14:10:07 HCI01 firewalld[24040]: WARNING: > > > COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -D > > > POSTROUTING -o vnet0 -j libvirt-O-vnet0' failed: Illegal target > > > name 'libvirt-O-vnet0'. Jan 21 14:10:07 HCI01 firewalld[24040]: > > > WARNING: COMMAND_FAILED: '/usr/sbin/ebtables --concurrent -t nat -L > > > libvirt-O-vnet0' failed: Chain 'libvirt-O-vnet0' doesn't exist. Jan > > > 21 14:10:07 HCI01 firewalld[24040]: WARNING: COMMAND_FAILED: > > > '/usr/sbin/ebtables --concurrent -t nat -F libvirt-O-vnet0' failed: > > > Chain 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 > > > firewalld[24040]: WARNING: COMMAND_FAILED: '/usr/sbin/ebtables > > > --concurrent -t nat -X libvirt-O-vnet0' failed: Chain > > > 'libvirt-O-vnet0' doesn't exist. Jan 21 14:10:07 HCI01 vdsm[3650]: > > > WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.ovirt-guest-agent.0 > > > already removed Jan 21 14:10:07 HCI01 vdsm[3650]: WARN Attempting > > > to remove a non existing network: > > > ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 14:10:07 > > > HCI01 vdsm[3650]: WARN Attempting to remove a non existing net > > > user: ovirtmgmt/ea1b312c-a462-45a9-ab75-78008bc4c9c9 Jan 21 > > > 14:10:07 HCI01 vdsm[3650]: WARN > > > File: > /var/lib/libvirt/qemu/channels/ea1b312c-a462-45a9-ab75-78008bc4c9c9.org.qemu.guest_agent.0 > > > already removed > > > > > > any ideas on that? > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > > > To unsubscribe send an email to users-leave(a)ovirt.org > > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ List > > > Archives: > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMMX5CY6VHFWW… > > > >

2 1

lvm problem
by Nyika Csaba 24 Jan '19

24 Jan '19

Hi all, I have an Ovirt 4.2.8 cluster. Nodes are 4.2 ovirt nodes and the volumes (5) attached to nodes by FC. 2 weeks ago i made a small vm (centos 7 based) for me to test (name A). After the test i dropped a vm. Next day a made an another vm (named B) to the developes and tired to add a new disk to the vm (B). Than a original volume group (vg) of the vm (B) missed and i got back the yesterday dropped vm`s (A) vg! I tired to restart a vm, but the vm never started again. I dropped this vm (B) too, and tired to add a new disk an older running vm (C) too, but a volume group changed to that vm`s vg what i dropped before (B). I checked this „error” and i got it ,then i delete or move disks from the end of the FC volume. Have sombody ever seen error like this? Thanks, csaba Ps: in this cluster a managed 120 productive vm, so….

1 0

Lvm problem
by csabany＠freemail.hu 24 Jan '19

24 Jan '19

Hi all, I have an Ovirt 4.2.8 cluster. Nodes are 4.2 ovirt nodes and the volumes (5) attached to nodes by FC. 2 weeks ago i made a small vm (centos 7 based) for me to test (name A). After the test i dropped a vm. Next day a made an another vm (named B) to the developes and tired to add a new disk to the vm (B). Than a original volume group (vg) of the vm (B) missed and i got back the yesterday dropped vm`s (A) vg! I tired to restart a vm, but the vm never started again. I dropped this vm (B) too, and tired to add a new disk an older running vm (C) too, but a volume group changed to that vm`s vg what i dropped before (B). I checked this „error” and i got it ,then i delete or move disks from the end of the FC volume. Have sombody ever seen error like this? Thanks, csaba Ps: in this cluster a managed 120 productive vm, so….

1 0

latest pycurl 7.43 brokes ovirtsdk4
by Nathanaël Blanchet 24 Jan '19

24 Jan '19

Hi all, If anyone uses latest pycurl 7.43 provided by pip or ansible tower/awx, any ovirtsdk4 calling will issue with the log: The full traceback is: WARNING: The below traceback may *not* be related to the actual failure. File "/tmp/ansible_ovirt_auth_payload_L1HK9E/__main__.py", line 202, in <module> import ovirtsdk4 as sdk File "/opt/awx/embedded/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 22, in <module> import pycurl fatal: [localhost]: FAILED! => { "changed": false, "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "state": "present", "timeout": 0, "token": null, "url": "https://acore.v100.abes.fr/ovirt-engine/api", "username": "admin@internal" } }, "msg": "ovirtsdk4 version 4.2.4 or higher is required for this module" } The only way is to set the version of pycurl with pip install -U "pycurl == 7.19.0" (Before this, in tower/awx, you should create venv) -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 4

oVirt 4.2.8 CPU Compatibility
by Stefano Danzi 24 Jan '19

24 Jan '19

Hello! I'm running oVirt 4.2.7.5-1.el7 on 3 hosts cluster. Cluster CPU Type is "AMD Opteron G3". On default cluster I can see the warning: "Warning: The CPU type 'AMD Opteron G3' will not be supported in the next minor version update'" Is it still supported in version 4.2.8? I can't see references in documentation or changelog.

5 5