- Users - oVirt List Archives

Disk move succeed but didn't move content
by Juan Pablo Lorier 03 Dec '19

03 Dec '19

Hi, I've a fresh new install of ovirt 4.3 and tried to import an gluster vmstore. I managed to import via NFS the former data domain. The problem is that when I moved the disks of the vms to the new ISCSI data domain, I got a warning that sparse disk type will be converted to qcow2 disks, and after accepting, the disks were moved with no error. The problem is that the disks now figure as <1Gb size instead of the original size and thus, the vms fail to start. Is there any way to recover those disks? I have no backup of the vms :-( Regards

3 4

Current status of Ceph support in oVirt (2019)?
by victorhooi＠yahoo.com 03 Dec '19

03 Dec '19

Hi, I currently have a 3-node HA cluster running Proxmox (with integrated Ceph). oVirt looks pretty neat, however, and I'm excited to check it out. One of the things I love about Proxmox is the integrated Ceph support. I saw on the mailing lists that there is some talk of Ceph support earlier, but it was via OpenStack/Cinder. What exactly does this mean? 1. Does this require you to install OpenStack, or will a vanilla Ceph installation work? 2. Is it possible to deploy Ceph on the same nodes that run oVirt? (i.e. is a 3-node oVirt + Ceph cluster possible?) 3. Is there any monitoring/management of Ceph from within oVirt? (Guessing no?) 4. Are all the normal VM features working yet, or is this planned? 5. Is making Ceph a first-class citizen (like Gluster) on oVirt on the roadmap? Thanks, Victor https://www.reddit.com/r/ovirt/comments/ci38zp/ceph_rbd_support_in_ovirt_fo…

3 3

Windows VirtIO drivers
by Vijay Sachdeva 03 Dec '19

03 Dec '19

Dear Team, How can we install virtIO windows drivers to Windows 2016. As of now I tried to attach floppy drive with virtio-win.vfd image but while installing drivers didn’t get loaded. Please guide or let me know the proper way to install drivers. Vijay Sachdeva

1 0

oVirt nodes not responding
by Tim Herrmann 03 Dec '19

03 Dec '19

Hi everyone, we have an oVirt-Cluster with 5 nodes and 3 of them provide the storage with GlusterFS and replica 3. The cluster is running 87 VMs and has 9TB storage where 4TB is in use. The version of the oVirt-Engine is 4.1.8.2 and GlusterFS is 3.8.15. The servers are running in a HP bladecenter and are connected with 10GBit to each other. Actually we have some problems that all ovirt nodes periodically won't respond in the cluster with the following error messages in the oVirt webinterface: VDSM glustervirt05 command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues Host glustervirt05 is not responding. It will stay in Connecting state for a grace period of 68 seconds and after that an attempt to fence the host will be issued. Host glustervirt05 does not enforce SELinux. Current status: PERMISSIVE Executing power management status on Host glustervirt05 using Proxy Host glustervirt02 and Fence Agent ilo4:xxx.xxx.xxx.xxx. Manually synced the storage devices from host glustervirt05 Status of host glustervirt05 was set to Up. In the vdsm logfile I can find the following message: 2019-11-26 11:18:22,909+0100 WARN (vdsm.Scheduler) [Executor] Worker blocked: <Worker name=jsonrpc/7 running <Task <JsonRpcTask {'params': {u'volumeName': u'data'}, 'jsonrpc': '2.0', 'method': u'GlusterVolume.healInfo', 'id': u'2e86ed2c- 3e79-42c1-a7e4-c09bfbfc7794'} at 0x7fb938373190> timeout=60, duration=180 at 0x316a6d0> task#=2859802 at 0x1b70dd0> (executor:351) And I figured out, that the gluster heal info command takes very long: [root@glustervirt01 ~]# time gluster volume heal data info Brick glustervirt01:/gluster/data/brick1 Status: Connected Number of entries: 0 Brick glustervirt02:/gluster/data/brick1 Status: Connected Number of entries: 0 Brick glustervirt03:/gluster/data/brick2 Status: Connected Number of entries: 0 real 3m3.626s user 0m0.593s sys 0m0.559s A strange behavier is also that there is one virtual machine (a postgresql database) which stops running unexpectedly every one or two days ... The only thing that has been changed on the vm in the least past was a resize of the disk. VM replication-zabbix is down with error. Exit message: Lost connection with qemu process. And when we add or delete a larger disk with approximately 100GB in glusterfs, the glusterfs cluster freaks out won't respond anymore. This also results in paused VMs ... Has anyone an idea what could cause such problems?

2 1

Re: Scenario: Ovirt-engine on hardware and recovery
by Strahil 03 Dec '19

03 Dec '19

As this is not a VM, you won't have to worry about putting 1 host in maintenance. I make backups lile this: engine-backup --mode=backup --scope=all --file=/root/engine-bkp-empty-ovirt1-ver4.3.7-rc4--2019-11-30 --log=/var/log/engine-backup.log I'm specifying the host that will be used for restore, which is needed when the engine is VM. In your bare-metal case - you just need to recover the OS/harfware and restore from backup. Best Regards, Strahil NikolovOn Dec 3, 2019 04:36, rwebb(a)ropeguru.com wrote: > > So thinking about my setup, I am thinking through different failure scenarios. > > So lets say I have a small physical server with 8 cores and 16GB RAM and I install Centos 7 and ovirt-engine on bare metal. This would also be the same scenario is the engine were on a VM. > > I run into a major hardware issue and completely lose the engine. How does one recover the cluster setup and not have to start from scratch by having to rebuild all the nodes? Can the engine just be rebuilt and the ovirt nodes be imported? > > This scenario is based on the nodes being built from the ovirt node iso. > _______________________________________________ > 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/XBFYDGZNCT4VL…

