VM without Host stuck in "Rebooting" State
by Raphael Höser
I have a VM which was send a "Reboot" and "Shutdown" command in short succession (two admins who were not thinking the same way) and now the VM is Stuck in "Rebooting".
It has no Host assigned and when trying to turn it of (via Shutdown or Power Off) it gives this error:
Sep 29, 2020, 10:27:10 AM
Failed to power off VM <vm_name> (Host: <UNKNOWN>, User: admin@internal-authz).
The engine logs don't provide more info either:
2020-09-29 10:42:18,628+02 INFO [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-68681) [d4c6547e-c326-4907-8c34-36fd5ab81dfa] Running command: StopVmCommand internal: false. Entities affected : ID: 55edef7a-7a0b-42f0-a98f-9150103fa0b1 Type: VMAction group STOP_VM with role type USER
2020-09-29 10:42:18,628+02 WARN [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-68681) [d4c6547e-c326-4907-8c34-36fd5ab81dfa] Strange, according to the status 'RebootInProgress' virtual machine '55edef7a-7a0b-42f0-a98f-9150103fa0b1' should be running in a host but it isn't.
2020-09-29 10:42:18,635+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-68681) [d4c6547e-c326-4907-8c34-36fd5ab81dfa] EVENT_ID: USER_FAILED_STOP_VM(56), Failed to power off VM degum-ci-windows3 (Host: <UNKNOWN>, User: admin@internal-authz).
What steps can I do to resolve this?
I do not need to restore this machine, I'm totally fine with just deleting it, but it may not impact other running machines.
3 years, 6 months
oVirt Change hosts to FQDN
by Jeremey Wise
I posted that I had wiped out the oVirt-engine.. running cleanup on all
three nodes. Done a re-deployment. Then to add nodes back.. though all
have entries for eachother in /etc/hosts and ssh works fine via short and
long name.
I added nodes back into cluster.. but had to do it via IP to get past
error.
Now, if I go to create a volume via the GUI in gluster I get:
Error while executing action Create Gluster Volume: Volume create failed:
rc=30800 out=() err=["Host 172_16_100_102 is not in 'Peer in Cluster'
state"]
Which seems to be related to using IP vs DNS to add gluster volumes
https://bugzilla.redhat.com/show_bug.cgi?id=1055928
Question: how do i fix the hosts in cluster being defined by IP vs desired
hostname?
--
jeremey.wise(a)gmail.com
3 years, 6 months
Source storage domain info in storage live migration
by Gianluca Cecchi
Hello,
having to monitor and check live storage migrations, it seems to me that
scrolling through events I can see information about the target storage
domain name, but nothing about the source. Is it correct?
Can it be added? Which kind of rfe bugzilla should I use in case? Against
what?
Thanks,
Gianluca
3 years, 6 months
Trouble with restoring hosted engine from backup
by Siddharth Patil
Dear all,
I'm trying to restore hosted-engine from backup, but it fails with the
following error message:
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
"\"Cluster name cannot be 'Default'. This is a reserved name for the
default DataCenter. Please choose\" \" another name for the cluster\""}
My DataCenter is called Primary and Cluster is called Default. I have two
hosts node01 and node02, with shared storage through NFS. I'm running the
restore on node02.
I can restore successfully if I change the Cluster name, but then I cannot
move node02 to the default cluster, or move node01 to the new cluster, as I
cannot shut down the VMs currently running on node01.
Please help!
Regards,
Siddharth
3 years, 6 months
Newbie question on network
by valerio.luccio＠nyu.edu
I apologize for asking what is probably a very basic question.
I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.
I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?
Thanks in advance,
Valerio
3 years, 6 months
Cannot change Cluster Compatibility Version after 4.4 upgrade
by paolo＠airaldi.it
Hi all,
we have an oVirt 4.3 with 3 Hosts and 20 VMs.
2 Hosts are Dell PowerEdge R610 with 2 Intel(R) Xeon(R) CPU E5540 processor
each (Intel Nehalem IBRS SSBD), while the third is an HP ProLiant ML350p
Gen8 with 2 Intel(R) Xeon(R) CPU E5-2620 v2 processor (Intel SandyBridge
IBRS SSBD MDS) They all are in the same Cluster.
Some of the 20 VMs are Windows (Win 10, Win 2012 and Win 2016)
We have upgraded to 4.4.2.6-1.el8 following the instruction
https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3.
We had some minor issues that have been fixed and now we need to change
Cluster Compatibility Version, but it fails complaining about Win10 and
Win2016 VMs. In agent.log, for each of them I have:
WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-122)
[292f1983] Validation of action 'UpdateVm' failed for user
admin@internal-authz. Reasons:
VAR__ACTION__UPDATE,VAR__TYPE__VM,CPU_TYPE_UNSUPPORTED_FOR_THE_GUEST_OS,$uns
upportedCpus opteron_g1, conroe, nehalem, penryn
The same messages appear even if the VMs are powered off.
We tried to change the Operating System in one VM configuration and if we
put Win2012 the VM is no more in the error list when we edit the Cluster,
but we're not sure the VMs will restart once Cluster compatibility will be
to 4.4
How can we proceed?
Hosts:
# rpm -qa|grep -i ovirt
ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
ovirt-host-dependencies-4.4.1-4.el8.x86_64
ovirt-hosted-engine-setup-2.4.6-1.el8.noarch
ovirt-python-openvswitch-2.11-0.2020061801.el8.noarch
ovirt-imageio-daemon-2.0.10-1.el8.x86_64
ovirt-release44-4.4.2-1.el8.noarch
ovirt-vmconsole-1.0.8-1.el8.noarch
python3-ovirt-engine-sdk4-4.4.4-1.el8.x86_64
ovirt-imageio-client-2.0.10-1.el8.x86_64
cockpit-ovirt-dashboard-0.14.11-1.el8.noarch
ovirt-provider-ovn-driver-1.2.30-1.el8.noarch
ovirt-vmconsole-host-1.0.8-1.el8.noarch
ovirt-openvswitch-2.11-0.2020061801.el8.noarch
ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch
ovirt-openvswitch-ovn-host-2.11-0.2020061801.el8.noarch
ovirt-openvswitch-ovn-2.11-0.2020061801.el8.noarch
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
ovirt-host-4.4.1-4.el8.x86_64
python3-ovirt-setup-lib-1.3.2-1.el8.noarch
ovirt-imageio-common-2.0.10-1.el8.x86_64
ovirt-hosted-engine-ha-2.4.4-1.el8.noarch
Engine:
# rpm -qa|grep -i ovirt
ovirt-engine-extension-aaa-jdbc-1.2.0-1.el8.noarch
ovirt-engine-dbscripts-4.4.2.6-1.el8.noarch
ovirt-engine-tools-4.4.2.6-1.el8.noarch
ovirt-openvswitch-ovn-central-2.11-0.2020061801.el8.noarch
ovirt-cockpit-sso-0.1.4-1.el8.noarch
ovirt-ansible-infra-1.2.2-1.el8.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch
ovirt-engine-tools-backup-4.4.2.6-1.el8.noarch
ovirt-engine-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch
ovirt-release44-4.4.2-1.el8.noarch
python3-ovirt-setup-lib-1.3.2-1.el8.noarch
ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch
ovirt-imageio-daemon-2.0.10-1.el8.x86_64
ovirt-python-openvswitch-2.11-0.2020061801.el8.noarch
ovirt-ansible-image-template-1.2.2-1.el8.noarch
ovirt-ansible-shutdown-env-1.1.0-1.el8.noarch
python3-ovirt-engine-lib-4.4.2.6-1.el8.noarch
ovirt-provider-ovn-1.2.30-1.el8.noarch
ovirt-engine-dwh-grafana-integration-setup-4.4.2.1-1.el8.noarch
ovirt-engine-dwh-setup-4.4.2.1-1.el8.noarch
ovirt-openvswitch-ovn-2.11-0.2020061801.el8.noarch
ovirt-vmconsole-proxy-1.0.8-1.el8.noarch
ovirt-imageio-common-2.0.10-1.el8.x86_64
ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
ovirt-ansible-repositories-1.2.5-1.el8.noarch
ovirt-engine-setup-4.4.2.6-1.el8.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch
ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch
ovirt-engine-extension-aaa-ldap-1.4.1-1.el8.noarch
ovirt-engine-extension-aaa-misc-1.1.0-1.el8.noarch
ovirt-engine-extensions-api-1.0.1-1.el8.noarch
ovirt-engine-setup-plugin-websocket-proxy-4.4.2.6-1.el8.noarch
ovirt-engine-api-explorer-0.0.6-1.el8.noarch
ovirt-engine-setup-plugin-cinderlib-4.4.2.6-1.el8.noarch
ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch
ovirt-engine-wildfly-19.1.0-2.el8.x86_64
ovirt-engine-wildfly-overlay-19.1.0-2.el8.noarch
ovirt-web-ui-1.6.4-1.el8.noarch
ovirt-openvswitch-2.11-0.2020061801.el8.noarch
python3-ovirt-engine-sdk4-4.4.4-1.el8.x86_64
ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch
ovirt-engine-metrics-1.4.1.1-1.el8.noarch
ovirt-ansible-manageiq-1.2.1-1.el8.noarch
ovirt-engine-4.4.2.6-1.el8.noarch
ovirt-engine-extension-logger-log4j-1.1.0-1.el8.noarch
ovirt-engine-websocket-proxy-4.4.2.6-1.el8.noarch
ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch
ovirt-engine-backend-4.4.2.6-1.el8.noarch
ovirt-vmconsole-1.0.8-1.el8.noarch
ovirt-dependencies-4.4.2-1.el8.noarch
ovirt-ansible-vm-infra-1.2.3-1.el8.noarch
ovirt-ansible-roles-1.2.3-1.el8.noarch
ovirt-engine-setup-base-4.4.2.6-1.el8.noarch
ovirt-engine-dwh-4.4.2.1-1.el8.noarch
ovirt-engine-restapi-4.4.2.6-1.el8.noarch
ovirt-engine-ui-extensions-1.2.3-1.el8.noarch
ovirt-engine-extension-aaa-ldap-setup-1.4.1-1.el8.noarch
ovirt-ansible-disaster-recovery-1.3.0-1.el8.noarch
3 years, 6 months
Re: oVirt networking.
by dhanaraj.ramesh＠yahoo.com
Hi
1) trunk all the network including management, VM traffic subnets in both ports and tag the management network as native
2) configure the bonds with active/backup with management IP while installing the OS
3) proceed the hosted engine installation in the same management network
4) once hosted engine is up, add all hosts and create vm traffic network with VLAN tags
3 years, 6 months
oVirt networking.
by Matthew.Stier＠fujitsu.com
oVirt newbie starting with 4.4.2.
Any good documentation on setting up networking?
I want to bond my two network interfaces. The native interface will be uses for management. All other traffic will be over tagged vlans.
3 years, 7 months
MOM can't run
by duhongyu
hi
I try to start momd by "systemctl restart momd" but it can't run , so I run momd by " /usr/sbin/momd -c /etc/momd.conf "
[root@node0 mom]# /usr/sbin/momd -c /etc/momd.conf
2020-09-27 14:31:12,291 - mom - INFO - MOM starting
2020-09-27 14:31:12,381 - mom.HostMonitor - INFO - Host Monitor starting
2020-09-27 14:31:12,381 - mom - INFO - hypervisor interface vdsm
2020-09-27 14:31:12,690 - mom - ERROR - Unable to import hypervisor interface: vdsm
2020-09-27 14:31:12,707 - mom.GuestManager - INFO - Guest Manager starting: multi-thread
2020-09-27 14:31:12,708 - mom.GuestManager - INFO - Guest Manager ending
2020-09-27 14:31:12,708 - mom.PolicyEngine - INFO - Policy Engine starting
2020-09-27 14:31:12,709 - mom.RPCServer - INFO - RPC Server is disabled
2020-09-27 14:31:12,710 - mom - INFO - Shutting down RPC server.
2020-09-27 14:31:12,710 - mom.PolicyEngine - INFO - Policy Engine ending
2020-09-27 14:31:12,710 - mom - INFO - Waiting for RPC server thread.
2020-09-27 14:31:12,710 - mom - INFO - Waiting for policy engine thread.
2020-09-27 14:31:12,710 - mom - INFO - Waiting for guest manager thread.
2020-09-27 14:31:12,710 - mom - INFO - Waiting for host monitor thread.
2020-09-27 14:31:12,828 - mom.HostMonitor - INFO - HostMonitor is ready
2020-09-27 14:31:17,710 - mom - INFO - MOM ending
/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py
import sys
sys.path.append('/usr/share/vdsm')
import API
import supervdsm
import logging
import traceback
from mom.HypervisorInterfaces.HypervisorInterface import HypervisorInterface, \
HypervisorInterfaceError
after I debug momd, I find not import API and supervdsm, can you give me some suggestion?
--
Regards
Hongyu Du
3 years, 7 months
