November 2019 - Users - oVirt List Archives

Warning: out of sync hosts ovirt-node3 ?
by wangyu13476969128＠126.com 13 Nov '19

13 Nov '19

In the ovirt-engine web interface, compute-->clusters, there is a cluster with the following information: Warning: out of sync hosts ovirt-node3 ? What is the cause ? How can I solve this problem ?

1 0

engine manager VM not launching
by bepassionatenow＠gmail.com 13 Nov '19

13 Nov '19

Good evening/morning, I can't launch the Engine Manager after the initial install through Cockpit. It initially started fine but I could never login. Cockpit showed that the VM was not set to auto-restart. I don't see how to change that and the button to "run" won't work. Spinning box in the top right corner is causing issues (won't register properly). Any help would be greatly appreciated. Thanks! Daniel

1 0

Windows Server 2019 crash dxgkrnl.sys
by gregor 13 Nov '19

13 Nov '19

Hello, during the Installation of Windows Server 2019 after the first reboot the VM crashed and inside the ntbtlog.txt I found that dxgkrnl.sys can not be loaded. Environment: oVirt 4.3.6.7-1.el7 CPU: Intel-Westmere Memory: 4096MB Operation System VM config: Windows 2019 x64 HDD: VirtIO-SCSI VirtIO driver: virtio-win-0.1.171_servers_amd64.vfd Does anybody has an hint how to solve this problem and use Windows Server 2019? Besides: It's possible to install and use Windows Server 2019 in VirtualBox 6.*. We have to install it in the meantime there to have a alternative solution because it took now about two days to find a solution. We tried different settings for VGA and drivers IDE ... and many more. best regards gregor

2 1

oVirt change IP's & add new ISO share
by Jonathan Mathews 13 Nov '19

13 Nov '19

Good Day I have to change the IP addresses of the oVirt Engine, hosts and storage to a new IP range. Please, can you advise the best way to do this and if there is anything I would need to change in the database? I have also run into an issue where someone has removed the ISO share/data on the storage, so I am unable to remove, activate, detach or even add a new ISO share. Please, can you advise the best wat to resolve this? Please see the below engine logs: 2019-10-30 11:39:13,918 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Failed in 'DetachStorageDomainVDS' method 2019-10-30 11:39:13,942 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM command failed: Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',) 2019-10-30 11:39:13,943 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] IrsBroker::Failed::DetachStorageDomainVDS: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 2019-10-30 11:39:13,951 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] FINISH, DetachStorageDomainVDSCommand, log id: 5547e2df 2019-10-30 11:39:13,951 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-38) [58f6cfb8] -- executeIrsBrokerCommand: Attempting on storage pool '5849b030-626e-47cb-ad90-3ce782d831b3' 2019-10-30 11:39:13,951 ERROR [org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Command 'org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358) 2019-10-30 11:39:13,952 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-38) [58f6cfb8] START, HSMGetAllTasksInfoVDSCommand(HostName = host01, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='291a3a19-7467-4783-a6f7-2b2dd0de9ad3'}), log id: 6cc238fb 2019-10-30 11:39:13,952 INFO [org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Command [id=cec030b7-4a62-43a2-9ae8-de56a5d71ef8]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageId='42b7d819-ce3a-4a18-a683-f4817c4bdb06'}', status='Inactive'}. 2019-10-30 11:39:13,975 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Correlation ID: 28ac658, Job ID: b31e0f44-2d82-47bf-90d9-f69e399d994f, Call Stack: null, Custom Event ID: -1, Message: Failed to detach Storage Domain iso to Data Center Default. (User: admin@internal) 2019-10-30 11:42:46,711 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-25) [31e89bba] START, SPMGetAllTasksInfoVDSCommand( IrsBaseVDSCommandParameters:{runAsync='true', storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', ignoreFailoverLimit='false'}), log id: 59192768 2019-10-30 11:42:48,825 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Failed in 'ActivateStorageDomainVDS' method 2019-10-30 11:42:48,855 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM command failed: Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',) 2019-10-30 11:42:48,856 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] IrsBroker::Failed::ActivateStorageDomainVDS: IRSGenericException: IRSErrorException: Failed to ActivateStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 2019-10-30 11:42:48,864 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] FINISH, ActivateStorageDomainVDSCommand, log id: 518fdcf 2019-10-30 11:42:48,865 ERROR [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Command 'org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: IRSGenericException: IRSErrorException: Failed to ActivateStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358) 2019-10-30 11:42:48,865 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-25) [31e89bba] -- executeIrsBrokerCommand: Attempting on storage pool '5849b030-626e-47cb-ad90-3ce782d831b3' 2019-10-30 11:42:48,865 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-25) [31e89bba] START, HSMGetAllTasksInfoVDSCommand(HostName = host02, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='3673a0e1-721d-40ba-a179-b1f13a9aec43'}), log id: 47ef923b 2019-10-30 11:42:48,866 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Command [id=68bf0e1e-6a0b-41cb-9cad-9eb2bf87c5ee]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageId='42b7d819-ce3a-4a18-a683-f4817c4bdb06'}', status='Inactive'}. 2019-10-30 11:42:48,888 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Correlation ID: 5b208434, Job ID: dff5f615-9dc4-4d79-a37e-5c6e99a2cc6b, Call Stack: null, Custom Event ID: -1, Message: Failed to activate Storage Domain iso (Data Center Default) by admin@internal Thanks Jonathan