1 0

Re: host failed to attach one of the storage domains attached to it
by Strahil 03 Dec '19

03 Dec '19

Hi Daniel, The hosts go to unresponsive mode as one of the gluster volumes cannot be mounted. Verify that all host can mount (over /mnt) all gluster volumes. If they do, just set the hosts into maintenance and then activate them. Best Regards, Strahil NikolovOn Dec 2, 2019 12:03, Daniel Menzel <daniel.menzel(a)menzel-it.net> wrote: > > Dear all, > > after a GlusterFS reboot of two servers out of three (and thus a loss of quorum) by an admin we've got strange problems: > > The hosted engine and one export work perfectly fine. (Same three servers!) > Another export (main one) seems to be fine within GlusterFS itself. But: When we activate this domain most of the hosts go into "non operational" with the subject's error message. As soon as we deactivate this domain all those hosts come back online. Strange thing: The GlusterFS export seems to be mounted on the SPM. > > Does anyone know what could have happened and how to fix that? > > Kind regards > Daniel

1 0

Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Strahil 03 Dec '19

03 Dec '19

Hi Jiffin, Thanks for the info. As I'm now on Gluster v7 , I hope it won't happen again. It's nice to know it got fixed. Best Regards, Strahil NikolovOn Dec 2, 2019 11:32, Jiffin Thottan <jthottan(a)redhat.com> wrote: > > Hi Krutika, > > Apparently, in context acl info got corrupted see brick logs > > [posix-acl.c:263:posix_acl_log_permit_denied] 0-data_fast-access-control: > client: > CTX_ID:dae9ffad-6acd-4a43-9372-229a3018fde9-GRAPH_ID:0-PID:11468-HOST:ovirt2.localdomain-PC_NAME:data_fast-client-0-RECON_NO:-0, > gfid: be318638-e8a0-4c6d-977d-7a937aa84806, > req(uid:107,gid:107,perm:1,ngrps:4), > ctx(uid:0,gid:0,in-groups:0,perm:000,updated-fop:INVALID, acl:-) > [Permission denied] > > which resulted in the situation. There was one bug similar was reported https://bugzilla.redhat.com/show_bug.cgi?id=1668286 and > > it got fixed in 6.6 release IMO https://review.gluster.org/#/c/glusterfs/+/23233/. But here he mentioned he saw the issue when > > he upgraded from 6.5 to 6.6 > > One way to workaround is to perform a dummy setfacl(preferably using root) on the corrupted files which will forcefully fetch the acl > > info again from backend and update the context. Another approach to restart brick process(kill and vol start force) > > Regards, > Jiffin > > ----- Original Message ----- > From: "Krutika Dhananjay" <kdhananj(a)redhat.com> > To: "Strahil Nikolov" <hunter86_bg(a)yahoo.com>, "Jiffin Thottan" <jthottan(a)redhat.com>, "raghavendra talur" <rtalur(a)redhat.com> > Cc: "Nir Soffer" <nsoffer(a)redhat.com>, "Rafi Kavungal Chundattu Parambil" <rkavunga(a)redhat.com>, "users" <users(a)ovirt.org>, "gluster-user" <gluster-users(a)gluster.org> > Sent: Monday, December 2, 2019 11:48:22 AM > Subject: Re: [ovirt-users] Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing > > Sorry about the late response. > > I looked at the logs. These errors are originating from posix-acl > translator - > > > > *[2019-11-17 07:55:47.090065] E [MSGID: 115050] > [server-rpc-fops_v2.c:158:server4_lookup_cbk] 0-data_fast-server: 162496: > LOOKUP /.shard/5985adcb-0f4d-4317-8a26-1652973a2350.6 > (be318638-e8a0-4c6d-977d-7a937aa84806/5985adcb-0f4d-4317-8a26-1652973a2350.6), > client: > CTX_ID:8bff2d95-4629-45cb-a7bf-2412e48896bc-GRAPH_ID:0-PID:13394-HOST:ovirt1.localdomain-PC_NAME:data_fast-client-0-RECON_NO:-0, > error-xlator: data_fast-access-control [Permission denied][2019-11-17 > 07:55:47.090174] I [MSGID: 139001] > [posix-acl.c:263:posix_acl_log_permit_denied] 0-data_fast-access-control: > client: > CTX_ID:8bff2d95-4629-45cb-a7bf-2412e48896bc-GRAPH_ID:0-PID:13394-HOST:ovirt1.localdomain-PC_NAME:data_fast-client-0-RECON_NO:-0, > gfid: be318638-e8a0-4c6d-977d-7a937aa84806, > req(uid:36,gid:36,perm:1,ngrps:3), > ctx(uid:0,gid:0,in-groups:0,perm:000,updated-fop:INVALID, acl:-) > [Permission denied][2019-11-17 07:55:47.090209] E [MSGID: 115050] > [server-rpc-fops_v2.c:158:server4_lookup_cbk] 0-data_fast-server: 162497: > LOOKUP /.shard/5985adcb-0f4d-4317-8a26-1652973a2350.7 > (be318638-e8a0-4c6d-977d-7a937aa84806/5985adcb-0f4d-4317-8a26-1652973a2350.7), > client: > CTX_ID:8bff2d95-4629-45cb-a7bf-2412e48896bc-GRAPH_ID:0-PID:13394-HOST:ovirt1.localdomain-PC_NAME:data_fast-client-0-RECON_NO:-0, > error-xlator: data_fast-access-control [Permission denied][2019-11-17 > 07:55:47.090299] I [MSGID: 139001] > [posix-acl.c:263:posix_acl_log_permit_denied] 0-data_fast-access-control: > client: > CTX_ID:8bff2d95-4629-45cb-a7bf-2412e48896bc-GRAPH_ID:0-PID:13394-HOST:ovirt1.localdomain-PC_NAME:data_fast-client-0-RECON_NO:-0, > gfid: be318638-e8a0-4c6d-977d-7a937aa84806, > req(uid:36,gid:36,perm:1,ngrps:3), > ctx(uid:0,gid:0,in-groups:0,perm:000,updated-fop:INVALID, acl:-) > [Permission denied]* > > Jiffin/Raghavendra Talur, > Can you help? > > -Krutika > > On Wed, Nov 27, 2019 at 2:11 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> > wrote: > > > Hi Nir,All, > > > > it seems that 4.3.7 RC3 (and even RC4) are not the problem here(attached > > screenshot of oVirt running on v7 gluster). > > It seems strange that both my serious issues with oVirt are related to > > gluster issue (1st gluster v3 to v5 migration and now this one). > > > > I have just updated to gluster v7.0 (Centos 7 repos), and rebooted all > > nodes. > > Now both Engine and all my VMs are back online - so if you hit issues with > > 6.6 , you should give a try to 7.0 (and even 7.1 is coming soon) before > > deciding to wipe everything. > > > > @Krutika, > > > > I guess you will ask for the logs, so let's switch to gluster-users about > > this one ? > > > > Best Regards, > > Strahil Nikolov > > > > В понеделник, 25 ноември 2019 г., 16:45:48 ч. Гринуич-5, Strahil Nikolov < > > hunter86_bg(a)yahoo.com> написа: > > > > > > Hi Krutika, > > > > I have enabled TRACE log level for the volume data_fast, > > > > but the issue is not much clear: > > FUSE reports: > > > > [2019-11-25 21:31:53.478130] I [MSGID: 133022] > > [shard.c:3674:shard_delete_shards] 0-data_fast-shard: Deleted shards of > > gfid=6d9ed2e5-d4f2-4749-839b-2f1 > > 3a68ed472 from backend > > [2019-11-25 21:32:43.564694] W [MSGID: 114031] > > [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-0: > > remote operation failed. Path:

1 0

Re: NFS Storage Domain on OpenMediaVault
by Amit Bawer 03 Dec '19

03 Dec '19

On Mon, Dec 2, 2019 at 7:21 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > Thanks for the response. > > As it turned out, the issue was on the export where I had to remove > subtree_check and added no_root_squash and it started working. > > Being new to the setup, I am still trying to work through some config > issues and deciding if I want to continue. The main thing I am looking for > is good HA and failover capability. Been using Proxmox VE and I like the > admin of it, but failover still needs work. Simple things like auto > migration when rebooting a host does not exist and is something I need. > for RHEV, you can check the Cluster scheduling policies https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… > Robert > ------------------------------ > *From:* Strahil Nikolov <hunter86_bg(a)yahoo.com> > *Sent:* Sunday, December 1, 2019 2:54 PM > *To:* users(a)ovirt.org <users(a)ovirt.org>; Robert Webb <rwebb(a)ropeguru.com> > *Subject:* Re: [ovirt-users] NFS Storage Domain on OpenMediaVault > > Does sanlock user has rights on the ...../dom_md/ids ? > > Check the sanlock.service for issues. > journalctl -u sanlock.service > > Best Regards, > Strahil Nikolov > > В неделя, 1 декември 2019 г., 17:22:21 ч. Гринуич+2, rwebb(a)ropeguru.com < > rwebb(a)ropeguru.com> написа: > > > I have a clean install with openmediavault as backend NFS and cannot get > it to work. Keep getting permission errors even though I created a vdsm > user and kvm group; and they are the owners of the directory on OMV with > full permissions. > > The directory gets created on the NFS side for the host, but then get the > permission error and is removed form the host but the directory structure > is left on the NFS server. > > Logs: > > From the engine: > > Error while executing action New NFS Storage Domain: Unexpected exception > > From the oVirt node log: > > 2019-11-29 10:03:02 136998 [30025]: open error -13 EACCES: no permission > to open /rhev/data-center/mnt/192.168.1.56: > _export_Datastore-oVirt/f38b19e4-8060-4467-860b-09cf606ccc15/dom_md/ids > 2019-11-29 10:03:02 136998 [30025]: check that daemon user sanlock 179 > group sanlock 179 has access to disk or file. > > File system on Openmediavault: > > drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 . > drwxr-xr-x 9 root root 4096 Nov 27 20:56 .. > drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 > f38b19e4-8060-4467-860b-09cf606ccc15 > > drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 . > drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 .. > drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 dom_md > drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 images > > drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 . > drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 .. > -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 ids > -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 inbox > -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 leases > -rw-rw-r--+ 1 vdsm kvm 343 Nov 29 10:03 metadata > -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 outbox > -rw-rw----+ 1 vdsm kvm 1302528 Nov 29 10:03 xleases > _______________________________________________ > 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/ILKNT57F6VUHE… > _______________________________________________ > 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/KH2H2V254Z7T7… >

2 1

NFS Storage Domain on OpenMediaVault
by rwebb＠ropeguru.com 02 Dec '19

02 Dec '19

I have a clean install with openmediavault as backend NFS and cannot get it to work. Keep getting permission errors even though I created a vdsm user and kvm group; and they are the owners of the directory on OMV with full permissions. The directory gets created on the NFS side for the host, but then get the permission error and is removed form the host but the directory structure is left on the NFS server. Logs: From the engine: Error while executing action New NFS Storage Domain: Unexpected exception From the oVirt node log: 2019-11-29 10:03:02 136998 [30025]: open error -13 EACCES: no permission to open /rhev/data-center/mnt/192.168.1.56:_export_Datastore-oVirt/f38b19e4-8060-4467-860b-09cf606ccc15/dom_md/ids 2019-11-29 10:03:02 136998 [30025]: check that daemon user sanlock 179 group sanlock 179 has access to disk or file. File system on Openmediavault: drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 . drwxr-xr-x 9 root root 4096 Nov 27 20:56 .. drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 f38b19e4-8060-4467-860b-09cf606ccc15 drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 . drwxrwsrwx+ 3 vdsm kvm 4096 Nov 29 10:03 .. drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 dom_md drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 images drwxrwsr-x+ 2 vdsm kvm 4096 Nov 29 10:03 . drwxrwsr-x+ 4 vdsm kvm 4096 Nov 29 10:03 .. -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 ids -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 inbox -rw-rw----+ 1 vdsm kvm 0 Nov 29 10:03 leases -rw-rw-r--+ 1 vdsm kvm 343 Nov 29 10:03 metadata -rw-rw----+ 1 vdsm kvm 16777216 Nov 29 10:03 outbox -rw-rw----+ 1 vdsm kvm 1302528 Nov 29 10:03 xleases

4 3

host failed to attach one of the storage domains attached to it
by Daniel Menzel 02 Dec '19

02 Dec '19

Dear all, after a GlusterFS reboot of two servers out of three (and thus a loss of quorum) by an admin we've got strange problems: 1. The hosted engine and one export work perfectly fine. (Same three servers!) 2. Another export (main one) seems to be fine within GlusterFS itself. But: When we activate this domain most of the hosts go into "non operational" with the subject's error message. As soon as we deactivate this domain all those hosts come back online. Strange thing: The GlusterFS export seems to be mounted on the SPM. Does anyone know what could have happened and how to fix that? Kind regards Daniel

1 0

Overt Networking VM not pinging
by Vijay Sachdeva 02 Dec '19

02 Dec '19

Dear Community, I have installed Ovirt Engine 4.3 and Ovirt Node 4.3. Node got successfully added to engine and setup host network also done. When trying to ping host using “ovirtmgmt” as vNic profile for a VM, it is not even able to ping it’s host or any other machine on that same network. Also added a VLAN network which is passed via same uplink of Node interface where “Ovirtmgmt” is passed, that is also not working. Although this vnet is vnic type is VirtIO and state shows “UNKNOWN”, would this be a problem? Any help would be highly appreciated. Thanks Vijay Sachdeva Senior Manager – Service Delivery IndiQus Technologies O +91 11 4055 1411 | M +91 8826699409 www.indiqus.com

3 7

hyperconverged single node with SSD cache fails gluster creation
by thomas＠hoberg.net 01 Dec '19

01 Dec '19

I am seeing more success than failures at creating single and triple node hyperconverged setups after some weeks of experimentation so I am branching out to additional features: In this case the ability to use SSDs as cache media for hard disks. I tried first with a single node that combined caching and compression and that fails during the creation of LVMs. I tried again without the VDO compression, but actually the results where identical whilst VDO compression but without the LV cache worked ok. I tried various combinations, using less space etc., but the results are always the same and unfortunately rather cryptic (substituted the physical disk label with {disklabel}): TASK [gluster.infra/roles/backend_setup : Extend volume group] ***************** failed: [{hostname}] (item={u'vgname': u'gluster_vg_{disklabel}p1', u'cachethinpoolname': u'gluster_thinpool_gluster_vg_{disklabel}p1', u'cachelvname': u'cachelv_gluster_thinpool_gluster_vg_{disklabel}p1', u'cachedisk': u'/dev/sda4', u'cachemetalvname': u'cache_gluster_thinpool_gluster_vg_{disklabel}p1', u'cachemode': u'writeback', u'cachemetalvsize': u'70G', u'cachelvsize': u'630G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Physical volume \"/dev/mapper/vdo_{disklabel}p1\" still in use\n", "item": {"cachedisk": "/dev/sda4", "cachelvname": "cachelv_gluster_thinpool_gluster_vg_{disklabel}p1", "cachelvsize": "630G", "cachemetalvname": "cache_gluster_thinpool_gluster_vg_{disklabel}p1", "cachemetalvsize": "70G", "cachemode": "writeback", "cachethinpoolname": "gluster_thinpool_gluster_vg_{disklabel}p1", "vgname": "gluster_vg_{disklabel}p1"}, "msg": "Unable to reduce gluster_vg_{disklabel}p1 by /dev/dm-15.", "rc": 5} somewhere within that I see something that points to a race condition ("still in use"). Unfortunately I have not been able to pinpoint the raw logs which are used at that stage and I wasn't able to obtain more info. At this point quite a bit of storage setup is already done, so rolling back for a clean new attempt, can be a bit complicated, with reboots to reconcile the kernel with data on disk. I don't actually believe it's related to single node and I'd be quite happy to move the creation of the SSD cache to a later stage, but in a VDO setup, this looks slightly complex to someone without intimate knowledge of LVS-with-cache-and-perhaps-thin/VDO/Gluster all thrown into one. Needless the feature set (SSD caching & compressed-dedup) sounds terribly attractive but when things don't just work, it's more terrifying.

5 7

Moving HostedEngine
by Joseph Goldman 28 Nov '19

28 Nov '19

Hi List, In one of my installs, I set up the first storage domain (and where the HostedEngine is) on a bigger NFS NAS - since then I have created a Gluster volume that spans the 3 hosts and I'm putting a few VM's in there for higher reliability (as SAN is single point of failure) namely I'd like to put HostedEngine in there so it stays up no matter what and can help report if issues occur (network issue to NAS, NAS dies etc etc) Looking through other posts and documentation, there's no real way to move the HostedEngine storage, is this correct? The solution I've seen is to backup the hosted engine DB, blow it away, and re-deploy it from the .backup file configuring it to the new storage domain in the deploy script - is this the only process? How likely is this to fail? Is it likely that all VM's and settings will be picked straight back up and continue to operate like normal? I dont have a test setup to play around with atm so just trying to gauge confidence in such a solution. Thanks, Joe

3 3

Migrate VM from oVirt to oVirt
by adrianquintero＠gmail.com 28 Nov '19

28 Nov '19

Hello, What would be the procedure to migrate a VM from oVirt to oVirt? Migrate from oVirt 4.2 running on Site A to oVirt 4.3 Site B. thanks!

5 7

Re: HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Strahil 28 Nov '19

28 Nov '19

The HostedEngine does it automatically, but the option that defines the OVF refresh interval is not accurate. Just power it up without that option (cluster in maintenance) and keep it running for a day. On the next day power it off and try to power it up via hosted-engine --vm-start. Best Regards, Strahil NikolovOn Nov 28, 2019 11:54, Ralf Schenk <rs(a)databay.de> wrote: > > Hello, > > I did something like that via "virsh edit HostedEngine". > > But how is the change written back to the shared storage ("hosted_storage" so it stays permanent for HA Engine ? > > I was able to boot up HostedEngine manually via virsh start after removing the required flag from XML (I first added a user to sasldb in /etc/libvirt/passwd.db to be able to log into libvirt). > > Bye > > > Am 28.11.2019 um 05:51 schrieb Strahil: > > Hi Ralf, > When the deployment fail - you can dump the xml from virsh , edit it, undefine the current HostedEngine and define your modified HostedEngine 's xml. > > Once you do that, you can try to start the > VM. > > Good luck. > > Best Regards, > Strahil Nikolov > > On Nov 27, 2019 18:28, Ralf Schenk <rs(a)databay.de> wrote: >> >> Hello, >> >> This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. >> >> At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. >> >> QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". >> >> Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. >> >> From VM XML: >> >> <cpu mode='custom' match='exact' check='partial'> >> <model fallback='allow'>EPYC</model> >> <topology sockets='16' cores='4' threads='1'/> >> <feature policy='require' name='ibpb'/> >> <feature policy='require' name='virt-ssbd'/> >> >> from cat /proc/cpuinfo: >> >> processor : 47 >> vendor_id : AuthenticAMD >> cpu family : 23 >> model : 49 >> model name : AMD EPYC 7402P 24-Core Processor >> stepping : 0 >> microcode : 0x830101c >> cpu MHz : 2800.000 >> cache size : 512 KB >> physical id : 0 >> siblings : 48 >> core id : 30 >> cpu cores : 24 >> api

1 0

Re: spice connection error
by Strahil 28 Nov '19

28 Nov '19

Check on host 'node3' in the Network configuration if you have a network out of sync or any clues about the error . Best Regards, Strahil NikolovOn Nov 28, 2019 11:44, Kim Kargaard <Kim.Kargaard(a)noroff.no> wrote: > > Hi, > > I am getting the attached error when trying to move the Display from the one network to the other within the cluster. I can't see any place to set an IP for the vnic that I want to set as the display network. > > Any thoughts? > > Kim > > On 28/11/2019, 06:41, "Strahil" <hunter86_bg(a)yahoo.com> wrote: > > As far as I know , the engine plays a role as a proxy during the establishment of the connection. > Check that you can reach both engine and the host from your system. > > For the same reason, I use noVNC - as you just need a single port to the engine in addition to the rest of the settings. > > Best Regards, > Strahil NikolovOn Nov 27, 2019 11:27, kim.kargaard(a)noroff.no wrote: > > > > Hi, > > > > When trying to connect from a remote network on the spice console to a VM, I get the following error: > > > > (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out > > > > I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: > > > > Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. > > > > I am not sure what this means. Any ideas? > > > > Kind regards > > > > Kim > > _______________________________________________ > > 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/6YEI3I4NCAHQO… > >

1 0

VDSM Errors see below
by rob.downer＠orbitalsystems.co.uk 28 Nov '19

28 Nov '19

I have removed all deployment of the hosted engine by running the following commands. ovirt-hosted-engine-cleanup vdsm-tool configure --force systemctl restart libvirtd systemctl restart vdsm on my hosts I have the following ovirt 1 is the host I ran the hosted engine setup. I have set the Gluster network to use the same subnet and set up forward and reverse DNS for the Gluster port network NIC's I had this working using a separate subnet but thought to try it on the same subnet to avoid any issues that may have occurred while using a separate network subnet. the main Host IP address is still showing in Unamanaged Connections on Ovirt 1 .. is this anything to be concerned about after running the commands above... I have restarted all machines. All come back with these VDSM errors... Node 1 [root@ovirt1 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2019-11-28 13:29:40 UTC; 37min ago Process: 31178 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS) Process: 30721 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 /dev/null -2 /dev/null /usr/share/vdsm/vdsmd (code=exited, status=0/SUCCESS) Main PID: 30721 (code=exited, status=0/SUCCESS) Nov 26 22:42:49 ovirt1.kvm.private vdsm[30721]: WARN MOM not available, KSM stats will be missing. Nov 26 22:42:49 ovirt1.kvm.private vdsm[30721]: WARN Not ready yet, ignoring event '|virt|VM_status|871ce9d5-417a-4278-8446-28b681760c1b' args={'871ce9d5-417a-4278-8446-28b681760c1b': {'status': 'Poweri... Nov 28 13:28:43 ovirt1.kvm.private vdsm[30721]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:29:26 ovirt1.kvm.private vdsm[30721]: WARN File: /var/lib/libvirt/qemu/channels/871ce9d5-417a-4278-8446-28b681760c1b.com.redhat.rhevm.vdsm already removed Nov 28 13:29:26 ovirt1.kvm.private vdsm[30721]: WARN File: /var/lib/libvirt/qemu/channel/target/domain-1-HostedEngineLocal/org.qemu.guest_agent.0 already removed Nov 28 13:29:39 ovirt1.kvm.private vdsm[30721]: WARN MOM not available. Nov 28 13:29:39 ovirt1.kvm.private vdsm[30721]: WARN MOM not available, KSM stats will be missing. Nov 28 13:29:39 ovirt1.kvm.private systemd[1]: Stopping Virtual Desktop Server Manager... Nov 28 13:29:39 ovirt1.kvm.private vdsmd_init_common.sh[31178]: vdsm: Running run_final_hooks Nov 28 13:29:40 ovirt1.kvm.private systemd[1]: Stopped Virtual Desktop Server Manager. Hint: Some lines were ellipsized, use -l to show in full. [root@ovirt1 ~]# nodectl check Status: WARN Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... BAD NODE 2 [root@ovirt2 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-28 13:57:30 UTC; 1min 13s ago Process: 3626 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 5418 (vdsmd) Tasks: 38 CGroup: /system.slice/vdsmd.service └─5418 /usr/bin/python2 /usr/share/vdsm/vdsmd Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: libvirt: Network Filter Driver error : Network filter not found: no nwfilter with matching name 'vdsm-no-mac-spoofing' Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running dummybr Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running tune_system Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running test_space Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running test_lo Nov 28 13:57:30 ovirt2.kvm.private systemd[1]: Started Virtual Desktop Server Manager. Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN File: /var/run/vdsm/trackedInterfaces/eno1 already removed Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN MOM not available. Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN MOM not available, KSM stats will be missing. [root@ovirt2 ~]# nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK [root@ovirt2 ~]# Node 3 [root@ovirt3 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-28 13:57:08 UTC; 12min ago Process: 2849 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 3220 (vdsmd) Tasks: 38 CGroup: /system.slice/vdsmd.service └─3220 /usr/bin/python2 /usr/share/vdsm/vdsmd Nov 28 13:57:07 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running nwfilter Nov 28 13:57:07 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running dummybr Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running tune_system Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running test_space Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running test_lo Nov 28 13:57:08 ovirt3.kvm.private systemd[1]: Started Virtual Desktop Server Manager. Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN File: /var/run/vdsm/trackedInterfaces/eno1 already removed Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN MOM not available. Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN MOM not available, KSM stats will be missing. [root@ovirt3 ~]# nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK [root@ovirt3 ~]#

1 0

Re: HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Strahil 28 Nov '19

28 Nov '19

Hi Ralf, When the deployment fail - you can dump the xml from virsh , edit it, undefine the current HostedEngine and define your modified HostedEngine 's xml. Once you do that, you can try to start the VM. Good luck. Best Regards, Strahil NikolovOn Nov 27, 2019 18:28, Ralf Schenk <rs(a)databay.de> wrote: > > Hello, > > This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. > > At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. > > QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". > > Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. > > From VM XML: > > <cpu mode='custom' match='exact' check='partial'> > <model fallback='allow'>EPYC</model> > <topology sockets='16' cores='4' threads='1'/> > <feature policy='require' name='ibpb'/> > <feature policy='require' name='virt-ssbd'/> > > from cat /proc/cpuinfo: > > processor : 47 > vendor_id : AuthenticAMD > cpu family : 23 > model : 49 > model name : AMD EPYC 7402P 24-Core Processor > stepping : 0 > microcode : 0x830101c > cpu MHz : 2800.000 > cache size : 512 KB > physical id : 0 > siblings : 48 > core id : 30 > cpu cores : 24 > apicid : 61 > initial apicid : 61 > fpu : yes > fpu_exception : yes > cpuid level : 16 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca > bogomips : 5600.12 > TLB size : 3072 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 43 bits physical, 48 bits virtual > power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] > > Any solution/workaround available ?

2 1

Re: Moving HostedEngine
by Strahil 28 Nov '19

28 Nov '19

It is highly 'super duper' not recommended to do that. Also, consider using thinLVM (requirement for gluster snapshots) for a brick of the separate gluster volume. I'm using the 3rd partirion of my OS SSD to host my gluster's volume and I have no issues so far. Best Regards, Strahil NikolovOn Nov 28, 2019 01:05, Joseph Goldman <joseph(a)goldman.id.au> wrote: > > So I can't host OTHER VM's on this gluster volume? If its already a running GLuser for other VMs i can't now re-reploy HE in that gluster volume? > > On 2019-11-28 3:27 AM, Alan G wrote: > > I've had to do this a couple of times and always ended up with a working system in the end. > > As a fall back option (although I've never had to use it) I have a backup engine VM running completely outside of oVIrt (ESXi host in my case). Then if the hosted_engine deploy fails for any reason you can restore onto the backup vm as a temp solution while you work through the hosted engine deploy issues. > > A few things that come to mind: - > > * You will need a dedicated gluster volume for hosted_storage and it needs to be replica+arbiter. >> >> * Make sure you put the cluster in global maint mode before performing the engine backup, I recall having issues with the restore when I didn't do that. >> * Migrate all other VMs off the host running Engine before doing the backup. This will be the host you will restore onto. >> >> >> ---- On Wed, 27 Nov 2019 09:46:23 +0000 Joseph Goldman <joseph(a)goldman.id.au> wrote ---- >> >>> Hi List, >>> >>> In one of my installs, I set up the first storage domain (and where >>> the HostedEngine is) on a bigger NFS NAS - since then I have created a >>> Gluster volume that spans the 3 hosts and I'm putting a few VM's in >>> there for higher reliability (as SAN is single point of failure) namely >>> I'd like to put HostedEngine in there so it stays up no matter what and >>> can help report if issues occur (network issue to NAS, NAS dies etc etc) >>> >>> Looking through other posts and documentation, there's no real way to >>> move the HostedEngine storage, is this correct? The solution I've seen >>> is to backup the hosted engine DB, blow it away, and re-deploy it from >>> the .backup file configuring it to the new storage domain in the deploy >>> script - is this the only process? How likely is this to fail? Is it >>> likely that all VM's and settings will be picked straight back up and >>> continue to operate like normal? I dont have a test setup to play around >>> with atm so just trying to gauge confidence in such a solution. >>> >>> Thanks, >>> Joe >>> _______________________________________________ >>> 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:

1 0

Re: Moving HostedEngine
by Strahil 28 Nov '19

28 Nov '19

Hi Joseph, It is mandatory to create a dedicated gluster volume for the HostedEngine. There is a thread which explains why and the risks of not following these guidlines. You can set the volume on thinLVM, so you can snapshot your gluster's volume before patching of the engine (of course you have to shutdown the engine in advance). About the transfer, the safest way is to backup & restore as you are not migrating from 1 type of storage domain to another of same type. Yet, I can't help you with that procedure - as I have never done it. Best Regards, Strahil NikolovOn Nov 27, 2019 11:46, Joseph Goldman <joseph(a)goldman.id.au> wrote: > > Hi List, > > In one of my installs, I set up the first storage domain (and where > the HostedEngine is) on a bigger NFS NAS - since then I have created a > Gluster volume that spans the 3 hosts and I'm putting a few VM's in > there for higher reliability (as SAN is single point of failure) namely > I'd like to put HostedEngine in there so it stays up no matter what and > can help report if issues occur (network issue to NAS, NAS dies etc etc) > > Looking through other posts and documentation, there's no real way to > move the HostedEngine storage, is this correct? The solution I've seen > is to backup the hosted engine DB, blow it away, and re-deploy it from > the .backup file configuring it to the new storage domain in the deploy > script - is this the only process? How likely is this to fail? Is it > likely that all VM's and settings will be picked straight back up and > continue to operate like normal? I dont have a test setup to play around > with atm so just trying to gauge confidence in such a solution. > > Thanks, > Joe > _______________________________________________ > 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/ZTO6Q3UTEDJCD…

1 0

Re: spice connection error
by Strahil 28 Nov '19

28 Nov '19

As far as I know , the engine plays a role as a proxy during the establishment of the connection. Check that you can reach both engine and the host from your system. For the same reason, I use noVNC - as you just need a single port to the engine in addition to the rest of the settings. Best Regards, Strahil NikolovOn Nov 27, 2019 11:27, kim.kargaard(a)noroff.no wrote: > > Hi, > > When trying to connect from a remote network on the spice console to a VM, I get the following error: > > (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out > > I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: > > Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. > > I am not sure what this means. Any ideas? > > Kind regards > > Kim > _______________________________________________ > 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/6YEI3I4NCAHQO…

1 0

Re: Engine deployment last step.... Can anyone help ?
by Strahil 28 Nov '19

28 Nov '19

Hi Rob, Can you check the gluster's volume ? gluster volume status engine gluster volume heal engine info summary Still, this is strange that the firewall is having such differences. Fastest way to sync that node to the settings from the other is to: 1. Backup /etc/firewalld 2. Remove /etc/firewalld 3. Copy /etc/firewalld from another node (either scp or rsync wil do) 4. Restart the firewalld daemon 5. Make a test firewalld reload Best Regards, Strahil NikolovOn Nov 27, 2019 00:09, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: > > Is this the issue ? > > on the deployment host the firewall is active but only on eno2, eno1 appears to have decided to be unmanaged … > > also the deployment host has 17 rules active > > the other two have 7 each… > > > Zone > Interfaces > IP Range > Public > default > eno2 > * > > Unmanaged Interfaces > > > Name > > IP Address > > Sending > > Receiving > > ;vdsmdummy; > > > Inactive > > eno1 > > > > > ovirtmgmt > > 192.168.100.38/24 > > > > virbr0-nic > > >> >> On 25 Nov 2019, at 17:16, Parth Dhanjal <dparth(a)redhat.com> wrote: >> >> Rather than disabling firewalld, >> You can add the ports and restart the firewalld service >> >> # firewall-cmd --add-service=cockpit >> >> # firewall-cmd --add-service=cockpit --permanent >> >> >> >> On Mon, Nov 25, 2019 at 10:43 PM Amit Bawer <abawer(a)redhat.com> wrote: >>> >>> firewalld is running? >>> >>> systemctl disable --now firewalld >>> >>> On Monday, November 25, 2019, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>> >>>> It can’t be DNS, since the engine runs on a separate network anyway ie front end, so why can’t it reach the Volume I wonder >>>> >>>> >>>>> On 25 Nov 2019, at 12:55, Gobinda Das <godas(a)redhat.com> wrote: >>>>> >>>>> There could be two reason >>>>> 1- Your gluster service may not be running. >>>>> 2- In Storage Connection there mentioned <volumename> may not exists >>>>> >>>>> can you please paste the output of "gluster volume status" ? >>>>> >>>>> On Mon, Nov 25, 2019 at 5:03 PM Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>> >>>>>> [ INFO ] skipping: [localhost] >>>>>> [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] >>>>>> [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400. >>>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Failed to fetch Gluster Volume List]\". HTTP response code is 400.”} >>>>>> >>>>>> >>>>>>> On 25 Nov 2019, at 09:16, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>>> >>>>>>> Yes, >>>>>>> >>>>>>> I’ll restart all Nodes after wiping the failed setup of Hosted engine using. >>>>>>> >>>>>>> ovirt-hosted-engine-cleanup >>>>>>> vdsm-tool configure --force >>>>>>> systemctl restart libvirtd >>>>>>> systemctl restart vdsm >>>>>>> >>>>>>> although last time I did >>>>>>> >>>>>>> systemctl restart vdsm >>>>>>> >>>>>>> VDSM did not restart maybe that is OK as Hosted Engine was then de deployed or is that the issue ? >>>>>>> >>>>>>> >>>>>>>> On 25 Nov 2019, at 09:13, Parth Dhanjal <dparth(a)redhat.com> wrote: >>>>>>>> >>>>>>>> Can you please share the error in case it fails again? >>>>>>>> >>>>>>>> On Mon, Nov 25, 2019 at 2:42 PM Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>>>>> >>>>>>>>> hmm, I’’l try again, that failed last time. >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 25 Nov 2019, at 09:08, Parth Dhanjal <dparth(a)redhat.com> wrote: >>>>>>>>>> >>>>>>>>>> Hey! >>>>>>>>>> >>>>>>>>>> For >>>>>>>>>> Storage Connection you can add - <hostname1>:/engine >>>>>>>>>> And for >>>>>>>>>> Mount Options - backup-volfile-servers=<hostname2>:<hostname3> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Nov 25, 2019 at 2:31 PM <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>>>>>>> >>>>>>>>>>> So... >>>>>>>>>>> >>>>>>>>>>> I have got to the last step >>>>>>>>>>> >>>>>>>>>>> 3 Machines with Gluster Storage configured however at the last screen >>>>>>>>>>> >>>>>>>>>>> ....Deploying the Engine to Gluster and the wizard does not auto fill the two fields >>>>>>>>>>> >>>>>>>>>>> Hosted Engine Deployment >>>>>>>>>>> >>>>>>>>>>> Storage Connection >>>>>>>>>>> and >>>>>>>>>>> Mount Options >>>>>>>>>>> >>>>>>>>>>> I also had to expand /tmp as it was not big enough to fit the engine before moving... >>>>>>>>>>> >>>>>>>>>>> What can I do to get the auto complete sorted out ? >>>>>>>>>>> >>>>>>>>>>> I have tried entering ovirt1.kvm.private:/gluster_lv_engine - The Volume name >>>>>>>>>>> and >>>>>>>>>>> ovirt1.kvm.private:/gluster_bricks/engine >>>>>>>>>>> >>>>>>>>>>> Ovirt1 being the actual machine I'm running this on. >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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/NL4HS6MIKWQAG… >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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/LQ5YXX7IVV6ZP… >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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/VHQ3LTES6ABPL… >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> Thanks, >>>>> Gobinda >>>> >>>> >

1 0

HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Ralf Schenk 27 Nov '19

27 Nov '19

Hello, This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. From VM XML: <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>EPYC</model> <topology sockets='16' cores='4' threads='1'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='virt-ssbd'/> from cat /proc/cpuinfo: processor : 47 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7402P 24-Core Processor stepping : 0 microcode : 0x830101c cpu MHz : 2800.000 cache size : 512 KB physical id : 0 siblings : 48 core id : 30 cpu cores : 24 apicid : 61 initial apicid : 61 fpu : yes fpu_exception : yes cpuid level : 16 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca bogomips : 5600.12 TLB size : 3072 4K pages clflush size : 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] Any solution/workaround available ? -- *Ralf Schenk* fon +49 (0) 24 05 / 40 83 70 fax +49 (0) 24 05 / 40 83 759 mail *rs(a)databay.de* <mailto:rs@databay.de> *Databay AG* Jens-Otto-Krag-Straße 11 D-52146 Würselen *www.databay.de* <http://www.databay.de> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Wilhelm Dohmen ------------------------------------------------------------------------

1 0

Certificate of host is invalid
by Jon bae 27 Nov '19

27 Nov '19

Hello everybody, since last update to 4.3.7 I get this error message: Certificate of host *host.name <http://host.name>* is invalid. The certificate doesn't contain valid subject alternative name, please enroll new certificate for the host. Have you an idea of how I can fix that? Regards Jonathan

1 0

spice connection error
by kim.kargaard＠noroff.no 27 Nov '19

27 Nov '19

Hi, When trying to connect from a remote network on the spice console to a VM, I get the following error: (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. I am not sure what this means. Any ideas? Kind regards Kim

1 0