Mutually exclusive VMs
by Shantur Rathore
Hi all,
I am trying to figure if there is a way to force oVirt to schedule VMs on
different hosts.
So if I am cloning 6 VMs from a template, I want oVirt to schedule them on
all different hosts.
No 2 VMs must schedule on the same host.
I know that there is pin-to-host functionality but I don't want to manually
pin it to hosts.
Thanks
Shantur
3 years, 10 months
Unable to edit DNS connfiguration on hosts
by miguel.garcia@toshibagcs.com
I had to replace the DNS server in my network so I want to update the DNS address on each host so in oVirt web interface I go to Compute > Host > Hostname > Network Interfaces > Setup Host Networks
Right there I click on the edit button of the vlan for networking, check out (host ip address is static), DNS configuration, check DNS configuration, Type DNS ip address and click ok to save change. I got message: Error while executing action HostSetupNetworks: Unexpected Exception.
Into engile.log found message "Operation not permitted" related to this action despite that was executed with my user account (wint admin privileges) and same message was returned using admin@internal user.
2021-01-20 11:35:31,579-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] START, HostSetupNetworksVDSCommand(HostName = hyp10.eboss, HostSetupNetworksVdsCommandParameters:{hostId='39c05625-7b59-4a38-a5a9-5d556ae1fe18', vds='Host[hyp10.eboss,39c05625-7b59-4a38-a5a9-5d556ae1fe18]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='tgcs182vlan', vdsmName='tgcs182vlan', nicName='eno1', vlan='null', vmNetwork='true', stp='false', properties='[]', ipv4BootProtocol='STATIC_IP', ipv4Address='10.89.182.10', ipv4Netmask='255.255.255.0', ipv4Gateway='10.89.182.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='[NameServer:{address='10.89.182.204'}, NameServer:{address='10.89.176.71'}]'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSw
itchType='OVS', managementNetworkChanged='false'}), log id: 23059843
2021-01-20 11:35:31,582-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] FINISH, HostSetupNetworksVDSCommand, return: , log id: 23059843
2021-01-20 11:35:35,665-05 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}]
2021-01-20 11:35:35,665-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Failed in 'HostSetupNetworksVDS' method
2021-01-20 11:35:35,666-05 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}]
2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM hyp10.eboss command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}
2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Error: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603
2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Command 'HostSetupNetworksVDSCommand(HostName = hyp10.eboss, HostSetupNetworksVdsCommandParameters:{hostId='39c05625-7b59-4a38-a5a9-5d556ae1fe18', vds='Host[hyp10.eboss,39c05625-7b59-4a38-a5a9-5d556ae1fe18]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='tgcs182vlan', vdsmName='tgcs182vlan', nicName='eno1', vlan='null', vmNetwork='true', stp='false', properties='[]', ipv4BootProtocol='STATIC_IP', ipv4Address='10.89.182.10', ipv4Netmask='255.255.255.0', ipv4Gateway='10.89.182.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='[NameServer:{address='10.89.182.204'}, NameServer:{address='10.89.176.71'}]'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', cluster
SwitchType='OVS', managementNetworkChanged='false'})' execution failed: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603
2021-01-20 11:35:35,673-05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Host setup networks finished. Lock released. Monitoring can run now for host 'hyp10.eboss' from data-center 'tgcs-gdl-dc1-public'
2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Command 'org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 (Failed with error unexpected and code 16)
2021-01-20 11:35:35,677-05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Lock freed to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK39c05625-7b59-4a38-a5a9-5d556ae1fe18=HOST_NETWORK]', sharedLocks=''}'
This error message happens even in master as in nodes hosts.
Any idea how can I solve it?
Thanks in advance
3 years, 10 months
Problems Installing host on brand new 4.4 cluster
by David Johnson
Hi all,
I am standing up a brand new cluster on new hardware.
The ovirt controller is installed and appears to be running fine.
When I attempt to add the new host, I get the flag that says "Non
Operational", and the exclamation mark with the message "Host has no
default route".
I have confirmed that I have bidirectional ssh connections between the
controller and the new host.
Selinux is disabled.
Firewall is disabled.
I can get to the host console via the link in the GUI Compute|Hosts page.
This looks like a common symptom of a host of problems, but there is
nothing to readily indicate what the actual problem is.
In the ovirt-engine log, I found this entry: "Host 'ovirt-host-03' is set
to Non-Operational, it is missing the following networks: 'ovirtmgmt'"
This seems self-explanatory, but I see no way to add the missing network to
the host.
Thank you in advance for your help
Regards,
David Johnson
* <http://www.linkedin.com/in/pojoguy>*
3 years, 10 months
Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"
by james.freeman@a24.io
Hi all
I am in the process of migrating a RHV 4.3 setup to RHV 4.4 and struggling with the setup. I am installing on RHEL 8.3, using settings backed up from the RHV 4.3 install (via 'hosted-engine --deploy --restore-from-file=backup.bck').
The install process always fails at the same point for me at the moment, and I can't figure out how to get past it. As far as install progress goes, the local hosted-engine comes up and runs on the node. I have been able to grep for local_vm_ip in the logs, and can SSH into it with the password I set during the setup phase.
However the install playbooks always fail with:
2021-01-18 18:38:00,086-0500 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:167 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.
Earlier in the logs, I note the following:
2021-01-18 18:34:51,258-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"}
2021-01-18 18:37:16,661-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod
method['method']()
File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 435, in _closeup
raise RuntimeError(_('Failed executing ansible-playbook'))
RuntimeError: Failed executing ansible-playbook
2021-01-18 18:37:18,996-0500 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook
2021-01-18 18:37:32,421-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host rhvm.example.org port 22: No route to host", "skip_reason": "Host localhost is unreachable", "unreachable": true}
I find the unreachable message a bit odd, as at this stage all that has happened is that the local hosted-engine has been brought up to be configured, and so it is running on virbr0, not on my actual network. As a result, that DNS address will never resolve, and the IP it resolves to won't be up. I gave the installation script permission to modify the local /etc/hosts but this hasn't improved things.
I presume I'm missing something in the install process, or earlier on in the logs, but I've been scanning for errors and possible clues to no avail.
Any and all help greatly appreciated!
3 years, 10 months
VM Disks order
by Erez Zarum
When attaching a disk it is not possible to set the disk order nor modify the order later.
Example:
A new VM is provisioned with 5 disks, Disk0 is the OS and then later attached disks by order up to Disk4.
Removing Disk3 and then later attaching does not promise it will be attached back as Disk3.
In most other platforms it is possible to set the order.
Am i missing something? if not, is there a plan to add this feature?
3 years, 10 months
Why the update hung here ?
by tommy
Hi , I just update the hosts, but why the log print these info many many
times for a long while.
3 years, 10 months
noVNC error.
by tommy
Hi:
I use novnc console can connect to engine vm.
But when I using novnc console connect to other vm in other datacenter,
failed.
The ovirt-websocket-proxy log is:
Jan 19 15:43:32 ooeng.tltd.com ovirt-websocket-proxy.py[1312]:
192.168.10.104 - - [19/Jan/2021 15:43:32] connecting to:
ohost2.tltd.com:5900 (using SSL)
Jan 19 15:43:32 ooeng.tltd.com ovirt-websocket-proxy.py[1312]:
ovirt-websocket-proxy[24096] INFO msg:824 handler exception: [SSL:
UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:618)
What reason ?
3 years, 10 months
Guest don't start : Cannot access backing file
by Lionel Caignec
Hi,
i've a big problem, i juste shutdown (power off completely) a guest to make a cold restart. And at startup the guest say : "Cannot access backing file '/rhev/data-center/mnt/blockSD/69348aea-7f55-41be-ae4e-febd86c33855/images/8224b2b0-39ba-44ef-ae41-18fe726f26ca/ca141675-c6f5-4b03-98b0-0312254f91e8'"
When i look from shell on Hypervisor the device file is red blinking...
Trying to change SPM, look device into all hosts, copy disk etc... no way to get my disk back online. It seems ovirt completely lost (delete?) the block device.
There is a way to manually dump (dd) the device in command line in order to import it inside ovirt?
My environment
Storage : SAN (managed by ovirt)
Ovirt-engine 4.4.3.12-1.el8
Host centos 8.2
Vdsm 4.40.26
Thanks for help i'm stuck and it's really urgent
--
Lionel Caignec
3 years, 10 months