3 4

DHCP Client in Guest VM does not work on ovirtmgmt
by ccesario＠blueit.com.br 13 Nov '19

13 Nov '19

Hello, Is there any special config to usage dhcp client on Guest VM using ovirtmgmt/ovirtmgmt vnic profile ? Currently I have a VM using the ovirtmgmt/ovirtmgmt NIC profile and this interface is configured as DHCP client, and this does not work when using ovirtmgmt/ovirtmgmt as NIC profile. But if I assign manual IP address from the same range of DHCP server the comunication it works. And If usage other NIC profile in other VLAN with other DHCP server it works. It seems ovirtmgmt/ovirtmgmt profile filter the DHCP protocol. Could someone has idea to allow DHCP protocol works on ovirtmgmt/ovirtmgmt NIC profile? Best regards Carlos

7 24

Tesla P4 and /sys/class/mdev_bus/
by Fabrice Bacchella 13 Nov '19

13 Nov '19

I have a Tesla P4 installed on a HPE ProLiant DL360 Gen10 on a CentOS 7.7. The setup was running fine since at least February. I made a successful upgrade from oVirt 4.2 to 4.3 and CentOS 7.6 to CentOS 7.7. I was using in oVirt in a pass-througth setting. I made a minor upgrade a few days ago. And since the VM is unable to see the Tesla P4. I think that the main problem is with mdev. vdsm-client Host hostdevListByCaps | grep mdev return nothing. There is no directory /sys/class/mdev_bus. I tried a full modload: modprobe nvidia_vgpu_vfio nvidia vfio_mdev mdev vfio_iommu_type1 vfio nvidia nvidia-modeset nvidia-drm nvidia-uvm vfio-pci. But it does nothing. Why did my kernel think the P4 is not mdev-compatible any more ? How can I check that ? I think it break when upgrading my kernel from kernel-3.10.0-1062.1.2.el7.x86_64 to kernel-3.10.0-1062.4.1.el7.x86_64. I tried with both the nouveau driver and the nvidia driver.

2 2

Re: Do I need to use self hosted engine with a GlusterFs three node setup
by Strahil 13 Nov '19

13 Nov '19

I remember creating my oVirt setup in 2 stages: 1. Using cockpit to deploy the gluster cluster 2. Using cockpit to deploy HCI on the created gluster clustet. If that's not changed you can only deploy the gluster clustet, thrn deploy the engine somewhere else and then connect the engine (add storage domain) to the gluster cluster, which also can be your oVirt compute nodes (making them at the end HyperConverged oVirt Cluster). Of course , that was an year ago - so it could be different. Best Regards, Strahil NikolovOn Nov 13, 2019 14:16, donagh.moran(a)oracle.com wrote: > > Hi Vojtech > > Thanks for the info, I have been looking for a method of creating the gluster cluster via cockpit on one of my three hosts but the only way I can see is via the hosted engine setup. Is it a case that we need to configure the hosts to use gluster storage with the cli commands prior to adding it to a pre-existing non hosted engine? > > Donagh > _______________________________________________ > 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/IIEY3Z3GDGH4V…

1 0

[ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Sandro Bonazzola 13 Nov '19

13 Nov '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 Third Release Candidate for testing, as of November 13th, 2019. This update is a release candidate of the seventh 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.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. While testing this release candidate please note that oVirt node now includes: - ansible 2.9.0 - GlusterFS 6.6 Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ * 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.7/ [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://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 3

Re: Do I need to use self hosted engine with a GlusterFs three node setup
by Strahil 13 Nov '19

13 Nov '19

You don't need to host the engine on the gluster cluster. I know people you have hosted the engine on a bare metal (pacemaker cluster) , so feel free to experiment. The only requirement is that tge engine needs to be able to communicate with the hosts (I'm not sure if layer 2 connectivity is necessary). Best Regards, Strahil Nikolov Best Regards, Strahil NikolovOn Nov 12, 2019 16:00, donagh.moran(a)oracle.com wrote: > > Every piece of documentation I read regarding the setup of Gluster seems to suggest using at least one of the the nodes to host the engine. Is this a requirement of can I use an engine that is deployed on a VM on another server in the same network? Any info would be much appreciated. > _______________________________________________ > 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/LN4CTUMQSTJX4…

2 1

Re: restore
by suporte＠logicworks.pt 13 Nov '19

13 Nov '19

yes you are right. I miss that. Sorry Thanks a lot De: "Staniforth, Paul" <P.Staniforth(a)leedsbeckett.ac.uk> Para: suporte(a)logicworks.pt, "users" <users(a)ovirt.org> Enviadas: Terça-feira, 12 De Novembro de 2019 17:49:18 Assunto: Re: restore As you did a full backup including the data warehouse you need engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --provision-dwh-db --restore-permissions see https://www.ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.… Backups and Migration | oVirt Chapter 12: Backups and Migration Backing Up and Restoring the oVirt Engine Backing up oVirt Engine - Overview. Use the engine-backup tool to take regular backups of the oVirt Engine. The tool backs up the engine database and configuration files into a single file and can be run without interrupting the ovirt-engine service.. Syntax for the engine-backup Command www.ovirt.org Regards, Paul S. From: suporte(a)logicworks.pt <suporte(a)logicworks.pt> Sent: 12 November 2019 17:39 To: users <users(a)ovirt.org> Subject: [ovirt-users] restore Hi, I did a backup of engine like this # engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name In a newly installed machine try to restore it: # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm # yum update # yum install ovirt-engine # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions but get this error: Start of engine-backup with mode 'restore' scope: all archive file: file_name log file: log_file_name Preparing to restore: - Unpacking file 'file_name' Restoring: - Files Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'. I'm running ovirt Version:4.3.4.3-1.el7 If I run # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --no-restore-permissions still the same error Any idea? Many Thanks -- Jose Ferradeira http://www.logicworks.pt To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

2 2

External networks issue after upgrading to 4.3.6
by ada per 12 Nov '19

12 Nov '19

After upgrading to the latest stable version the external networks lost all functionality. Under providers-->ovn-network-provider the test runs successfully. But when im creating an external provider network, attaching it to a router as a LAN setting up dhcp lease it is not reachable from other VMs in the same network. Hosts and hosted engine can't seem to ping it either. I tried disabling firewalls on both hosted engines, VMs and host and still nothing. When configuring Logical networks or VLANs they work perfectly tje one problem is the external networks. I have another environment running on a previous version of ovirt and it works perfectly there. I think its a bug. Thanks for your help

4 16

Re: Migrate VM from oVirt to oVirt
by Strahil 12 Nov '19

12 Nov '19

You will need a storage that will be your 'USB stick' . For example you can attach NFS-based storage domain, migrate the disks of the VM to that storage. Then power off that VM, set the storage to maintenance and then detach it from first oVirt engine. Then you attach and activate that NFS storage in your new oVirt engine. After Activation, there will be an 'Import VMs/templates' tab . Click on it and import the VM in a cluster. Last step is to migrate your VM's disks from that NFS to their permanent storage. Best Regards, Strahil NikolovOn Nov 12, 2019 04:39, adrianquintero(a)gmail.com wrote: > > 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! > _______________________________________________ > 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/4OTOXXGYWL2SM…

1 0

restore
by suporte＠logicworks.pt 12 Nov '19

12 Nov '19

Hi, I did a backup of engine like this # engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name In a newly installed machine try to restore it: # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm # yum update # yum install ovirt-engine # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions but get this error: Start of engine-backup with mode 'restore' scope: all archive file: file_name log file: log_file_name Preparing to restore: - Unpacking file 'file_name' Restoring: - Files Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'. I'm running ovirt Version:4.3.4.3-1.el7 If I run # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --no-restore-permissions still the same error Any idea? Many Thanks -- Jose Ferradeira http://www.logicworks.pt

