- Users - oVirt List Archives

Re: Failed to execute stage 'Environment customization': IPAddress() does not support netmasks or subnet prefixes! See documentation for details.
by James Loker-Steele 28 Jul '20

28 Jul '20

Hi Anton, I tried without the /24 it threw an error saying it wasn’t a correct cidr address 10.93.130.50/64 (it added the /64) Interesting though, I have manually created the ovirtmgmt bridge interface and assigned an IP address to it (as per another post) and it has gone past this step now without the /24. The part I am crashing out on is being unable to resolve the address. I can post the error shortly. This is strange behaviour as the host can resolve, but I will be adding dns addresses to the ovirtmgmt interface and trying again(post didn’t show to add them) When I installed <4.2 I didn’t get these issues it went smoothly. The problems seem related to ansible. Best regards James Sent from my iPhone > On 28 Jul 2020, at 07:25, Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > > Hi James, > > You can remove the “/24” prefix after the IP address for the management VM. You will get prompts to add the netmask and gateway after you add the IP address. > > > Anton Louw > Cloud Engineer: Storage and Virtualization at Vox > T: 087 805 0000 | D: 087 805 1572 > M: N/A > E: anton.louw(a)voxtelecom.co.za > A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > > > > > > > > > > > Disclaimer > > The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here. > > > > From: James Loker-Steele via Users <users(a)ovirt.org> > Sent: 27 July 2020 11:36 > To: users(a)ovirt.org > Subject: [ovirt-users] Failed to execute stage 'Environment customization': IPAddress() does not support netmasks or subnet prefixes! See documentation for details. > > Hi All, > Trying to install a self-hosted engine but cannot get past this step. > > [root@<hostname hidden> /]# hosted-engine --deploy > [ INFO ] Stage: Initializing > [ INFO ] Stage: Environment setup > During customization use CTRL-D to abort. > Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine. > The locally running engine will be used to configure a new storage domain and create a VM there. > At the end the disk of the local VM will be moved to the shared storage. > Are you sure you want to continue? (Yes, No)[Yes]: > Configuration files: [] > Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200724164325-fyyler.log > Version: otopi-1.8.3 (otopi-1.8.3-1.el7) > [ INFO ] Stage: Environment packages setup > [ INFO ] Stage: Programs detection > [ INFO ] Stage: Environment setup (late) > [ INFO ] Stage: Environment customization > > --== STORAGE CONFIGURATION ==-- > > > --== HOST NETWORK CONFIGURATION ==-- > > Please indicate the gateway IP address [10.x.x.x]: > [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Detecting interface on existing management bridge] > [ INFO ] TASK [ovirt.hosted_engine_setup : Get all active network interfaces] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Filter bonds with bad naming] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Generate output list] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists] > [ INFO ] skipping: [localhost] > Please indicate a nic to set ovirtmgmt bridge on: (bond0, bond0.130, bond0.60, em1) [em1]: bond0.130 > Please specify which way the network connectivityshould be checked (ping, dns, tcp, none) [dns]: > > --== VM CONFIGURATION ==-- > > Please enter the name of the datacenter where you want to deploy this hosted-engine host. [Default]: > Please enter the name of the cluster where you want to deploy this hosted-engine host. [Default]: > If you want to deploy with a custom engine appliance image, > please specify the path to the OVA archive you would like to use > (leave it empty to skip, the setup will use ovirt-engine-appliance rpm installing it if missing): /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.3-20190926.1.0.5.el7.ova > [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size) > [ INFO ] Checking OVF XML content (could take a few minutes depending on archive size) > Please specify the number of virtual CPUs for the VM (Defaults to appliance OVF value): [4]: > Please specify the memory size of the VM in MB (Defaults to appliance OVF value): [4]: 16384 > [ INFO ] Detecting host timezone. > Please provide the FQDN you would like to use for the engine. > Note: This will be the FQDN of the engine VM you are now going to launch, > it should not point to the base host or to any other existing machine. > Engine VM FQDN: []: <fqdn hidden> > Please provide the domain name you would like to use for the engine appliance. > Engine VM domain: [<tld hidden>] > Enter root password that will be used for the engine appliance: > Confirm appliance root password: > Enter ssh public key for the root user that will be used for the engine appliance (leave it empty to skip): > [WARNING] Skipping appliance root ssh public key > Do you want to enable ssh access for the root user (yes, no, without-password) [yes]: > Do you want to apply a default OpenSCAP security profile (Yes, No) [No]: > You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:3a:4b:fc]: > > How should the engine VM network be configured (DHCP, Static)[DHCP]? static > Please enter the IP address to be used for the engine VM []: 10.93.130.50/24 > [ ERROR ] Failed to execute stage 'Environment customization': IPAddress() does not support netmasks or subnet prefixes! See documentation for details. > [ INFO ] Stage: Clean up > [ INFO ] Cleaning temporary resources > [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch logs from the engine VM] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Set destination directory path] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Create destination directory] > [ INFO ] changed: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Find the local appliance image] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Set local_vm_disk_path] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] > [ INFO ] ok: [localhost -> localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Copy engine logs] > [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] > [ INFO ] ok: [localhost] > [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20200724165204.conf' > [ INFO ] Stage: Pre-termination > [ INFO ] Stage: Termination > [ ERROR ] Hosted Engine deployment failed > Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200724164325-fyyler.log > > > Nothing in log is of much help. > > Also tried to install via Cockpit but gets to prepareVM and displays settings, click next and deployment failed. > No log. > I have tried specifying the OVA and not specifying. > > Anyone can help? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/E676EUG7Y3TQF…

1 1

Failed to execute stage 'Environment customization': IPAddress() does not support netmasks or subnet prefixes! See documentation for details.
by James Loker-Steele 28 Jul '20

28 Jul '20

