- Users - oVirt List Archives

Migrate self-hosted engine between cluster
by raul.caballero.girol＠gmail.com 12 Apr '19

12 Apr '19

Hello everibody, Iḿ a noob with ovirt and I have a problem. I have deployed a new enviroment with a self-hosted engine. Now, when I am learning about ovirt, I think that my engine should be in another cluster. How I can move my manage from one cluster to other?. Cheers

3 3

Re: Cannot allocate and run VM from VM-Pool. There are no available VMs in the VM-Pool
by nicolas＠devels.es 12 Apr '19

12 Apr '19

Are the VMs from the pool 'up'? If so, no assignation can be done unless they are powered off. El 2019-04-12 14:31, Florian Rädler escribió: > I am getting the following Error after a Pool was generated and > migrated to another host. > > START_POOL fehlgeschlagen [Cannot allocate and run VM from VM-Pool. > There are no available VMs in the VM-Pool.] > > No user is connected to any of the running VMs. What can I do to solve > this problem? > > ------------------------- > > Pflichtangaben anzeigen [1] > > Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie > hier: http://www.deutschebahn.com/de/konzern/datenschutz [2] > > Links: > ------ > [1] http://www.deutschebahn.com/pflichtangaben/20190408 > [2] http://www.deutschebahn.com/de/konzern/datenschutz > > _______________________________________________ > 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/UL2KJKETQYFZR…

1 0

Cannot allocate and run VM from VM-Pool. There are no available VMs in the VM-Pool
by Florian Rädler 12 Apr '19

12 Apr '19

I am getting the following Error after a Pool was generated and migrated to another host. START_POOL fehlgeschlagen [Cannot allocate and run VM from VM-Pool. There are no available VMs in the VM-Pool.] No user is connected to any of the running VMs. What can I do to solve this problem? ________________________________ Pflichtangaben anzeigen<http://www.deutschebahn.com/pflichtangaben/20190408> Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier: http://www.deutschebahn.com/de/konzern/datenschutz

1 0

[ANN] oVirt 4.3.3 Fourth Release Candidate is now available
by Sandro Bonazzola 12 Apr '19

12 Apr '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.3 Fourth Release Candidate, as of April 12th, 2019. This update is a release candidate of the third in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. 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 [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance will be available soon - oVirt Node will be available soon[2] Additional Resources: * Read more about the oVirt 4.3.3 release highlights: http://www.ovirt.org/release/4.3.3/ * 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] http://www.ovirt.org/release/4.3.3/ [2] 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

Re: [Gluster-users] Gluster snapshot fails
by Strahil Nikolov 12 Apr '19

12 Apr '19