2 1

Fwd: [moVirt] Do I need to use a self hosted engine with a GlusterFs three node setup
by Tomas Jelinek 12 Nov '19

12 Nov '19

forwarding to the correct list ---------- Forwarded message --------- From: <donagh.moran(a)oracle.com> Date: Tue, Nov 12, 2019 at 3:03 PM Subject: [moVirt] Do I need to use a self hosted engine with a GlusterFs three node setup To: <movirt(a)ovirt.org> Every piece of documentation I read regarding the setup of Gluster seems to suggest using at least one of the the nodes to host the engine. Is this a requirement of can I use an engine that is deployed on a VM on another server in the same network? Any info would be much appreciated. _______________________________________________ moVirt mailing list -- movirt(a)ovirt.org To unsubscribe send an email to movirt-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/movirt@ovirt.org/message/7ZA5XNMLS3QQ…

1 0

Does ovirt support sshfs?
by TomK 12 Nov '19

12 Nov '19

Hi All, Does ovirt support sshfs for mount locally accessible LUN's instead of NFS? -- Thx, TK.

2 1

SHE with multipath on multiple iSCSI targets
by Francesco Castellano 12 Nov '19

12 Nov '19

Dear sirs, we're trying to install an SHE oVirt 4.3.6 using an iSCSI SAN that provides us multiple targets (8) over 4 different portals. Following 5.1 of "RHV installation using Cockpit" we set up iscsi and multipath ahead with a 90GB LUN to be used for the engine VM. Unfortunately, even if the node OS sees correctly the LUN, e.g.: # multipath -ll > 36000d31004235a000000000000000018 dm-34 COMPELNT,Compellent Vol > size=90G features='1 queue_if_no_path' hwhandler='0' wp=rw > `-+- policy='service-time 0' prio=1 status=active > |- 16:0:0:3 sdu 65:64 active ready running > |- 24:0:0:3 sdt 65:48 active ready running > |- 17:0:0:3 sds 65:32 active ready running > |- 25:0:0:3 sdv 65:80 active ready running > |- 15:0:0:3 sdx 65:112 active ready running > |- 29:0:0:3 sdw 65:96 active ready running > |- 28:0:0:3 sdy 65:128 active ready running > |- 20:0:0:3 sdz 65:144 active ready running > `- 21:0:0:3 sdaa 65:160 active ready running # lsscsi -ist | grep 36000d31004235a000000000000000018 > [15:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a43,t,0x0 > /dev/sdx 36000d31004235a000000000000000018 96.6GB > [16:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a43,t,0x0 > /dev/sdu 36000d31004235a000000000000000018 96.6GB > [17:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a44,t,0x0 > /dev/sds 36000d31004235a000000000000000018 96.6GB > [20:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235243,t,0x0 > /dev/sdz 36000d31004235a000000000000000018 96.6GB > [21:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235244,t,0x0 > /dev/sdaa 36000d31004235a000000000000000018 96.6GB > [24:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a48,t,0x0 > /dev/sdt 36000d31004235a000000000000000018 96.6GB > [25:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a49,t,0x0 > /dev/sdv 36000d31004235a000000000000000018 96.6GB > [28:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235248,t,0x0 > /dev/sdy 36000d31004235a000000000000000018 96.6GB > [29:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235249,t,0x0 > /dev/sdw 36000d31004235a000000000000000018 96.6GB > # iscsiadm -m session | grep -E '[a2]4[3489]' | sort -k 3.8 > tcp: [1] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a43 > (non-flash) > tcp: [2] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a43 > (non-flash) > tcp: [3] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a44 > (non-flash) > tcp: [6] 10.201.204.20:3260,0 iqn.2002-03.com.compellent:5000d31004235243 > (non-flash) > tcp: [7] 10.201.204.20:3260,0 iqn.2002-03.com.compellent:5000d31004235244 > (non-flash) > tcp: [10] 10.201.205.10:3260,0 > iqn.2002-03.com.compellent:5000d31004235a48 (non-flash) > tcp: [11] 10.201.205.10:3260,0 > iqn.2002-03.com.compellent:5000d31004235a49 (non-flash) > tcp: [14] 10.201.205.20:3260,0 > iqn.2002-03.com.compellent:5000d31004235248 (non-flash) > tcp: [15] 10.201.205.20:3260,0 > iqn.2002-03.com.compellent:5000d31004235249 (non-flash) > during the engine deploy neither via cockpit nor with "hosted-engine --deploy" it was able to see any LUN. Having a lot of portals (4) and each having 4 targets (two of which being independents path to the LUN), we chose a portal to discover, it proposed us 4 targets, and we had to choose a target to log in, but in the end, no LUN was proposed. After a few attempts, we found that, if we logged out from any targets (and clean up the open-iscsi database), after the login in an appropriate target, the installer proposed us the LUN, and we successfully deployed the SHE. But unfortunately, such an installation doesn't track effectively all the 8 paths over 8 different targets, but just the one chosen during the installation (this is different, for example, with respect to other LUNs for data domains that we attached afterwards). Thus we miss the HA we aimed to for the engine data domain. I said this, because when I ask for /ovirt-engine/api/storagedomains, whilst a second LUN has 8 children with different targets below storage_domain/${another data domain}/storage/volume_group/logical_units/logical_unit/, for the hosted_storage I just have one. My questions are: a) is there a way to add the other targets/paths consistently (even through the REST interface)? b) is there another installation, or recovery, procedure to get the engine data domain in high availability on our iSCSI topology? Thank you so much for your suggestions, they are really appreciated, Best regards, Francesco Castellano