Hi All, Trying to install a self-hosted engine but cannot get past this step. [root@<hostname hidden> /]# hosted-engine --deploy [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine. The locally running engine will be used to configure a new storage domain and create a VM there. At the end the disk of the local VM will be moved to the shared storage. Are you sure you want to continue? (Yes, No)[Yes]: Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200724164325-fyyler.log Version: otopi-1.8.3 (otopi-1.8.3-1.el7) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup (late) [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- --== HOST NETWORK CONFIGURATION ==-- Please indicate the gateway IP address [10.x.x.x]: [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Detecting interface on existing management bridge] [ INFO ] TASK [ovirt.hosted_engine_setup : Get all active network interfaces] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Filter bonds with bad naming] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Generate output list] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists] [ INFO ] skipping: [localhost] Please indicate a nic to set ovirtmgmt bridge on: (bond0, bond0.130, bond0.60, em1) [em1]: bond0.130 Please specify which way the network connectivityshould be checked (ping, dns, tcp, none) [dns]: --== VM CONFIGURATION ==-- Please enter the name of the datacenter where you want to deploy this hosted-engine host. [Default]: Please enter the name of the cluster where you want to deploy this hosted-engine host. [Default]: If you want to deploy with a custom engine appliance image, please specify the path to the OVA archive you would like to use (leave it empty to skip, the setup will use ovirt-engine-appliance rpm installing it if missing): /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.3-20190926.1.0.5.el7.ova [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size) [ INFO ] Checking OVF XML content (could take a few minutes depending on archive size) Please specify the number of virtual CPUs for the VM (Defaults to appliance OVF value): [4]: Please specify the memory size of the VM in MB (Defaults to appliance OVF value): [4]: 16384 [ INFO ] Detecting host timezone. Please provide the FQDN you would like to use for the engine. Note: This will be the FQDN of the engine VM you are now going to launch, it should not point to the base host or to any other existing machine. Engine VM FQDN: []: <fqdn hidden> Please provide the domain name you would like to use for the engine appliance. Engine VM domain: [<tld hidden>] Enter root password that will be used for the engine appliance: Confirm appliance root password: Enter ssh public key for the root user that will be used for the engine appliance (leave it empty to skip): [WARNING] Skipping appliance root ssh public key Do you want to enable ssh access for the root user (yes, no, without-password) [yes]: Do you want to apply a default OpenSCAP security profile (Yes, No) [No]: You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:3a:4b:fc]: How should the engine VM network be configured (DHCP, Static)[DHCP]? static Please enter the IP address to be used for the engine VM []: 10.93.130.50/24 [ ERROR ] Failed to execute stage 'Environment customization': IPAddress() does not support netmasks or subnet prefixes! See documentation for details. [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20200724165204.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200724164325-fyyler.log Nothing in log is of much help. Also tried to install via Cockpit but gets to prepareVM and displays settings, click next and deployment failed. No log. I have tried specifying the OVA and not specifying. Anyone can help?

2 1

Adding hypervisor fails, yum links deprecated (Centos 7.7/ oVirt 4.3)
by wjb2130＠cumc.columbia.edu 28 Jul '20

28 Jul '20

Greetings. In a multi-hypervisor environment, we are running Centos 7.7.1908, with ovirt-4.3. There are problems adding a new hypervisor, because all the yum resources have switched in favor of newer versions. Is there a proceedure to add a hypervisor under the oVirt Virtualization manager while retaining an older, known working OS version like Centos 7.7.1908 ? Upgrading everything across the board isn't an immediate option. There are many VMs and hypervisors in production, and can't be disturbed. In sum: is it still possible to install known working 4.30.33-1.el7? All that is presented now is 4.30.46-1.el7 I ran: yum install vdsm-4.30.33-1.el7.x86_64. This completed. However, when I tried to add the resulting hypservisor using the oVirt web UI, that fails. Logs on that management server showed that the install process insists on using 4.30.46-1.el7. Any way to avoid this? 2020-07-22 20:30:58,621-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [45782a5f] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host hypervisor7: Failed to execute stage 'Package installation': [u'vdsm-4.30.46-1.el7.x86_64 requires lvm2 >= 7:2.02.186-7.el7_8.1'].

2 1

change lun for hosted_engine use?
by Philip Brown 28 Jul '20

28 Jul '20

I currently have a self-hosted engine, running in a dedicated ISCSI storage domain. I'd like to change the backend hardware for the storage. i think there's some longwinded and complicated method of shutting down the engine, backup, creating a NEW one, restore, and whoknowswhat. I was wondering though, if maybe there's a way to just add an iscsi lun to the storage domain, and tell ovirt, "Hey, move the stuff over to that other lun" ? Ive added the new lun already :) havent found a reference to move the files' residence though. If it helps, my end goal is to remove that lun completely. -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

2 3

Deploying new Ovirt Node on new 4.4 cluster. ansible code incorrect
by erin.sims＠bookit.com 27 Jul '20

27 Jul '20

Hi Guys we attempted to deploy a new ovirt cluster two weeks ago. 4.4.1 and 4.4.0 Once we got the engine up we tried to add a new node and Ansible began to fail on the deploy scripts. I search the logs and discovered the Ansible script was not evaluating the right versions of python, python3. Also the yum module should of been dnf. Once i change those in many places it worked great. I am just trying to figure out what went wrong with our deploy so this doesn't happen again. we are using a hosted engine on a centos 8 vm. please let me know what logs i can grab or apps to run for more details. details: engine: [root@ovirt ~]# uname -a Linux ovirt.ism.ld 4.18.0-193.6.3.el8_2.x86_64 #1 SMP Wed Jun 10 11:09:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@ovirt ~]# cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) [root@ovirt ~]# uname -a Linux ovirt.ism.ld 4.18.0-193.6.3.el8_2.x86_64 #1 SMP Wed Jun 10 11:09:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@ovirt ~]# cat /etc/os-release NAME="CentOS Linux" VERSION="8 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Linux 8 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" node2: CENTOS_MANTISBT_PROJECT="CentOS-8" CENTOS_MANTISBT_PROJECT_VERSION="8" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="8" [root@web2 ~]# cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) [root@web2 ~]# cat /etc/os-release NAME="CentOS Linux" VERSION="8 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" VARIANT="oVirt Node 4.4.1.1" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.4.1.1" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8" [root@web2 ~]# uname -a Linux web2.ism.ld 4.18.0-193.6.3.el8_2.x86_64 #1 SMP Wed Jun 10 11:09:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@web2 ~]# cat /etc/os-release NAME="CentOS Linux" VERSION="8 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" VARIANT="oVirt Node 4.4.1.1" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.4.1.1" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8" [root@web2 ~]# cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) node1: [root@web1 ~]# uname -a Linux web1.ism.ld 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Thu Apr 9 13:49:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [root@web1 ~]# dnf update CentOS-8 - Gluster 7 0.0 B/s | 0 B 00:00 Failed to download metadata for repo 'ovirt-4.4-centos-gluster7' Error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster7' [root@web1 ~]# cat /etc/centos-release CentOS Linux release 8.1.1911 (Core) [root@web1 ~]# cat /etc/os-release NAME="CentOS Linux" VERSION="8 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" VARIANT="oVirt Node 4.4.0" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.4.0" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8"

2 2

Centos based Ovirt 4.3.10.4-1.el7, VMs cannot communicate over VM networks
by Konstantinos B 27 Jul '20

27 Jul '20

Hi all Can anyone point into the right direction on how to troubleshoot VM connectivity between VM networks? The nodes have been double-installed from the engine. The external ovn-provider is reachable through HTTP. ovs-vsctl shows the interfaces once a VM is booted. However, no traffic is passed between VMs. Any help is greatly appreciated.

2 1

problem with custom bond options
by Jiří Sléžka 27 Jul '20