Hello All, I have tried to enable debug and see the reason for the issue. Here is the relevant glusterd.log: [2019-04-12 07:56:54.526508] E [MSGID: 106077] [glusterd-snapshot.c:1882:glusterd_is_thinp_brick] 0-management: Failed to get pool name for device systemd-1 [2019-04-12 07:56:54.527509] E [MSGID: 106121] [glusterd-snapshot.c:2523:glusterd_snapshot_create_prevalidate] 0-management: Failed to pre validate [2019-04-12 07:56:54.527525] E [MSGID: 106024] [glusterd-snapshot.c:2547:glusterd_snapshot_create_prevalidate] 0-management: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of isos are thinly provisioned LV. [2019-04-12 07:56:54.527539] W [MSGID: 106029] [glusterd-snapshot.c:8613:glusterd_snapshot_prevalidate] 0-management: Snapshot create pre-validation failed [2019-04-12 07:56:54.527552] W [MSGID: 106121] [glusterd-mgmt.c:147:gd_mgmt_v3_pre_validate_fn] 0-management: Snapshot Prevalidate Failed [2019-04-12 07:56:54.527568] E [MSGID: 106121] [glusterd-mgmt.c:1015:glusterd_mgmt_v3_pre_validate] 0-management: Pre Validation failed for operation Snapshot on local node [2019-04-12 07:56:54.527583] E [MSGID: 106121] [glusterd-mgmt.c:2377:glusterd_mgmt_v3_initiate_snap_phases] 0-management: Pre Validation Failed here is the output of lvscan & lvs: [root@ovirt1 ~]# lvscan ACTIVE '/dev/gluster_vg_md0/my_vdo_thinpool' [9.86 TiB] inherit ACTIVE '/dev/gluster_vg_md0/gluster_lv_data' [500.00 GiB] inherit ACTIVE '/dev/gluster_vg_md0/gluster_lv_isos' [50.00 GiB] inherit ACTIVE '/dev/gluster_vg_ssd/my_ssd_thinpool' [168.59 GiB] inherit ACTIVE '/dev/gluster_vg_ssd/gluster_lv_engine' [40.00 GiB] inherit ACTIVE '/dev/centos_ovirt1/swap' [6.70 GiB] inherit ACTIVE '/dev/centos_ovirt1/home' [1.00 GiB] inherit ACTIVE '/dev/centos_ovirt1/root' [60.00 GiB] inherit [root@ovirt1 ~]# lvs --noheadings -o pool_lv my_vdo_thinpool my_vdo_thinpool my_ssd_thinpool [root@ovirt1 ~]# ssh ovirt2 "lvscan;lvs --noheadings -o pool_lv" ACTIVE '/dev/gluster_vg_md0/my_vdo_thinpool' [<9.77 TiB] inherit ACTIVE '/dev/gluster_vg_md0/gluster_lv_data' [500.00 GiB] inherit ACTIVE '/dev/gluster_vg_md0/gluster_lv_isos' [50.00 GiB] inherit ACTIVE '/dev/gluster_vg_ssd/my_ssd_thinpool' [<161.40 GiB] inherit ACTIVE '/dev/gluster_vg_ssd/gluster_lv_engine' [40.00 GiB] inherit ACTIVE '/dev/centos_ovirt2/root' [15.00 GiB] inherit ACTIVE '/dev/centos_ovirt2/home' [1.00 GiB] inherit ACTIVE '/dev/centos_ovirt2/swap' [16.00 GiB] inherit my_vdo_thinpool my_vdo_thinpool my_ssd_thinpool [root@ovirt1 ~]# ssh ovirt3 "lvscan;lvs --noheadings -o pool_lv" ACTIVE '/dev/gluster_vg_sda3/gluster_thinpool_sda3' [41.00 GiB] inherit ACTIVE '/dev/gluster_vg_sda3/gluster_lv_data' [15.00 GiB] inherit ACTIVE '/dev/gluster_vg_sda3/gluster_lv_isos' [15.00 GiB] inherit ACTIVE '/dev/gluster_vg_sda3/gluster_lv_engine' [15.00 GiB] inherit ACTIVE '/dev/centos_ovirt3/root' [20.00 GiB] inherit ACTIVE '/dev/centos_ovirt3/home' [1.00 GiB] inherit ACTIVE '/dev/centos_ovirt3/swap' [8.00 GiB] inherit gluster_thinpool_sda3 gluster_thinpool_sda3 gluster_thinpool_sda3 I am mounting my bricks via systemd , as I have issues with bricks being started before VDO. [root@ovirt1 ~]# findmnt /gluster_bricks/isos TARGET SOURCE FSTYPE OPTIONS /gluster_bricks/isos systemd-1 autofs rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=21843 /gluster_bricks/isos /dev/mapper/gluster_vg_md0-gluster_lv_isos xfs rw,noatime,nodiratime,seclabel,attr2,inode64,noquota [root@ovirt1 ~]# ssh ovirt2 "findmnt /gluster_bricks/isos " TARGET SOURCE FSTYPE OPTIONS /gluster_bricks/isos systemd-1 autofs rw,relatime,fd=26,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14279 /gluster_bricks/isos /dev/mapper/gluster_vg_md0-gluster_lv_isos xfs rw,noatime,nodiratime,seclabel,attr2,inode64,noquota [root@ovirt1 ~]# ssh ovirt3 "findmnt /gluster_bricks/isos " TARGET SOURCE FSTYPE OPTIONS /gluster_bricks/isos systemd-1 autofs rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17770 /gluster_bricks/isos /dev/mapper/gluster_vg_sda3-gluster_lv_isos xfs rw,noatime,nodiratime,seclabel,attr2,inode64,logbsize=256k,sunit=512,swidth=1024,noquota [root@ovirt1 ~]# grep "gluster_bricks" /proc/mounts systemd-1 /gluster_bricks/data autofs rw,relatime,fd=22,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=21513 0 0 systemd-1 /gluster_bricks/engine autofs rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=21735 0 0 systemd-1 /gluster_bricks/isos autofs rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=21843 0 0 /dev/mapper/gluster_vg_ssd-gluster_lv_engine /gluster_bricks/engine xfs rw,seclabel,noatime,nodiratime,attr2,inode64,sunit=256,swidth=256,noquota 0 0 /dev/mapper/gluster_vg_md0-gluster_lv_isos /gluster_bricks/isos xfs rw,seclabel,noatime,nodiratime,attr2,inode64,noquota 0 0 /dev/mapper/gluster_vg_md0-gluster_lv_data /gluster_bricks/data xfs rw,seclabel,noatime,nodiratime,attr2,inode64,noquota 0 0 Obviously , gluster is catching "systemd-1" as a device and tries to check if it's a thin LV.Where should I open a bug for that ? P.S.: Adding oVirt User list. Best Regards,Strahil Nikolov В четвъртък, 11 април 2019 г., 4:00:31 ч. Гринуич-4, Strahil Nikolov <hunter86_bg(a)yahoo.com> написа: Hi Rafi, thanks for your update. I have tested again with another gluster volume.[root@ovirt1 glusterfs]# gluster volume info isos Volume Name: isos Type: Replicate Volume ID: 9b92b5bd-79f5-427b-bd8d-af28b038ed2a Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: ovirt1:/gluster_bricks/isos/isos Brick2: ovirt2:/gluster_bricks/isos/isos Brick3: ovirt3.localdomain:/gluster_bricks/isos/isos (arbiter) Options Reconfigured: cluster.granular-entry-heal: enable performance.strict-o-direct: on network.ping-timeout: 30 storage.owner-gid: 36 storage.owner-uid: 36 user.cifs: off features.shard: on cluster.shd-wait-qlength: 10000 cluster.shd-max-threads: 8 cluster.locking-scheme: granular cluster.data-self-heal-algorithm: full cluster.server-quorum-type: server cluster.quorum-type: auto cluster.eager-lock: enable network.remote-dio: off performance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off transport.address-family: inet nfs.disable: on performance.client-io-threads: off cluster.enable-shared-storage: enable Command run: logrotate -f glusterfs ; logrotate -f glusterfs-georep; gluster snapshot create isos-snap-2019-04-11 isos description TEST Logs:[root@ovirt1 glusterfs]# cat cli.log [2019-04-11 07:51:02.367453] I [cli.c:769:main] 0-cli: Started running gluster with version 5.5 [2019-04-11 07:51:02.486863] I [MSGID: 101190] [event-epoll.c:621:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2019-04-11 07:51:02.556813] E [cli-rpc-ops.c:11293:gf_cli_snapshot] 0-cli: cli_to_glusterd for snapshot failed [2019-04-11 07:51:02.556880] I [input.c:31:cli_batch] 0-: Exiting with: -1 [root@ovirt1 glusterfs]# cat glusterd.log [2019-04-11 07:51:02.553357] E [MSGID: 106024] [glusterd-snapshot.c:2547:glusterd_snapshot_create_prevalidate] 0-management: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of isos are thinly provisioned LV. [2019-04-11 07:51:02.553365] W [MSGID: 106029] [glusterd-snapshot.c:8613:glusterd_snapshot_prevalidate] 0-management: Snapshot create pre-validation failed [2019-04-11 07:51:02.553703] W [MSGID: 106121] [glusterd-mgmt.c:147:gd_mgmt_v3_pre_validate_fn] 0-management: Snapshot Prevalidate Failed [2019-04-11 07:51:02.553719] E [MSGID: 106121] [glusterd-mgmt.c:1015:glusterd_mgmt_v3_pre_validate] 0-management: Pre Validation failed for operation Snapshot on local node My LVs hosting the bricks are:[root@ovirt1 ~]# lvs gluster_vg_md0 LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_data gluster_vg_md0 Vwi-aot--- 500.00g my_vdo_thinpool 35.97 gluster_lv_isos gluster_vg_md0 Vwi-aot--- 50.00g my_vdo_thinpool 52.11 my_vdo_thinpool gluster_vg_md0 twi-aot--- 9.86t 2.04 11.45 [root@ovirt1 ~]# ssh ovirt2 "lvs gluster_vg_md0" LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_data gluster_vg_md0 Vwi-aot--- 500.00g my_vdo_thinpool 35.98 gluster_lv_isos gluster_vg_md0 Vwi-aot--- 50.00g my_vdo_thinpool 25.94 my_vdo_thinpool gluster_vg_md0 twi-aot--- <9.77t 1.93 11.39 [root@ovirt1 ~]# ssh ovirt3 "lvs gluster_vg_sda3" LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_data gluster_vg_sda3 Vwi-aotz-- 15.00g gluster_thinpool_sda3 0.17 gluster_lv_engine gluster_vg_sda3 Vwi-aotz-- 15.00g gluster_thinpool_sda3 0.16 gluster_lv_isos gluster_vg_sda3 Vwi-aotz-- 15.00g gluster_thinpool_sda3 0.12 gluster_thinpool_sda3 gluster_vg_sda3 twi-aotz-- 41.00g 0.16 1.58 As you can see - all bricks are thin LV and space is not the issue. Can someone hint me how to enable debug , so gluster logs can show the reason for that pre-check failure ? Best Regards,Strahil Nikolov В сряда, 10 април 2019 г., 9:05:15 ч. Гринуич-4, Rafi Kavungal Chundattu Parambil <rkavunga(a)redhat.com> написа: Hi Strahil, The name of device is not at all a problem here. Can you please check the log of glusterd, and see if there is any useful information about the failure. Also please provide the output of `lvscan` and `lvs --noheadings -o pool_lv` from all nodes Regards Rafi KC ----- Original Message ----- From: "Strahil Nikolov" <hunter86_bg(a)yahoo.com> To: gluster-users(a)gluster.org Sent: Wednesday, April 10, 2019 2:36:39 AM Subject: [Gluster-users] Gluster snapshot fails Hello Community, I have a problem running a snapshot of a replica 3 arbiter 1 volume. Error: [root@ovirt2 ~]# gluster snapshot create before-423 engine description "Before upgrade of engine from 4.2.2 to 4.2.3" snapshot create: failed: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of engine are thinly provisioned LV. Snapshot command failed Volume info: Volume Name: engine Type: Replicate Volume ID: 30ca1cc2-f2f7-4749-9e2e-cee9d7099ded Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: ovirt1:/gluster_bricks/engine/engine Brick2: ovirt2:/gluster_bricks/engine/engine Brick3: ovirt3:/gluster_bricks/engine/engine (arbiter) Options Reconfigured: cluster.granular-entry-heal: enable performance.strict-o-direct: on network.ping-timeout: 30 storage.owner-gid: 36 storage.owner-uid: 36 user.cifs: off features.shard: on cluster.shd-wait-qlength: 10000 cluster.shd-max-threads: 8 cluster.locking-scheme: granular cluster.data-self-heal-algorithm: full cluster.server-quorum-type: server cluster.quorum-type: auto cluster.eager-lock: enable network.remote-dio: off performance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off transport.address-family: inet nfs.disable: on performance.client-io-threads: off cluster.enable-shared-storage: enable All bricks are on thin lvm with plenty of space, the only thing that could be causing it is that ovirt1 & ovirt2 are on /dev/gluster_vg_ssd/gluster_lv_engine , while arbiter is on /dev/gluster_vg_sda3/gluster_lv_engine. Is that the issue ? Should I rename my brick's VG ? If so, why there is no mentioning in the documentation ? Best Regards, Strahil Nikolov _______________________________________________ Gluster-users mailing list Gluster-users(a)gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users

