Error after restoring hosted-engine
by Roberto Bertucci
Hello,
after restoring hosted-engine from a backup, i have several problems. Let's start with the first, other threads for others...
I can't see hosted-engine vm in vm list.
Looking at engine log, i see the following:
2022-07-05 16:51:26,330+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-49) [4c8e10ac] null architecture type, replacing with x86_64, VM [HostedEngine]
2022-07-05 16:51:26,332+02 INFO [org.ovirt.engine.core.bll.HostedEngineImporter] (EE-ManagedThreadFactory-engine-Thread-4932) [4c8e10ac] Try to import the Hosted Engine VM 'VM [HostedEngine]'
2022-07-05 16:51:26,334+02 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Lock Acquired to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_NAME, 4daba166-3da4-4220-8a56-5ddadf83015d=VM]', sharedLocks='[4daba166-3da4-4220-8a56-5ddadf83015d=REMOTE_VM]'}'
2022-07-05 16:51:26,335+02 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Error during ValidateFailure.: java.lang.NullPointerException
at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.validator.VmValidator.isBiosTypeSupported(VmValidator.java:467)
at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmCommandBase.validate(ImportVmCommandBase.java:158)
at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmCommand.validate(ImportVmCommand.java:220)
at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.internalValidateInTransaction(CommandBase.java:824)
at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:140)
at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:157)
........
........
2022-07-05 16:51:26,335+02 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Lock freed to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_NAME, 4daba166-3da4-4220-8a56-5ddadf83015d=VM]', sharedLocks='[4daba166-3da4-4220-8a56-5ddadf83015d=REMOTE_VM]'}'
2022-07-05 16:51:26,335+02 ERROR [org.ovirt.engine.core.bll.HostedEngineImporter] (EE-ManagedThreadFactory-engine-Thread-4932) [752aa465] Failed importing the Hosted Engine VM
Is there any way to solve this issue?
Web management interface is working except for the fact that i can't add new nodes and forget a storage domain which is no more existent.
Thank you,
Roberto
2 years, 9 months
4.5.1 hyperconverged install failure "No valid network interface has been found"
by Dax Kelson
TL;DR hyperconverged install. Gluster install works, hosted engine fails
with "no valid network interface has ben found"
I have a three node hyperconverged cluster that had previously been running
oVirt 4.4 successfully.
A fully wipe and clean install of 4.5.1 was attempted with:
ovirt-node-ng-installer-4.5.1-2022062306.el8.iso
On each node, there are two statically configured 10Gb ethernet interfaces
(and some unused 1Gb interfaces)
enp5s0f0 - ovirt management/VM network (default gateway is on this network)
enp5s0f1 - gluster network (isolated network)
Name resolution is done via /etc/hosts on each node:
100.64.0.7 node1-ovirt node1-ovirt.local
100.64.0.8 node2-ovirt node2-ovirt.local
100.64.0.9 node3-ovirt node3-ovirt.local
100.79.192.1 node1-ovirt-storage node1-ovirt-storage.local
100.79.192.2 node2-ovirt-storage node2-ovirt-storage.local
100.79.192.3 node3-ovirt-storage node3-ovirt-storage.local
Attempting to install the hosted engine fails with:
*System data could not be retrieved!*
*No valid network interface has been found*
*If you are using Bonds or VLANs Use the following naming conventions:*
- VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128,
enp3s0.50)
- Bond interfaces: bond*number* (for example, bond0, bond1)
- VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50,
bond1.128)
* Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad
* Networking teaming is not supported and will cause errors
Here is the network setup on node1:
[root@node1-ovirt ovirt]# ip -4 addr ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
6: enp5s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
inet 100.64.0.7/20 brd 100.64.15.255 scope global noprefixroute enp5s0f0
valid_lft forever preferred_lft forever
7: enp5s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
inet 100.79.192.1/24 brd 100.79.192.255 scope global noprefixroute
enp5s0f1
valid_lft forever preferred_lft forever
8: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state
DOWN group default qlen 1000
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
[root@node1-ovirt ovirt]#
My troubleshooting is that the failure is /probably/ coming from this file,
but I'm not sure why:
/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml
Help?
Thanks!
Dax Kelson
2 years, 9 months
oVirt v4.5 - Error when importing templates
by Erkan E
I have oVirt version 4.5.1.3 installed. When importing templates exported from oVirt v4.3 to oVirt v4.5, it fails and the error message below is raised. Even it is the same for templates exported form oVirt 4.5 as well.
- "Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : e is null. Please have your administrator to check the UI logs"
Related logs in /var/log/ovirt-engine/ui.log:
2022-07-05 12:37:31,652Z ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-3) [] Permutation name: 5EAE784A6F0B215E2BA85365FFA20B1F
2022-07-05 12:37:31,652Z ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-3) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : e is null
at org.ovirt.engine.ui.uicompat.Event.$raise(Event.java:99)
at org.ovirt.engine.ui.uicommonweb.models.ListModel.$setSelectedItem(ListModel.java:82)
at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.$setSelectedItem(SearchableListModel.java:406)
at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.setSelectedItem(SearchableListModel.java:406)
at org.ovirt.engine.ui.common.editor.UiCommonEditorVisitor.$updateListEditor(UiCommonEditorVisitor.java:189)
at org.ovirt.engine.ui.common.editor.UiCommonEditorVisitor.$lambda$5(UiCommonEditorVisitor.java:136)
at org.ovirt.engine.ui.common.editor.UiCommonEditorVisitor$lambda$5$Type.eventRaised(UiCommonEditorVisitor.java:136)
at org.ovirt.engine.ui.uicompat.Event.$raise(Event.java:99)
at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.$setItems(SearchableListModel.java:714)
at org.ovirt.engine.ui.uicommonweb.models.vms.ImportVmFromExportDomainModel.$lambda$0(ImportVmFromExportDomainModel.java:89)
at org.ovirt.engine.ui.uicommonweb.models.vms.ImportVmFromExportDomainModel$lambda$0$Type.onSuccess(ImportVmFromExportDomainModel.java:89)
at org.ovirt.engine.ui.frontend.Frontend$1.$onSuccess(Frontend.java:239)
at org.ovirt.engine.ui.frontend.Frontend$1.onSuccess(Frontend.java:239)
at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.$onSuccess(OperationProcessor.java:133)
at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.onSuccess(OperationProcessor.java:133)
at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$3$1.$onSuccess(GWTRPCCommunicationProvider.java:161)
at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$3$1.onSuccess(GWTRPCCommunicationProvider.java:161)
at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198)
at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233)
at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409)
at Unknown.onreadystatechange<(https://<SERVERNAME>/ovirt-engine/webadmin/?locale=en_US line 9 > injectedScript)
at com.google.gwt.core.client.impl.Impl.apply(Impl.java:306)
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:345)
at Unknown.My/<(https://<SERVERNAME>/ovirt-engine/webadmin/?locale=en_US line 9 > injectedScript)
at Unknown.anonymous(Unknown)
2 years, 9 months
vm backup, vprotect, user permissions
by Peter Hudec
Hi,
I would like to ask about thepermission for ht e vPortect to backup the VMs.
We have got 4 hypervisors in 1 DC for production and use admin account for backup.
Recently we added 3 more hypervisors for TEST/DEV. These new hypervisors are in separate DC.
As the vProtect got licence only for 4 hosts, we would like to create new user for taking backup only for the production DC.
We added vprotect user.
Add the DatacenterAdmin toe that users only for production DC, but this do not works, the problems are
- the vprotect user see all hosts ;(
- the backup are not able to finish, seems that some permission is still missing
Does anyone let me help with such a setup?
regards
Peter
2 years, 9 months
Problems with selinux after updating an ovirt node
by Giorgio Biacchi
Hi folks,
today I got a problem with vdsm and selinux after updating a host:
[root@host04 ~]# nodectl check
Status: WARN
Bootloader ... OK
Layer boot entries ... OK
Valid boot entries ... OK
Mount points ... OK
Separate /var ... OK
Discard is used ... OK
Basic storage ... OK
Initialized VG ... OK
Initialized Thin Pool ... OK
Initialized LVs ... OK
Thin storage ... OK
Checking available space in thinpool ... OK
Checking thinpool auto-extend ... OK
vdsmd ... BAD
So I run:
[root@host04 ~]# /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start
vdsm: Running mkdirs
vdsm: Running configure_vdsm_logs
vdsm: Running run_init_hooks
vdsm: Running check_is_configured
lvm is configured for vdsm
Current revision of multipath.conf detected, preserving
Managed volume database is already configured
abrt is already configured for vdsm
libvirt is already configured for vdsm
sanlock is configured for vdsm
Modules sebool are not configured
Error:
One of the modules is not configured to work with VDSM.
To configure the module use the following:
'vdsm-tool configure [--module module-name]'.
If all modules are not configured try to use:
'vdsm-tool configure --force'
(The force flag will stop the module's service and start it
afterwards automatically to load the new configuration.)
vdsm: stopped during execute check_is_configured task (task returned
with error code 1).
But also runnining this gave me an error:
[root@host04 ~]# vdsm-tool configure --module sebool
Checking configuration status...
Running configure...
libsepol.context_from_record: type cloud_what_var_cache_t is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert
system_u:object_r:cloud_what_var_cache_t:s0 to sid
invalid context system_u:object_r:cloud_what_var_cache_t:s0
libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned
error code 255.
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 209, in main
return tool_command[cmd]["command"](*args)
File "/usr/lib/python3.6/site-packages/vdsm/tool/__init__.py", line
40, in wrapper
func(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py",
line 145, in configure
_configure(c)
File "/usr/lib/python3.6/site-packages/vdsm/tool/configurator.py",
line 92, in _configure
getattr(module, 'configure', lambda: None)()
File
"/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py",
line 88, in configure
_setup_booleans(True)
File
"/usr/lib/python3.6/site-packages/vdsm/tool/configurators/sebool.py",
line 60, in _setup_booleans
sebool_obj.finish()
File "/usr/lib/python3.6/site-packages/seobject.py", line 340, in finish
self.commit()
File "/usr/lib/python3.6/site-packages/seobject.py", line 330, in commit
rc = semanage_commit(self.sh)
OSError: [Errno 0] Error
I managed to solve this by running:
[root@host04 ~]# semodule -i
/usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp
[root@host04 ~]# vdsm-tool configure --module sebool
Checking configuration status...
Running configure...
Done configuring modules to VDSM.
Regards
--
gb
PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
2 years, 9 months
ONN upgrade failing due to /var/cache/dnf filling up
by nroach44＠nroach44.id.au
I'm just wondering if anyone else has seen this, and if it's worth logging a case?
I've found that this seems to manifest itself as "Stop service" will succeed in the log, and them some time later the upgrade will fail. rm -rfv /var/cache/dnf* will resolve it.
Cheers,
Nathaniel.
2 years, 9 months
Unable to install on a bonded NIC
by weeglos＠yahoo.com
So I'm running a fresh install of oVirt on a new Centos Stream node. Fresh install.
I installed the OS with bonded interfaces. I bonded them during the install via anaconda.
I followed the doc here: https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_...
When I got to the hosted-engine --deploy step, it errored out saying, "Only Team devices are present. Teaming is unsupported."
However, I'm not teaming my network adapters at all. I'm bonding them:
[root@mustafar ~]# cat /etc/sysconfig/network-scripts/ifcfg-Bond_connection_1
BONDING_OPTS="mode=balance-rr downdelay=0 miimon=1 updelay=0"
TYPE=Bond
BONDING_MASTER=yes
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME="Bond connection 1"
UUID=[redacted]
DEVICE=bond0
ONBOOT=yes
IPADDR=192.168.5.83
PREFIX=24
GATEWAY=192.168.5.1
DNS1=192.168.5.2
DNS2=192.168.5.3
DNS3=192.168.5.4
DOMAIN=[redacted]
[root@mustafar ~]#
What gives with this?
2 years, 9 months
Live Migration FAIL
by m.rohweder＠itm-h.de
Hi,
on my setup the live migration looks greate but,
all sytems finnished migration tasks and running on other Host, but most of them (random instances not every time the same) going into hung (100%cpu insode VM an no response), that only reset can fix.
and i cannot find annything.
Greetings
Michael
2 years, 9 months
Invalid username or password
by less foobar
I've installed a fresh ovirt. The default engine user doesn't work for me.
* I've tried changing the password with:
```
ovirt-aaa-jdbc-tool user password-reset admin --password-valid-to="2035-12-31 12:00:00Z"
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
Password:
Reenter password:
updating user admin...
user updated successfully
```
* I've tried unblocking the admin user:
```
ovirt-aaa-jdbc-tool user unlock admin
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
updating user admin...
user updated successfully
```
* I've tried `admin`, `admin@internal` and `root@localhost`
* Here is my admin details:
```
ovirt-aaa-jdbc-tool user show admin
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
-- User admin(bca1d04a-cc83-4ab6-8233-602ab66df6d9) --
Namespace: *
Name: admin
ID: bca1d04a-cc83-4ab6-8233-602ab66df6d9
Display Name:
Email: root@localhost
First Name: admin
Last Name:
Department:
Title:
Description:
Account Disabled: false
Account Locked: false
Account Unlocked At: 2022-07-04 17:16:50Z
Account Valid From: 2022-06-28 21:27:59Z
Account Valid To: 2222-06-28 21:27:59Z
Account Without Password: false
Last successful Login At: 1970-01-01 00:00:00Z
Last unsuccessful Login At: 1970-01-01 00:00:00Z
Password Valid To: 2035-12-31 12:00:00Z
```
* above the keycloak sign-in page I see ovirt-internal this is why I'm assuming I'm on the right page. No matter where I click on `Administration Porta`, `VM Portal` or in the upper right corner I land on that page. This is why I'm assuming it is the internal login page and my "default" admin account should work.
* If I try the `Monitoring Portal` I can login without any issues.
2 years, 9 months