27 Jul '20

Hello, CentOS8, oVirt 4.4.1.10-1.el8 I am trying to setup active-backup (mode=1) bonding mode with custom properties. I have one 10GE switch, the second is just 1G. 10GE link is the primary one. cat /etc/sysconfig/network-scripts/ifcfg-bond0 BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100 mode=active-backup primary=ens5 updelay=0" TYPE=Bond BONDING_MASTER=yes PROXY_METHOD=none BROWSER_ONLY=no IPV4_FAILURE_FATAL=no IPV6_DISABLED=yes IPV6INIT=no NAME=bond0 UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7 DEVICE=bond0 ONBOOT=yes MTU=9000 When I try to add a custom parameter "fail_over_mac=active" (which I believe could solve my problems with stalled mac addresses in switch's cam table in case of failover) I got... "Error while executing action HostSetupNetworks: Unexpected exception" ...in manager. In the engine.log it looks like 2020-07-22 21:20:35,774+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': 'MAC address cannot be specified in bond interface along with specified bond options'}] 2020-07-22 21:20:35,774+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Failed in 'HostSetupNetworksVDS' method 2020-07-22 21:20:35,774+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': 'MAC address cannot be specified in bond interface along with specified bond options'}] 2020-07-22 21:20:35,811+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-hci01.mch.local command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': 'MAC address cannot be specified in bond interface along with specified bond options'} Could anybody explain me what 'MAC address cannot be specified in bond interface along with specified bond options' means? I believe a MAC address is not configured in interface configuration. Or does it mean 'fail_over_mac=active' is not supported in oVirt? Thanks in advance, Jiri

3 12

Re: Ovirt SYSTEM user does not allow deletion of VM networks
by Konstantinos B 25 Jul '20

25 Jul '20

I've deleted them from the cluster as well but re-appear. I've removed ovirt-engine through engine-cleanup installed again and they reappear. Removed ovirt-engine deleted all "ovirt*" files and currenty trying to re-install. I've checked the host's ovs-vsctl bridges and only the desired are shown. So i believe it's an issue on the engine itself.

3 3

Shutdown procedure for single host HCI Gluster
by Gianluca Cecchi 25 Jul '20

25 Jul '20

Hello, I'm testing the single node HCI with ovirt-node-ng 4.3.9 iso. Very nice and many improvements over the last time I tried it. Good! I have a doubt related to shutdown procedure of the server. Here below my steps: - Shutdown all VMs (except engine) - Put into maintenance data and vmstore domains - Enable Global HA Maintenance - Shutdown engine - Shutdown hypervisor It seems that the last step doesn't end and I had to brutally power off the hypervisor. Here the screenshot regarding infinite failure in unmounting /gluster_bricks/engine https://drive.google.com/file/d/1ee0HG21XmYVA0t7LYo5hcFx1iLxZdZ-E/view?usp=… What would be the right step to do before the final shutdown of hypervisor? Thanks, Gianluca

3 10

RDP
by eevans＠digitaldatatechs.com 24 Jul '20

24 Jul '20

I am using Ovirt 4.3. I followed the instructions for get RDP to work for a user, but admin@internal is the only user the RDP will launch for. The other test users I created and are added to the Remote Desktop Users group which is the permission I assigned to the VM's as well as the user name. I added users first, then the group to see if it would help. So far, admin@internal, the Ovirt admin user, is the only user RDP will work for. I know I am missing something, I'm just not sure what. Any help would be appreciated. Eric.

3 4

very very bad iscsi performance
by Philip Brown 24 Jul '20

24 Jul '20

I'm trying to get optimal iscsi performance. We're a heavy iscsi shop, with 10g net. I'mm experimenting with SSDs, and the performance in ovirt is way, way less than I would have hoped. More than an order of magnitude slower. here's a datapoint. Im running filebench, with the OLTP workload. First, i run it on one of the hosts, that has an SSD directly attached. create an xfs filesystem (created on a vg "device" on top of the SSD), mount it with noatime, and run the benchmark. 37166: 74.084: IO Summary: 3746362 ops, 62421.629 ops/s, (31053/31049 r/w), 123.6mb/s, 161us cpu/op, 1.1ms latency I then unmount it, and make the exact same device an iscsi target, and create a storage domain with it. I then create a disk for a VM running *on the same host*, and run the benchmark. The same thing: filebench, oltp workload, xfs filesystem, noatime. 13329: 91.728: IO Summary: 153548 ops, 2520.561 ops/s, (1265/1243 r/w), 4.9mb/s, 289us cpu/op, 88.4ms latency 62,000 ops/s vs 2500 ops/s. what???? Someone might be tempted to say, "try making the device directly available, AS a device, to the VM". Unfortunately,this is not an option. My goal is specifically to put together a new, high performing storage domain, that I can use as database devices in VMs. I'm not expecting the same 62,000 ops/second. but I was expecting at *least* 5,000. Ideally more like 10,000. -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

5 13

qemu-guest-agent on Ubuntu doesn't report FQDN
by Florian Schmid 24 Jul '20

24 Jul '20

Hi, I have a problem with Ubuntu 20.04 VM reporting the correct FQDN to the engine. Starting with this release, the ovirt-guest-agent is not available anymore. Therefore, I have installed qemu-geust-agent with package defaults. Now in the Engine, I only see the hostname under FQDN tab, instead the real full name with domain. I'm running an oVirt environment on 4.3.8. The VM is resolveable, forward and reverse DNS entries are working. hostname -f shows the correct FQDN. Even adding IP and FQDN to /etc/hosts file doesn't change anything. qemu-guest-agent version: 4.2-3ubuntu6.3 I manage this VM via ansible 2.9 and ansible is able to get the FQDN of the VM without any issues... What can I do here to debug my issue? Does the engine cache the wrong result? Even after stopping and starting the VM again, engine is only showing the hostname instead of the FQDN. Best regards, Florian

5 10

Problem with paused VMs in ovirt 4.3.10.
by Damien 24 Jul '20

24 Jul '20