1 3

Hosted-engine inaccessible
by Tau Makgaile 12 Apr '19

12 Apr '19

Hi, I am currently experiencing a problem with my Hosted-engine. Hosted-engine disconnected after increasing / partition. The increase went well but after some time the hosted-enigine VM disconnected and has since been giving alerts such as* re-initializingFSM*. Though VMs underneth are running, Hosted-engine --vm-status: *"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail"* There is no backup to restore at the moment. I am looking for a way to bring it up without redeploying the hosted engine. Thanks in advance for your help. Kind regards, Tau

4 5

oVirt Node 4.3 Master on fc28
by femi adegoke 12 Apr '19

12 Apr '19

4.3 Master is looking good!! A few questions: - In Step #2: Fqdns: for a 3 host cluster, are we to add the 2nd & 3rd hosts? - In Step #5: Bricks: What effect does the RAID setting have? Enable Dedupe & Compression is new? Configure LV Cache: what do we enter for SSD? What happens if my disks are already all SSD, do I still benefit from using this?

4 11

Install of oVirt.hosted-engine-setup from galaxy fails
by Vrgotic, Marko 11 Apr '19

11 Apr '19

Dear oVirt team, Install of role oVirt.hosted-engine-setup from Galaxy repo fails: - downloading role 'hosted-engine-setup', owned by oVirt [WARNING]: - oVirt.hosted-engine-setup was NOT installed successfully: - sorry, oVirt.hosted-engine-setup was not found on https://galaxy.ansible.com. Apparently it fails due to name of the repo in the Galaxy which is with “_” instead of expected “-” . Marko Vrgotic