3 5

Quick question regarding FQDN
by Christian Reiss 11 Nov '19

11 Nov '19

Hey folks, for production use quality it is recommended to have backend (storage) and front end seperated. Let' assume: - 85.0.0.0/24 public IP block - 10.100.0.0/24 private IPs for DC internal usage - 10.200.0.0/24 private IPs for storage only LAN and running, as per recommendation 3 nodes: - node01: - fqdn: node01.dc-example.com - fqdn storage: node02.storage.example.com - no public IP - 10.100.0.1 primary IP - 10.200.0.1 storage IP - node02: - fqdn: node02.dc-example.com - fqdn storage: node02.storage.example.com - no public IP - 10.100.0.2 primary IP - 10.200.0.2 storage IP - node03: - fqdn: node03.dc-example.com - fqdn storage: node02.storage.example.com - no public IP - 10.100.0.3 primary IP - 10.200.0.3 storage IP The storage network is its own physical network with 10gig that only connects those three servers. How can I specify which IP to use for storage, which for frontend traffic? I am assuming this as the controller and all admins should be able to reach the nodes via frontend, which is not the storage one. Okay, I am lost. Whats the real solution here? Or is "frontend" no-ip, just VM traffic and "backend" is the 10gig storage "Only" where all the FQDN reside? Thanks for clarification, -Chris. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

4 3

I want to configure an web server
by Istiaque Islam 11 Nov '19

11 Nov '19

Hi there, I have installed oVirt on a server and related ISO and Data domains. I can create Virtual Machines and that machine get access to internet to download things. What I want to do now : 1. create an web server using centos and access that webserver from anywhere with internet connection 2. Then I shall configure a domain name for that webserver hosted in oVirt Virtual Machine. My Question : How to configure the virtual machine in oVirt so that when I enter my specified domain name/IP it will hit that particular virtual machine? As it is a virtual machine, it will not get any public IP, so how should i configure the virtual machine set up so that it can be used as an web server. Thanks in advance. -- With Regards, *Mohammed Istiaque Islam* *Contact no *: *+8801745723593* Email : jisan6347(a)gmail.com LinkedIn Profile : Profile_Linkedin_Istiaque <http://www.linkedin.com/in/mohammed-istiaque-islam-59541866>

3 2

Re: When I log in ovirt-engine , it show "Unable to log in because the user account is disabled or locked. Contact the system administrator."
by wangyu13476969128＠126.com 11 Nov '19

11 Nov '19

It's OK now. Thank you very much !

1 0

Re: When I log in ovirt-engine , it show "Unable to log in because the user account is disabled or locked. Contact the system administrator."
by Strahil 11 Nov '19

11 Nov '19

Login via ssh on the engine and unlock your user via ovirt-aaa-jdbc-tool tool. Best Regards, Strahil NikolovOn Nov 11, 2019 11:05, wangyu13476969128(a)126.com wrote: > > When I log in ovirt-engine，the username and password is correct. > But the error show "Unable to log in because the user account is disabled or locked. Contact the system administrator." > How can I solve this problem ? > _______________________________________________ > 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/TGLVOMEDV2TGK…