Hi! We have a problem with paused VMs in ovirt cluster. Please, help to solve this. In ovirt manager massege "VM rtb-stagedsw02-ovh has been paused." Resume fails with error "Failed to resume VM rtb-stagedsw02-ovh (Host: ovirt-node09-ovh.local, User: admin@internal-authz)." In oVirt Cluster 38 VM, paused VM only ubuntu 20.04 focal with docker swarm. Archived logs in attach. Packeges on ovirt nodes: python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-provider-ovn-driver-1.2.29-1.el7.noarch ovirt-vmconsole-host-1.0.7-2.el7.noarch python2-ovirt-host-deploy-1.8.5-1.el7.noarch ovirt-imageio-common-1.5.3-0.el7.x86_64 cockpit-machines-ovirt-195.6-1.el7.centos.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-host-dependencies-4.3.5-1.el7.x86_64 ovirt-host-4.3.5-1.el7.x86_64 python-ovirt-engine-sdk4-4.3.4-2.el7.x86_64 ovirt-host-deploy-common-1.8.5-1.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-hosted-engine-setup-2.3.13-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-imageio-daemon-1.5.3-0.el7.noarch cockpit-ovirt-dashboard-0.13.10-1.el7.noarch ovirt-release43-4.3.10-1.el7.noarch ovirt-hosted-engine-ha-2.3.6-1.el7.noarch Packeges on HostedEngine: ovirt-ansible-infra-1.1.13-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.3.10.4-1.el7.noarch ovirt-engine-websocket-proxy-4.3.10.4-1.el7.noarch ovirt-engine-restapi-4.3.10.4-1.el7.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-iso-uploader-4.3.2-1.el7.noarch ovirt-provider-ovn-1.2.29-1.el7.noarch ovirt-imageio-proxy-setup-1.5.3-0.el7.noarch ovirt-engine-extension-aaa-ldap-setup-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.10.4-1.el7.noarch python-ovirt-engine-sdk4-4.3.4-2.el7.x86_64 python2-ovirt-host-deploy-1.8.5-1.el7.noarch ovirt-ansible-vm-infra-1.1.22-1.el7.noarch ovirt-engine-metrics-1.3.7-1.el7.noarch ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch ovirt-engine-wildfly-overlay-17.0.1-1.el7.noarch ovirt-ansible-roles-1.1.7-1.el7.noarch ovirt-engine-dwh-setup-4.3.8-1.el7.noarch python2-ovirt-engine-lib-4.3.10.4-1.el7.noarch ovirt-engine-extension-aaa-ldap-1.3.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.10.4-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.10.4-1.el7.noarch ovirt-engine-tools-backup-4.3.10.4-1.el7.noarch ovirt-engine-webadmin-portal-4.3.10.4-1.el7.noarch ovirt-host-deploy-common-1.8.5-1.el7.noarch ovirt-ansible-image-template-1.1.12-1.el7.noarch ovirt-ansible-manageiq-1.1.14-1.el7.noarch ovirt-engine-wildfly-17.0.1-1.el7.x86_64 ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch ovirt-imageio-common-1.5.3-0.el7.x86_64 ovirt-imageio-proxy-1.5.3-0.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch ovirt-vmconsole-proxy-1.0.7-2.el7.noarch ovirt-engine-setup-base-4.3.10.4-1.el7.noarch ovirt-engine-setup-plugin-cinderlib-4.3.10.4-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.10.4-1.el7.noarch ovirt-release43-4.3.10-1.el7.noarch ovirt-engine-backend-4.3.10.4-1.el7.noarch ovirt-engine-tools-4.3.10.4-1.el7.noarch ovirt-web-ui-1.6.0-1.el7.noarch ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-ui-extensions-1.0.10-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.10.4-1.el7.noarch ovirt-engine-4.3.10.4-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch ovirt-host-deploy-java-1.8.5-1.el7.noarch ovirt-engine-dwh-4.3.8-1.el7.noarch ovirt-engine-api-explorer-0.0.5-1.el7.noarch ovirt-guest-agent-common-1.0.16-1.el7.noarch ovirt-engine-setup-4.3.10.4-1.el7.noarch ovirt-engine-dbscripts-4.3.10.4-1.el7.noarch In /var/log/ovirt-engine/engine.log: 2020-07-24 09:38:44,472+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] VM '18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99'(rtb-stagedsw02-ovh) move d from 'Up' --> 'Paused' 2020-07-24 09:38:44,493+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] EVENT_ID: VM_PAUSED(1,025), VM rtb-stagedsw02-ovh has been paused. In /var/log/vdsm/vdsm.log 2020-07-24 09:38:42,771+0300 INFO (libvirt/events) [virt.vm] (vmId='18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99') CPU stopped: onSuspend (vm:6100) 2020-07-24 09:38:44,328+0300 INFO (jsonrpc/1) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0}, 'io_tune_policies_dict': {'4d9519f6-1ab9-4032-8fdf-4c6118531544': {'poli cy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glust erSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/images/e1cfb9ec-39d8-416d-9f5f-0b54765301d4/8f95d60d-931b-4764-993c-ba9373efe361', 'name': 'sda'}]}, 'b031a269-6bcd-40b7-9737-e47112a54b3a': {'po licy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glu sterSD/10.0.11.101:_vmstore01/5e05fed3-448b-4f86-b5ba-004982194c90/images/9c3cc7a0-254e-4756-91b6-fb54e21abf38/71dd8024-8aec-46da-a80f-34260655e929', 'name': 'sda'}, {'ioTune': {'write_bytes_sec': 0L, 'total_io ps_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glusterSD/10.0.11.101:_vmstore01/5e05fed3-448b-4f86-b5ba-004982194c90/images/ 3e3a5064-5fe1-40c0-81f5-44f1a3a4d503/13549972-82de-4746-aeea-3e1531f9c180', 'name': 'sdb'}]}, 'b5fad17c-fa9d-4a80-99e7-6f86e6e19c9b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_ iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/image s/15ce6cb0-6f06-4a31-92d8-b6e1bcabf3bc/613de344-d1ad-49aa-a2d0-d60ca9eb7cd3', 'name': 'sda'}]}, '18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'tota l_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': u'/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/im ages/7978e2db-c560-4315-a775-223f1b13ae31/d927eea8-e588-449e-b07b-c845d15b082e', 'name': 'sda'}, {'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_s ec': 0L, 'total_bytes_sec': 0L}, 'path': u'/rhev/data-center/mnt/glusterSD/10.0.11.107:_vmstore02/16c5070c-cc5f-4595-965f-66838c7c17a5/images/b925dc2e-17ba-470d-a9be-cb96d4ef1f0d/951d9712-7160-4f88-a838-970aec8 2b3ea', 'name': 'sdb'}]}}} from=::1,34598 (api:54) 2020-07-24 09:38:49,747+0300 WARN (qgapoller/1) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7fe5c84de6e0> on ['18f6bb79-ba9b-4a0e-bcb2-b4ef4904ef99'] (periodic:289) In /var/log/libvirt/qemu/rtb-stagedsw03-ovh.log KVM: entry failed, hardware error 0x80000021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=00001000 EBX=43117da8 ECX=0000000c EDX=00000121 ESI=00000003 EDI=17921000 EBP=43117cb0 ESP=43117c98 EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES =0000 00000000 ffffffff 00809300 CS =9b00 7ff9b000 ffffffff 00809300 SS =0000 00000000 ffffffff 00809300 DS =0000 00000000 ffffffff 00809300 FS =0000 00000000 ffffffff 00809300 GS =0000 00000000 ffffffff 00809300 LDT=0000 00000000 000fffff 00000000 TR =0040 001ce000 0000206f 00008b00 GDT= 001cc000 0000007f IDT= 00000000 00000000 CR0=00050032 CR2=17921000 CR3=2b92a003 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000fffe0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff <ff> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