2 1

Re: HostedEngine cleaned up
by Strahil 11 Apr '19

11 Apr '19

The real image is defined within the XML stanza in the vdsm.log when the VM was last started . So if you remember when the last time the HostedEngine was rebooted, you can check the vdsm.log on the host. From there - check the cluster for the file. If it's missing deploy the HostedEngine again (on the previous HostedEngine cluster volume or on a completely new). Then try to import all Storages and then you will be able to import existing VMs. Best Regards, Strahil NikolovOn Apr 11, 2019 20:12, Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > > What happened is the engine's root filesystem had filled up. My colleague tried to resize the root lvm. The engine then did not come back. In trying to resolve that he cleaned up the engine and tried to re-install it, no luck in doing that. > > That brought down all the VMs. All VMs are down. we trying to move them into one of the standalone kvm host. We have been trying to locate the VM disk images, with no luck. > > According to the of the VM xml configuration file.the disk file is /rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685 > > Unfortunately we can find it and the solution on teh forum states that we can only find in the associated logical volume, but i think only when teh vm is running. > > The disk images we have been trying to boot up from are the one's we got from the gluster bricks, but the are far small that real images and can't boot > > > On Thu, Apr 11, 2019 at 6:13 PM Simone Tiraboschi <stirabos(a)redhat.com> wrote: >> >> >> >> On Thu, Apr 11, 2019 at 9:46 AM Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: >>> >>> Hi, >>> >>> We have a situation where the HostedEngine was cleaned up and the VMs are no longer running. Looking at the logs we can see the drive files as: >> >> >> Do you have any guess on what really happened? >> Are you sure that the disks really disappeared? >> >> Please notice that the symlinks under rhev/data-center/mnt/glusterSD/glustermount... are created on the fly only when needed. >> >> Are you sure that your host is correctly connecting the gluster storage domain? >> >>> >>> >>> 2019-03-26T07:42:46.915838Z qemu-kvm: -drive file=/rhev/data-center/mnt/glusterSD/glustermount.goku:_vmstore/9f8ef3f6-53f2-4b02-8a6b-e171b000b420/images/b2b872cd-b468-4f14-ae20-555ed823e84b/76ed4113-51b6-44fd-a3cd-3bd64bf93685,format=qcow2,if=none,id=drive-ua-b2b872cd-b468-4f14-ae20-555ed823e84b,serial=b2b872cd-b468-4f14-ae20-555ed823e84b,werror=stop,rerror=stop,cache=none,aio=native: 'serial' is deprecated, please use the corresponding option of '-device' instead >>> >>> I assume this is the disk was writing to before it went down