1 0

Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by Yedidyah Bar David 11 Nov '19

11 Nov '19

On Mon, Nov 11, 2019 at 12:26 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > Thanks, > I should have been clearer, what I meant was could you install 4.3.5 and restore to that, then run engine-setup --offline? Of course, this should work. The only point is that once 4.3.6 is released, it's not that easy to install 4.3.5, because yum generally tries to install the latest versions of stuff - and in theory, there might be issues with installing stuff from 4.3.6 repo with a 4.3.5 engine, so if you want an exact replicate of a 4.3.5 engine, you have to check all relevant packages, not just the engine. > > Regards, > Paul S. > ________________________________ > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: 11 November 2019 10:19 > To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > Cc: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com>; users <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5? > > On Mon, Nov 11, 2019 at 12:12 PM Staniforth, Paul > <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > > I haven't tried it but doesn't engine-setup --offline stop it upgrading minor releases. > > It prevents only the packager component. > > If you already have 4.3.6 installed, which was the original question, > then engine-setup will still update the database schema. And if it > didn't, the 4.3.6 engine might fail working correctly with a 3.4.5.5 > database. In particular: > > The documentation for engine-backup always stated that you must run > engine-setup immediately after restore. But at some points in time, > and under certain conditions, this was actually optional. You could > have done a restore, and immediately start the engine, and it would > have worked. But this isn't the case if your restored db is older than > the installed engine. Then, you must run engine-setup before starting > the engine. > > Best regards, > > > > > Regards, > > Paul S. > > ________________________________ > > From: Yedidyah Bar David <didi(a)redhat.com> > > Sent: 11 November 2019 07:57 > > To: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com> > > Cc: users <users(a)ovirt.org> > > Subject: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5? > > > > On Tue, Oct 29, 2019 at 11:55 AM <wangyu13476969128(a)126.com> wrote: > > > > > > The current version of ovirt-engine in production environment is 4.3.5.5. > > > In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link: > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > > > I backed it up using the command: > > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > > > I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes. > > > > > > According to the relevant links: > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > > > The ovirt-engine is installed on the standby machine. > > > > > > After I have executed these three commands: > > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > > > > > 2. yum update > > > > > > 3. yum install ovirt-engine > > > > > > I found that the ovirt-engine version of the standby machine is 4.3.6 > > > > > > So my question is: > > > > > > 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine: > > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > > > Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)? > > > > In principle it should be ok. After you restore with above command, > > you should run 'engine-setup', and this will update your restored > > database schema to 4.3.6. > > This is not routinely tested explicitly, though, but I expect that > > people often do this, perhaps even unknowingly, when they restore from > > a backup taken with a somewhat-old version. > > > > > > > > 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5? > > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > > 2. yum update > > > 3. yum install ovirt-engine > > > > In theory you can change last one to 'yum install > > ovirt-engine-4.3.5.5'. I didn't try that, and you are quite likely to > > run into complex dependencies you'll have to satisfy by yourself. > > > > I think the best solution for you, if you care about active and > > standby to be identical, is to upgrade your active one as well, and > > keep them same version going forward. > > > > I'd also like to note that maintaining a standby engine and using it > > the way you intend to, is not in the scope of oVirt. People do similar > > things, but have to manually work around this and be careful. One very > > important issue is that if for any reason you allow both of them to be > > up at the same time, and manage the same hosts, they will not know > > about each other, and you'll see lots of confusion and errors. > > > > You might also want to check: > > > > 1. Hosted-engine setup with more than one host as hosted-engine host. > > There, you only have a single engine vm, but it can run on any of your > > hosts. You still have a single VM disk/image, and if that's corrupted, > > you have no HA and have to somehow reinstall/restore/etc. > > > > 2. https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > > > Best regards, > > -- > > Didi > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > > To view the terms under which this email is distributed, please go to:- > > http://leedsbeckett.ac.uk/disclaimer/email/ > > > > -- > Didi > > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ -- Didi

1 0

Guest Agent Warning
by ccesario＠blueit.com.br 11 Nov '19

11 Nov '19