1 0

iSCSI multipath with separate subnets... still not possible in 4.4.x?
by Mark R 24 Jul '20

24 Jul '20

I'm looking through quite a few bug reports and mailing list threads, but want to make sure I'm not missing some recent development. It appears that doing iSCSI with two separate, non-routed subnets is still not possible with 4.4.x. I have the dead-standard iSCSI setup with two separate switches, separate interfaces on hosts and storage, and separate subnets that have no gateway and are completely unreachable except from directly attached interfaces. The hosted-engine comes up with multiple paths and everything is perfect, but that's because Ansible/hosted-engine deploy script have configured things correctly. Once you need to import or add new storage domains, it's not possible to do so in a way that gets both paths connected *and* persists across host reboots. Following the docs to create 'iSCSI Multipath" bonds (plural, you can _not_ create a single bond that includes both interfaces and hope things route correctly... oVirt will try to connect from the interface for storage network A to the target on storage network B, which can't happen since they are not routed (and should not be). So, there's nothing in the docs about how you can accomplish multipathing, but there are a few mailing list messages that say "just create two separate "iSCSI Multipath" bonds in the datacenter, one for each of your two interfaces. You can do this, and you'll get hopeful that things might work now. You can do discovery and it succeeds, because no more trying to connect to unreachable targets. However, and big caveat, there's no way to tell this new/imported domain, "Oh, use this other interface as well, so you have redundant paths". Once the domain is attached and activated, you have a single path. You can then manage the domain, do a discovery, see a path that isn't connected yet, and log into it as well. Now you have two paths, is everything right with the world?!? Nope, it's impossible to persist that connection, it will be gone on next reboot and you'll always have to manually visit each host, do discovery, and login. Nothing in the UI allows you to "Save" that second connection in a way that it will be used again. Clicking "OK" does not, and going back to the "iSCSI Multipath" area of the Data Center you can't edit each of the bonds and make sure each logical network has every possible target checked, because these targets you've manually logged into are never listed in that area of the UI. So I really, really hope I'm wrong because I'd like to move past this snag and onto the next one (which is that bond interfaces in 4.4.x will not allow you to attach additional networks... works great in 4.3, appears broken in 4.4.x). But, no sense chasing that yet if iSCSI multipath isn't possible, which is looking likely. Has anyone had success, running iSCSI in by far the most common setup out there, but also in a way oVirt really doesn't want to let you? This is driving me nuts, I've paved and rebuilt these hosts dozens of times now, trying different methods in the hopes of getting multipath that persists.

6 7

Hosted Engine 4.4.1
by Vijay Sachdeva 24 Jul '20

24 Jul '20

Hello Everyone, Waiting for host to be up task is stuck for hours and when checked engine log found this below: 2020-07-22 16:50:35,717+02 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-1) [] OAuthException access_denied: Cannot authenticate user 'None@N/A': No valid profile found in credentials.. Has anyone faced such issue then please help me out..!! Thanks Vijay Sachdeva

2 4

Re: oVirt 4.3 ssh passwordless setup guide
by Strahil Nikolov 24 Jul '20

24 Jul '20

You need to keep the ssh root access from the engine , so you will need a 'Match' stanza for the engine. Of course testing is very important, but in case you got no test setup - you can set a node in maintenance and experiment a little bit. Best Regards, Strahil Nikolov На 23 юли 2020 г. 21:29:06 GMT+03:00, "Morris, Roy" <roy.morris(a)ventura.org> написа: >Hello, > >Does anyone have a guide or how to on setting up oVirt with >passwordless ssh setup? I want to do this with a production environment >to improve security but I have never done this before and want to build >a test environment to try it out. > >Best regards, >Roy Morris

1 0

oVirt 4.3 ssh passwordless setup guide
by Morris, Roy 23 Jul '20

23 Jul '20

Hello, Does anyone have a guide or how to on setting up oVirt with passwordless ssh setup? I want to do this with a production environment to improve security but I have never done this before and want to build a test environment to try it out. Best regards, Roy Morris

1 0

Upgrade from 4.3 to 4.4 fails with db or user ovirt_engine_history already exists
by wilderink＠triplon.nl 23 Jul '20

23 Jul '20