1 0

Re: Hosted-engine disconnected
by Strahil 11 Apr '19

11 Apr '19

Did you import your storages again after the redeploy ? If yes, there is a tab that allows you to import your templates and VMs. Most probably you will be able to get all of them almost without issues (in my case all VMs got under the default cluster). You only need new glusterfs volume for the redeploy of the engine. Still, have you booted your Engine and connected via VNC to check what happened ? Also, keep in mind that the vdsm.log contains the XML of each VM started on the host. That was how I booted my HostedEngine when the configuration was broken. Create the following alias: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' With it you will be able to use virsh define XML-file virsh start HostedEngine And so on... If you have an already running HostedEngine (new deploy), try first importing existing storage domains and their VMs. If not, try to power on your HostedEngine with virsh and rescue DVD (for example CentOS 7 install DVD is a good way) and use the troubleshoot menu to fix it. By the way , how did you extend the disks? Best Regards, Strahil NikolovOn Apr 11, 2019 18:33, Tau Makgaile <tau(a)sanren.ac.za> wrote: > > Hi, > > I have been experiencing a problem with my hosted-engine after increasing / partition. The increase went well for few minutes and disconnected. It started by showing bad head and it has since unreachable/ un-ping-able until. It was confusing because vms where still running. I decided to redeploy the engine with a hope that it will pull in the same vms into the dashboard. That did not give any positive results until i opted for a redeployment. things went well until i realized it will need to new glustermounts in order to go through, which also meant it risks losing information around my vms, which i have since stopped in order to allow the redeploment to carry on. > > I now need help to export all of the information around my vms, most importantly the disk images. I have been trying to get some disk images from /gluster_bricks/data/data/ with no luck in booting them up after conversion. I am thinking there might be information missing on this images since they boot into rescue mode. > > Please share more insight on how one can locate the entire disk information or the database where vms were last running. > > I did a check into log files, and did matching of the images with vms names but i have been unsuccessful. > > Thanks in advance for you reply, > > Kind regards, > Tau > >