Hello, Does someone has idea about fix/remove the warning message "The latest guest agent needs to be installed and running on the guest" from my VMs ? I already has the qemu agent running and updated on VMS. I already tried restart the VM and HOST but the warning persist. Any tip? My Env. ====== https://pasteboard.co/IDsJZE1.png Warning message ============== https://pasteboard.co/IDsLcNS.png Qemu agent ========== https://pasteboard.co/IDsMmdPp.png Best regards Carlos

4 9

Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by Yedidyah Bar David 11 Nov '19

11 Nov '19

On Mon, Nov 11, 2019 at 12:12 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > I haven't tried it but doesn't engine-setup --offline stop it upgrading minor releases. It prevents only the packager component. If you already have 4.3.6 installed, which was the original question, then engine-setup will still update the database schema. And if it didn't, the 4.3.6 engine might fail working correctly with a 3.4.5.5 database. In particular: The documentation for engine-backup always stated that you must run engine-setup immediately after restore. But at some points in time, and under certain conditions, this was actually optional. You could have done a restore, and immediately start the engine, and it would have worked. But this isn't the case if your restored db is older than the installed engine. Then, you must run engine-setup before starting the engine. Best regards, > > Regards, > Paul S. > ________________________________ > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: 11 November 2019 07:57 > To: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com> > Cc: users <users(a)ovirt.org> > Subject: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5? > > On Tue, Oct 29, 2019 at 11:55 AM <wangyu13476969128(a)126.com> wrote: > > > > The current version of ovirt-engine in production environment is 4.3.5.5. > > In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link: > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > I backed it up using the command: > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes. > > > > According to the relevant links: > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > The ovirt-engine is installed on the standby machine. > > > > After I have executed these three commands: > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > > > 2. yum update > > > > 3. yum install ovirt-engine > > > > I found that the ovirt-engine version of the standby machine is 4.3.6 > > > > So my question is: > > > > 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine: > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)? > > In principle it should be ok. After you restore with above command, > you should run 'engine-setup', and this will update your restored > database schema to 4.3.6. > This is not routinely tested explicitly, though, but I expect that > people often do this, perhaps even unknowingly, when they restore from > a backup taken with a somewhat-old version. > > > > > 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5? > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > 2. yum update > > 3. yum install ovirt-engine > > In theory you can change last one to 'yum install > ovirt-engine-4.3.5.5'. I didn't try that, and you are quite likely to > run into complex dependencies you'll have to satisfy by yourself. > > I think the best solution for you, if you care about active and > standby to be identical, is to upgrade your active one as well, and > keep them same version going forward. > > I'd also like to note that maintaining a standby engine and using it > the way you intend to, is not in the scope of oVirt. People do similar > things, but have to manually work around this and be careful. One very > important issue is that if for any reason you allow both of them to be > up at the same time, and manage the same hosts, they will not know > about each other, and you'll see lots of confusion and errors. > > You might also want to check: > > 1. Hosted-engine setup with more than one host as hosted-engine host. > There, you only have a single engine vm, but it can run on any of your > hosts. You still have a single VM disk/image, and if that's corrupted, > you have no HA and have to somehow reinstall/restore/etc. > > 2. https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > Best regards, > -- > Didi > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ -- Didi

2 1

Supporting larger than 8TiB Lun's iSCSI RHV/oVirt
by Green, Jacob Allen /C 11 Nov '19

11 Nov '19

I have a question regarding the information in the following screenshot. According to https://access.redhat.com/articles/906543 there is an 8TiB limit I assume this is per LUN? Also if I want to go past 8TiB per LUN is there some configuration I need to edit somewhere? And is there a problem with going past 8TiB per LUN? I think it more manageable to simply increase LUN sizes if you have the storage, instead of adding additional LUN’s to your storage domain, however I may not fully understand the problems with increasing LUN sizes. Thank you. [cid:image001.png@01D5948E.D0101740] Jacob.

2 1

After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by wangyu13476969128＠126.com 11 Nov '19

11 Nov '19

The current version of ovirt-engine in production environment is 4.3.5.5. In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link: https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html I backed it up using the command: engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes. According to the relevant links: https://ovirt.org/documentation/install-guide/chap-Installing_oVirt.html The ovirt-engine is installed on the standby machine. After I have executed these three commands: 1. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 2. yum update 3. yum install ovirt-engine I found that the ovirt-engine version of the standby machine is 4.3.6 So my question is: 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine: engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)? 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5? 1. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 2. yum update 3. yum install ovirt-engine

3 2