Currently, our upgrade to 4.4 fails with error: FATAL: Existing database 'ovirt_engine_history' or user 'ovirt_engine_history' found and temporary ones created We have upgraded the running 4.3 installation to the latest version and also use the latest packages for the upgrade on the new CentOS 8.2 installation. The back-up is made following the Hosted Engine upgrade steps in the manual, using: `engine-backup --scope=all --mode=backup --file=backup.bck --log=backuplog.log` The upgrade is performed after copying the backup.bck file to the new server and using `hosted-engine --deploy --restore-from-file=backup.bck` After creating the Engine VM, the installation process hangs when the backup is restored. We tried it several times, using a complete or a partial back-up. Old/current oVirt version: 4.3.10.4-1.el7 New version: 4.4.1.8 ovirt-ansible-hosted-engine-setup: 1.1.6 Did anyone get the same error while upgrading an existing installation? Thanks! Error log Ansible on Host: 2020-07-15 12:34:09,361+0200 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Run engine-backup] 2020-07-15 12:35:28,778+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': 'non-zero return code', 'cmd': 'engine-backup --mode=restore --log=/var/log/ovirt-engine/setup/restore-backup-$(date -u +%Y%m%d%H%M%S).log --file=/root/engine_backup --provision-all-databases --restore-permissions', 'stdout': "Start of engine-backup with mode 'restore'\nscope: all\narchive file: /root/engine_backup\nlog file: /var/log/ovirt-engine/setup/restore-backup-20200715103410.log\nPreparing to restore:\n- Unpacking file '/root/engine_backup'\nRestoring:\n- Files\n------------------------------------------------------------------------------\nPlease note:\n\nOperating system is different from the one used during backup.\nCurrent operating system: centos8\nOperating system at backup: centos7\n\nApache httpd configuration will not be restored.\nYou will be asked about it on the next engine-setup run.\n---------------------------------------------------------- --------------------\nProvisioning PostgreSQL users/databases:\n- user 'engine', database 'engine'\n- extra user 'ovirt_engine_history' having grants on database engine, created with a random password\n- user 'ovirt_engine_history', database 'ovirt_engine_history'", 'stderr': "FATAL: Existing database 'ovirt_engine_history' or user 'ovirt_engine_history' found and temporary ones created - Please clean up everything and try again", 'rc': 1, 'start': '2020-07-15 12:34:10.824630', 'end': '2020-07-15 12:35:28.488261', 'delta': '0:01:17.663631', 'changed': True, 'invocation': {'module_args': {'_raw_params': 'engine-backup --mode=restore --log=/var/log/ovirt-engine/setup/restore-backup-$(date -u +%Y%m%d%H%M%S).log --file=/root/engine_backup --provision-all-databases --restore-permissions', '_uses_shell': True, 'warn': True, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines' : ["Start of engine-backup with mode 'restore'", 'scope: all', 'archive file: /root/engine_backup', 'log file: /var/log/ovirt-engine/setup/restore-backup-20200715103410.log', 'Preparing to restore:', "- Unpacking file '/root/engine_backup'", 'Restoring:', '- Files', '------------------------------------------------------------------------------', 'Please note:', '', 'Operating system is different from the one used during backup.', 'Current operating system: centos8', 'Operating system at backup: centos7', '', 'Apache httpd configuration will not be restored.', 'You will be asked about it on the next engine-setup run.', '------------------------------------------------------------------------------', 'Provisioning PostgreSQL users/databases:', "- user 'engine', database 'engine'", "- extra user 'ovirt_engine_history' having grants on database engine, created with a random password", "- user 'ovirt_engine_history', database 'ovirt_engine_history'"], 'stderr_lines': ["FATAL: Existing d atabase 'ovirt_engine_history' or user 'ovirt_engine_history' found and temporary ones created - Please clean up everything and try again"], '_ansible_no_log': False, '_ansible_delegated_vars': {'ansible_host': 'ovirt-management.dc1.triplon', 'ansible_port': None, 'ansible_user': 'root'}} 2020-07-15 12:35:28,879+0200 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost -> ovirt-management.dc1.triplon]: FAILED! => {"changed": true, "cmd": "engine-backup --mode=restore --log=/var/log/ovirt-engine/setup/restore-backup-$(date -u +%Y%m%d%H%M%S).log --file=/root/engine_backup --provision-all-databases --restore-permissions", "delta": "0:01:17.663631", "end": "2020-07-15 12:35:28.488261", "msg": "non-zero return code", "rc": 1, "start": "2020-07-15 12:34:10.824630", "stderr": "FATAL: Existing database 'ovirt_engine_history' or user 'ovirt_engine_history' found and temporary ones created - Please clean up everything and try again", "stderr_lines": ["FATAL: Existing database 'ovirt_engine_history' or user 'ovirt_engine_history' found and temporary ones created - Please clean up everything and try again"], "stdout": "Start of engine-backup with mode 'restore'\nscope: all\narchive file: /root/engine_backup\nlog file: /var/log/ov irt-engine/setup/restore-backup-20200715103410.log\nPreparing to restore:\n- Unpacking file '/root/engine_backup'\nRestoring:\n- Files\n------------------------------------------------------------------------------\nPlease note:\n\nOperating system is different from the one used during backup.\nCurrent operating system: centos8\nOperating system at backup: centos7\n\nApache httpd configuration will not be restored.\nYou will be asked about it on the next engine-setup run.\n------------------------------------------------------------------------------\nProvisioning PostgreSQL users/databases:\n- user 'engine', database 'engine'\n- extra user 'ovirt_engine_history' having grants on database engine, created with a random password\n- user 'ovirt_engine_history', database 'ovirt_engine_history'", "stdout_lines": ["Start of engine-backup with mode 'restore'", "scope: all", "archive file: /root/engine_backup", "log file: /var/log/ovirt-engine/setup/restore-backup-20200715103410.log", "Prep aring to restore:", "- Unpacking file '/root/engine_backup'", "Restoring:", "- Files", "------------------------------------------------------------------------------", "Please note:", "", "Operating system is different from the one used during backup.", "Current operating system: centos8", "Operating system at backup: centos7", "", "Apache httpd configuration will not be restored.", "You will be asked about it on the next engine-setup run.", "------------------------------------------------------------------------------", "Provisioning PostgreSQL users/databases:", "- user 'engine', database 'engine'", "- extra user 'ovirt_engine_history' having grants on database engine, created with a random password", "- user 'ovirt_engine_history', database 'ovirt_engine_history'"]} restore-backup-xx.log file on the created Hosted Engine (retrieved by Ansible after failing): 2020-07-15 15:57:36 6437: Start of engine-backup mode restore scope all file /root/engine_backup 2020-07-15 15:57:36 6437: OUTPUT: Start of engine-backup with mode 'restore' 2020-07-15 15:57:36 6437: OUTPUT: scope: all 2020-07-15 15:57:36 6437: OUTPUT: archive file: /root/engine_backup 2020-07-15 15:57:36 6437: OUTPUT: log file: /var/log/ovirt-engine/setup/restore-backup-20200715135736.log 2020-07-15 15:57:36 6437: OUTPUT: Preparing to restore: 2020-07-15 15:57:36 6437: OUTPUT: - Unpacking file '/root/engine_backup' 2020-07-15 15:57:36 6437: Opening tarball /root/engine_backup to /tmp/engine-backup.5tvwGDx3qs 2020-07-15 15:57:37 6437: Verifying hash 2020-07-15 15:57:37 6437: Verifying version 2020-07-15 15:57:37 6437: Reading config 2020-07-15 15:57:37 6437: OUTPUT: Restoring: 2020-07-15 15:57:37 6437: OUTPUT: - Files 2020-07-15 15:57:37 6437: Restoring files 2020-07-15 15:57:38 6437: Reloading configuration 2020-07-15 15:57:38 6437: OUTPUT: Provisioning PostgreSQL users/databases: 2020-07-15 15:57:38 6437: provisionDB: user engine host localhost port 5432 database engine secured False secured_host_validation False 2020-07-15 15:57:38 6437: OUTPUT: - user 'engine', database 'engine' [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, /tmp/engine-backup.5tvwGDx3qs/pg-provision-answer-file Log file: /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20200715155739-3o20a7.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration (early) [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Initializing PostgreSQL [ INFO ] Creating PostgreSQL 'engine' database [ INFO ] Configuring PostgreSQL [ INFO ] Install selinux module /usr/share/ovirt-engine/selinux/ansible-runner-service.cil [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20200715155739-3o20a7.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of provisiondb completed successfully 2020-07-15 15:58:14 6437: OUTPUT: - extra user 'ovirt_engine_history' having grants on database engine, created with a random password [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, /tmp/engine-backup.5tvwGDx3qs/pg-provision-answer-file Log file: /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20200715155815-j4ba3l.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration (early) [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Install selinux module /usr/share/ovirt-engine/selinux/ansible-runner-service.cil [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20200715155815-j4ba3l.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of provisiondb completed successfully 2020-07-15 15:58:46 6437: provisionDB: user ovirt_engine_history host localhost port 5432 database ovirt_engine_history secured False secured_host_validation False 2020-07-15 15:58:46 6437: OUTPUT: - user 'ovirt_engine_history', database 'ovirt_engine_history' [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, /tmp/engine-backup.5tvwGDx3qs/pg-provision-answer-file Log file: /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20200715155847-qk7ipy.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment customization [ INFO ] Stage: Setup validation [ INFO ] Stage: Transaction setup [ INFO ] Stage: Misc configuration (early) [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Creating PostgreSQL 'ovirt_engine_history' database [ INFO ] Configuring PostgreSQL [ ERROR ] Failed to execute stage 'Misc configuration': Existing resources found, new ones created: database ovirt_engine_history_20200715155850 user ovirt_engine_history_20200715155850 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-provisiondb-20200715155847-qk7ipy.log [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of provisiondb failed 2020-07-15 15:58:52 6437: FATAL: Existing database 'ovirt_engine_history' or user 'ovirt_engine_history' found and temporary ones created - Please clean up everything and try again

3 4

Hosted Engine Ovirt 4.3.8
by Vijay Sachdeva 23 Jul '20

23 Jul '20

Hi Everyone, Does anyone has any idea why hosted engine setup stuck at “Wait for host to be up”. It’s been 4 hours deployment is going on and got stuck. Any help please..!! Thanks Vijay Sachdeva

2 1

oVirt 4.4 Engine data migration & GUI notes
by Andrei Verovski 23 Jul '20

23 Jul '20

Hi ! I have installed new oVirt 4.4 Engine (as separate entity, not hosted engine) and migrated data from old 4.3 installation. Everything went smooth. Q: Which PostgreSQL password now active - new one I entered during install or old which could migrate with old data? I noticed GUI changes straight on dashboard. Icons on top (data centres, clusters, hosts, etc) are simply put, too huge. This serves no useful purpose whatsoever, and consumes screen real estate for no reason. Decreasing their size by 2/3 will help to make 1st page more informative at 1st sight without extra scrolling. with best regards Andrei

3 4

HostedEngine start error: could not find capabilities for arch=x86_64 domaintype=kvm
by Gianluca Cecchi 23 Jul '20

23 Jul '20

Hello, I'm importing a VM into a new oVirt environment that is in 4.3.10: the new host is the same as the previous one (only difference it is in 4.3.10 while the old one in 4.3.9). This VM acted as a single host HCI environment (with 4.3.9). I imported the storage domain containing the VM and its disks and the VM boots ok. Now its Hosted Engine VM (that is so a nested VM) doesn't start. I think it was good when I stopped/detached it... and so I would like to cross check and verify if I missed something configuring the new environment or something changed from 4.3.9 to 4.3.10 In vdsm.log I see this reason: 2020-07-23 14:38:20,489+0200 ERROR (vm/9233dc8b) [virt.vm] (vmId='9233dc8b-7a4d-4fac-8551-dc7407f36548') The vm start process failed (vm: 934) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 868, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2892, in _run dom = self._connection.defineXML(self._domain.xml) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3743, in defineXML if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self) libvirtError: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm The relevant parts of the generated xml in vdsm.log seems: 2020-07-23 14:38:20,487+0200 INFO (vm/9233dc8b) [virt.vm] (vmId='9233dc8b-7a4d-4fac-8551-dc7407f36548') <?xml version="1.0" encoding="ut f-8"?><domain type="kvm" xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <name>HostedEngine</name> <uuid>9233dc8b-7a4d-4fac-8551-dc7407f36548</uuid> <memory>16777216</memory> <currentMemory>16777216</currentMemory> <iothreads>1</iothreads> <maxMemory slots="16">67108864</maxMemory> <vcpu current="2">32</vcpu> <sysinfo type="smbios"> <system> <entry name="manufacturer">oVirt</entry> <entry name="product">oVirt Node</entry> <entry name="version">7-7.1908.0.el7.centos</entry> <entry name="serial">704e1338-5dec-46f8-a186-8c2080dcefd8</entry> <entry name="uuid">9233dc8b-7a4d-4fac-8551-dc7407f36548</entry> </system> </sysinfo> <clock adjustment="0" offset="variable"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <features> <acpi/> </features> <cpu match="exact"> <model>Skylake-Server</model> <feature name="spec-ctrl" policy="require"/> <feature name="ssbd" policy="require"/> <feature name="md-clear" policy="require"/> <topology cores="2" sockets="16" threads="1"/> <numa> <cell cpus="0,1" id="0" memory="16777216"/> </numa> </cpu> <cputune/> ... </metadata> <on_poweroff>destroy</on_poweroff><on_reboot>destroy</on_reboot><on_crash>destroy</on_crash></domain> (vm:2890) Any insights? The configuration of the new 4.3.10 physical oVirt environment that contains the VM has this cluster cpu type: Intel Skylake Server IBRS SSBD MDS Family Do I have to change it to anything else? I don't remember how it was set in 4.3.9 Thanks in advance, Gianluca

1 1

Re: [moVirt] New ovirt 4.4.0.3-1.el8 leaves disks in illegal state on all snapshot actions
by Tomas Jelinek 23 Jul '20

23 Jul '20

forwarding to the correct list On Wed, Jul 22, 2020 at 5:15 PM Henri Aanstoot <fash(a)fash.nu> wrote: > Hi all, > > I've got 2 two node setup, image based installs. > When doing ova exports or generic snapshots, things seem in order. > Removing snapshots shows warning 'disk in illegal state' > > Mouse hover shows .. please do not shutdown before succesfully remove > snapshot > > > ovirt-engine log > 2020-07-22 16:40:37,549+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedExecutorService-commandCoordinator-Thread-2) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] EVENT_ID: > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM node2.lab command MergeVDS failed: > Merge failed > 2020-07-22 16:40:37,549+02 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] > (EE-ManagedExecutorService-commandCoordinator-Thread-2) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Command 'MergeVDSCommand(HostName = > node2.lab, > MergeVDSCommandParameters:{hostId='02df5213-1243-4671-a1c6-6489d7146319', > vmId='64c25543-bef7-4fdd-8204-6507046f5a34', > storagePoolId='5a4ea80c-b3b2-11ea-a890-00163e3cb866', > storageDomainId='9a12f1b2-5378-46cc-964d-3575695e823f', > imageGroupId='3f7ac8d8-f1ab-4c7a-91cc-f34d0b8a1cb8', > imageId='c757e740-9013-4ae0-901d-316932f4af0e', > baseImageId='ebe50730-dec3-4f29-8a38-9ae7c59f2aef', > topImageId='c757e740-9013-4ae0-901d-316932f4af0e', bandwidth='0'})' > execution failed: VDSGenericException: VDSErrorException: Failed to > MergeVDS, error = Merge failed, code = 52 > 2020-07-22 16:40:37,549+02 ERROR [org.ovirt.engine.core.bll.MergeCommand] > (EE-ManagedExecutorService-commandCoordinator-Thread-2) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Engine exception thrown while > sending merge command: org.ovirt.engine.core.common.errors.EngineException: > EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge > failed, code = 52 (Failed with error mergeErr and code 52) > Caused by: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge > failed, code = 52 > <driver name='qemu' error_policy='report'/> > <driver name='qemu' type='qcow2' cache='none' error_policy='stop' > io='threads'/> > 2020-07-22 16:40:39,659+02 ERROR > [org.ovirt.engine.core.bll.MergeStatusCommand] > (EE-ManagedExecutorService-commandCoordinator-Thread-3) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Failed to live merge. Top volume > c757e740-9013-4ae0-901d-316932f4af0e is still in qemu chain > [ebe50730-dec3-4f29-8a38-9ae7c59f2aef, c757e740-9013-4ae0-901d-316932f4af0e] > 2020-07-22 16:40:41,524+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-58) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Command id: > 'e0b2bce7-afe0-4955-ae46-38bcb8719852 failed child command status for step > 'MERGE_STATUS' > 2020-07-22 16:40:42,597+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-53) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Merging of snapshot > 'ef8f7e06-e48c-4a8c-983c-64e3d4ebfcf9' images > 'ebe50730-dec3-4f29-8a38-9ae7c59f2aef'..'c757e740-9013-4ae0-901d-316932f4af0e' > failed. Images have been marked illegal and can no longer be previewed or > reverted to. Please retry Live Merge on the snapshot to complete the > operation. > 2020-07-22 16:40:42,603+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-53) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Ending command > 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' > with failure. > 2020-07-22 16:40:43,679+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-15) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Ending command > 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. > 2020-07-22 16:40:43,774+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-15) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] EVENT_ID: > USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot > 'Auto-generated for Export To OVA' for VM 'Adhoc'. > > > VDSM on hypervisor > 2020-07-22 14:14:30,220+0200 ERROR (jsonrpc/5) [virt.vm] > (vmId='14283e6d-c3f0-4011-b90f-a1272f0fbc10') Live merge failed (job: > e59c54d9-b8d3-44d0-9147-9dd40dff57b9) (vm:5381) > if ret == -1: raise libvirtError ('virDomainBlockCommit() failed', > dom=self) > libvirt.libvirtError: internal error: qemu block name 'json:{"backing": > {"driver": "qcow2", "file": {"driver": "file", "filename": > "/rhev/data-center/mnt/10.12.0.9:_exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/bb3aed4b-fc41-456a-9c18-1409a9aa6d14"}}, > "driver": "qcow2", "file": {"driver": "file", "filename": > "/rhev/data-center/mnt/10.12.0.9:_exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/3995b256-2afb-4853-9360-33d0c12e5fd1"}}' > doesn't match expected '/rhev/data-center/mnt/10.12.0.9: > _exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/3995b256-2afb-4853-9360-33d0c12e5fd1' > 2020-07-22 14:14:30,234+0200 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC > call VM.merge failed (error 52) in 0.17 seconds (__init__:312) > > 2020-07-22 14:17:28,798+0200 INFO (jsonrpc/2) [api] FINISH getStats > error=Virtual machine does not exist: {'vmId': > '698d486c-edbf-4e28-a199-31a2e27bd808'} (api:129) > 2020-07-22 14:17:28,798+0200 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC > call VM.getStats failed (error 1) in 0.00 seconds (__init__:312) > > Also in log, > INFO (jsonrpc/1) [api.virt] FINISH getStats return={'status': {'code': 1, > 'message': "Virtual machine does not exist: > But is is there and accessible > > Any advice here? > Henri > > > ovirt 4.4.0.3-1.el8 > > OS Version: > RHEL - 8 - 1.1911.0.9.el8 > OS Description: > oVirt Node 4.4.0 > Kernel Version: > 4.18.0 - 147.8.1.el8_1.x86_64 > KVM Version: > 4.1.0 - 23.el8.1 > LIBVIRT Version: > libvirt-5.6.0-10.el8 > VDSM Version: > vdsm-4.40.16-1.el8 > SPICE Version: > 0.14.2 - 1.el8 > GlusterFS Version: > glusterfs-7.5-1.el8 > CEPH Version: > librbd1-12.2.7-9.el8 > Open vSwitch Version: > openvswitch-2.11.1-5.el8 > Nmstate Version: > nmstate-0.2.10-1.el8 > > _______________________________________________ > moVirt mailing list -- movirt(a)ovirt.org > To unsubscribe send an email to movirt-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/movirt@ovirt.org/message/3GXS3N77LEMQ… >

1 0

oVirt Network problem.
by Emil Dumitrache 22 Jul '20

22 Jul '20

Hello, I am new to oVirt. I have a problem and I don't know how to deal with it, i added another network besides the management network and after that the node did not respond to the oVIrt manager. I had to change the DNS to the new IP of the new network so that oVIrt manager can manage it. Now i have an error: Out-of-sync: Default route: host true, DC false. I checked on the node and the second network has DEFROUTE=NO and the management network to yes. I don't know why the manager is seeing that. Also the management IP does not respond to ping or anything. Please some advice for a newbie? The setup is: A standalone server with Centos7 and oVIrt manager installed and a node with ovirt node os. Thank you. [image: Tremend Logo] Emil Dumitrache IT Support Manager [image: Mobile] +40720450085 [image: Phone] +40-212-237-700 <0040212237700> [image: Email] emil.dumitrache(a)tremend.com [image: Website] www.tremend.com [image: Facebook] <https://www.facebook.com/TremendSoftware> [image: LinkedIN] [image: Skype] ------------------------------ Fastest growing Romanian company in Deloitte Fast 50 CE 2016

2 1

ovirt+SDN
by Marco Mangione 22 Jul '20

22 Jul '20

hello, anyone are using OVIRT with a SDN controller?

2 1

Re: Hosted Engine 4.4.1
by Vijay Sachdeva 22 Jul '20

22 Jul '20

Anyone please can help me out on this.? Vijay Sachdeva From: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> Date: Wednesday, 22 July 2020 at 8:24 PM To: Florian Schmid via Users <users(a)ovirt.org> Subject: Hosted Engine 4.4.1 Hello Everyone, Waiting for host to be up task is stuck for hours and when checked engine log found this below: 2020-07-22 16:50:35,717+02 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-1) [] OAuthException access_denied: Cannot authenticate user 'None@N/A': No valid profile found in credentials.. Has anyone faced such issue then please help me out..!! Thanks Vijay Sachdeva

1 0