1 0

Hosted-engine disconnected
by Tau Makgaile 11 Apr '19

11 Apr '19

Hi, I have been experiencing a problem with my hosted-engine after increasing / partition. The increase went well for few minutes and disconnected. It started by showing bad head and it has since unreachable/ un-ping-able until. It was confusing because vms where still running. I decided to redeploy the engine with a hope that it will pull in the same vms into the dashboard. That did not give any positive results until i opted for a redeployment. things went well until i realized it will need to new glustermounts in order to go through, which also meant it risks losing information around my vms, which i have since stopped in order to allow the redeploment to carry on. I now need help to export all of the information around my vms, most importantly the disk images. I have been trying to get some disk images from */gluster_bricks/data/data/ *with no luck in booting them up after conversion. I am thinking there might be information missing on this images since they boot into *rescue mode.* Please share more insight on how one can locate the entire disk information or the database where vms were last running. I did a check into log files, and did matching of the images with vms names but i have been unsuccessful. Thanks in advance for you reply, Kind regards, Tau

1 0

Disk Locked
by Николаев Алексей 11 Apr '19

11 Apr '19

2 2

Expand existing gluster storage in ovirt 4.2/4.3
by adrianquintero＠gmail.com 11 Apr '19

11 Apr '19

Hello, I have a 3 node ovirt 4.3 cluster that I've setup and using gluster (Hyperconverged setup) I need to increase the amount of storage and compute so I added a 4th host (server4.example.com) if it is possible to expand the amount of bricks (storage) in the "data" volume? I did some research and from that research the following caught my eye: old post "https://medium.com/@tumballi/scale-your-gluster-cluster-1-node-at-a-time-62…" So the question is, if taking that approach feasible? , is it even possible an oVirt point of view? --------------------------- My gluster volume: --------------------------- Volume Name: data Type: Replicate Volume ID: 003ffea0-b441-43cb-a38f-ccdf6ffb77f8 Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: server1.example1.com:/gluster_bricks/data/data Brick2: server2.example.com:/gluster_bricks/data/data Brick3: server3.example.com:/gluster_bricks/data/data (arbiter) Options Reconfigured: cluster.granular-entry-heal: enable performance.strict-o-direct: on network.ping-timeout: 30 storage.owner-gid: 36 storage.owner-uid: 36 cluster.choose-local: off user.cifs: off features.shard: on cluster.shd-wait-qlength: 10000 cluster.shd-max-threads: 8 cluster.locking-scheme: granular cluster.data-self-heal-algorithm: full cluster.server-quorum-type: server cluster.quorum-type: auto cluster.eager-lock: enable network.remote-dio: enable performance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off transport.address-family: inet nfs.disable: on performance.client-io-threads: off Thanks.

3 4

Re: Windows Guest timezone
by Strahil 11 Apr '19

11 Apr '19

I used to set windows machines to use HW clock in UTC , which helped for dual-boot hardware machines. Can't you use that approach and never worry about DST? Best Regards, Strahil NikolovOn Apr 11, 2019 11:42, Stefano Danzi <s.danzi(a)hawai.it> wrote: > > Hello! > > I've a guest windows VM (Server 2016) and hardware clock in oVirt > machine configuration is GMT +1. > Now we are DST period and machine timezone is GMT +2. Engine Dashboard > warn me about timezone > mismatch between configuration and running VM. I can't see a setting to > enable DST on emulated hardware. > > Some ideas? > _______________________________________________ > 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/ENKC37PNVQEZ2…

1 0

Windows Guest timezone
by Stefano Danzi 11 Apr '19

11 Apr '19

Hello! I've a guest windows VM (Server 2016) and hardware clock in oVirt machine configuration is GMT +1. Now we are DST period and machine timezone is GMT +2. Engine Dashboard warn me about timezone mismatch between configuration and running VM. I can't see a setting to enable DST on emulated hardware. Some ideas?

1 0

Ovirt does not support AMD EPYC CPUs?
by Erick Perez 11 Apr '19

11 Apr '19

Hi, In its current release, OVIRT only shows AMD Opteron G1,G2,G3,G4,G5 and no mention of EPYC. This thread mentioned that a respin of Ovirt will address this, but never happened. https://lists.ovirt.org/archives/list/users@ovirt.org/message/2PEAYGK5PE33W… comments?

1 0

Get Disk used size
by mustafa.taha.mu95＠gmail.com 11 Apr '19

11 Apr '19

Hi Can i have way to know the allocated/used size of the VM disk , without install any agent on the VM ?

2 1

change self-hosted engine storage domain
by jason.cox＠harris.com 11 Apr '19

11 Apr '19

Is it possible to change a self-hosted engine's storage domain's settings? I setup a 3-node ovirt + gluster cluster with a dedicated 'engine' storage domain. I can see through the administration portal that the engine storage domain is using a single gluster host and no backup volfile servers. The single gluster host that the engine storage domain settings refer to had to be removed, so now I'm getting issues where VDSM is reporting that it cannot get the volume file information for the engine storage domain. I'm not sure how to go about changing the settings since the only way I've seen how to do this is through the administration portal, which relies on the engine VM (and its storage) being available. What I'd like to do is change the storage domain's path and add mount options for the backup volfile servers.

2 1

Re: Get Disk used size
by Strahil 10 Apr '19

10 Apr '19

What type of storage is being used. If it's file based (NFS,Cluster , other POSIX compliant) you can use qemu-img info to check virtual and actual size of the disk. Still ,this method can be inaccurate. Best Regards, Strahil NikolovOn Apr 10, 2019 15:02, mustafa.taha.mu95(a)gmail.com wrote: > > Hi > Can i have way to know the allocated/used size of the VM disk , without install any agent on the VM ? > _______________________________________________ > 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/IAQPQLKHNZ5QS…

1 0

Re: Different credentials ovirt_vm module
by Ondra Machacek 10 Apr '19

10 Apr '19

Hello, this seems ok to me. Can you please check the engine.log, for some error? On 09/04/2019 22:26, Florian Rädler wrote: > Hi, > > how can i use other credentials (run once) in the ansible playbook for > Sysprep domain join? > > My playbook: > > User_name and root_password does not sound like it’s the right option. > > How can I realize that? > > BR > > Florian > > > ------------------------------------------------------------------------ > > Pflichtangaben anzeigen > <http://www.deutschebahn.com/pflichtangaben/20190408> > > Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie > hier: http://www.deutschebahn.com/de/konzern/datenschutz > > _______________________________________________ > 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/ZOKA7M24U5HSZ… >

1 0

accessing ovirt-image-repository from behind proxy?
by Jarosław Prokopowski 10 Apr '19

10 Apr '19

Hi, Is there a way to connect to ovirt-image-repository from ovirt-engine through proxy server? I tried to set http_proxy in /etc/profile of the hosted-engine VM and restarted the VM but it does not help... Errors I get while testing the connection: 2019-04-10 12:36:49,590+03 ERROR [org.ovirt.engine.core.bll.storage.repoimage.GetImagesListQuery] (default task-3) [58f90541-0212-4f1e-9b14-eafc9a8237b9] Failed to retrieve image list: Connec tion timed out (Connection timed out) ... 2019-04-10 12:57:40,609+03 ERROR [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] (default task-3) [3c3baa28-c1ac-4783-b362-44b21d7430b5] Command 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' failed: EngineException: (Failed with error PROVIDER_FAILURE and code 5050) Thanks Jarek

1 0

Installing VM - Fedora installer stuck on "Setting up installation source..."
by Jarosław Prokopowski 10 Apr '19

10 Apr '19

Hello, I installed oVirt 4.3.2, added NFS ISO domain and trying to create Fedora 26 VM. The installer starts but is stuck on "Installation Source Setting up installation source..." on the "INSTALLATION SUMMARY" screen. I cannot find any useful information in logs. Do you have any idea what can cause the issue and how to fix that? Thanks Jarek

2 3

Re: Vagrant Plugin
by Jeremy Tourville 10 Apr '19

10 Apr '19

Thanks for your reply Luca, I confirmed the cluster name, it is "Default". I even tried to run the script again and I made sure the D in default was upper case because linux is case sensitive. It still fails in the same way as before. [cid:c5758639-8ce0-46d1-ad0b-900af9cc138e] ________________________________ From: Luca 'remix_tj' Lorenzetto <lorenzetto.luca(a)gmail.com> Sent: Saturday, March 30, 2019 3:34 AM To: Jeremy Tourville Subject: Re: [ovirt-users] Vagrant Plugin Il ven 29 mar 2019, 19:12 Jeremy Tourville <Jeremy_Tourville(a)hotmail.com<mailto:Jeremy_Tourville@hotmail.com>> ha scritto: I am having some trouble getting the Ovirt Vagrant plugin working. I was able to get Vagrant installed and could even run the example scenario listed in the blog. https://www.ovirt.org/blog/2017/02/using-oVirt-vagrant.html My real issue is getting a vm generated by the SecGen project https://github.com/SecGen/SecGen to come up. If I use the VirtualBox provider everything works as expected and I can launch the vm with vagrant up. If I try to run using Ovirt provider it fails. I had originally posted this over in Google groups / Vagrant forums and it was suggested to take it to Ovirt. Hopefully, somebody here has some insights. The process fails quickly with the following output. Can anyone give some suggestions on how to fix the issue? I have also included a copy of my vagrantfile below. Thanks in advance for your assistance! ***Output*** Bringing machine 'escalation' up with 'ovirt4' provider... ==> escalation: Creating VM with the following settings... ==> escalation: -- Name: SecGen-default-scenario-escalation ==> escalation: -- Cluster: default ==> escalation: -- Template: debian_stretch_server_291118 ==> escalation: -- Console Type: spice ==> escalation: -- Memory: ==> escalation: ---- Memory: 512 MB ==> escalation: ---- Maximum: 512 MB ==> escalation: ---- Guaranteed: 512 MB ==> escalation: -- Cpu: ==> escalation: ---- Cores: 1 ==> escalation: ---- Sockets: 1 ==> escalation: ---- Threads: 1 ==> escalation: -- Cloud-Init: false ==> escalation: An error occured. Recovering.. ==> escalation: VM is not created. Please run `vagrant up` first. /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:52:in `raise_error': Fault reason is "Operation Failed". Fault detail is "Entity not found: Cluster: name=default". HTTP response code is 404. Hello Jeremy, Looks like you have no cluster called default in your setup. Edit your vagrant file accordingly to your setup. Luca

2 2

Re: Bug 1666795 - Related? - VM's don't start after shutdown on FCP
by Nardus Geldenhuys 10 Apr '19

10 Apr '19

attaching ovirt engine.log

1 1

virt-v2v from Fedora 29 to oVirt 4.3 and ovirtsdk4
by Gianluca Cecchi 10 Apr '19

10 Apr '19

Hello, I'm trying to migrate a VM from a Fedora 29 system to oVirt 4.3.2. I'm trying to use the "-o rhv-upload" option that should be faster. virt-v2v -o rhv-upload -oc https://my_engine/ovirt-engine/api -os my_sd_domain -op /tmp/ovirt-admin-password -of raw -oo rhv-cafile=/tmp/ca.pem -oo rhv-direct --bridge nat:ovn193 my_vm But I get " Traceback (most recent call last): File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'ovirtsdk4' virt-v2v: error: the Python module ‘ovirtsdk4’ could not be loaded, is it installed? See previous messages for problems. If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] " I see on Fedora 29 repos thease are the only relevant available packages: [root@ope46 ~]# dnf search ovirt ... ovirt-engine-cli.noarch : oVirt Engine Command Line Interface ... ovirt-engine-sdk-java-javadoc.noarch : Javadocs for ovirt-engine-sdk-java ... ovirt-engine-sdk-java.noarch : oVirt Engine Software Development Kit (Java) ... python2-ovirt-engine-sdk.noarch : oVirt Engine Software Development Kit (Python) ... and python2-ovirt-engine-sdk.noarch is related to source ovirt-engine-sdk-python-3.6.9.1-7.fc29.src.rpm so only sdk3 On oVirt repos I see here only for F28: https://resources.ovirt.org/pub/ovirt-4.3/rpm/fc28/x86_64/ trying to install # dnf install https://resources.ovirt.org/pub/ovirt-4.3/rpm/fc28/x86_64/python3-ovirt-eng… gives: Error: Problem: conflicting requests - nothing provides python(abi) = 3.6 needed by python3-ovirt-engine-sdk4-4.3.0-1.fc28.x86_64 (try to add '--skip-broken' to skip uninstallable packages) How can I get correct rpm packages to interact with v4 api of 4.3? Thanks, Gianluca

2 2