Adding iscsi issue 4.3
by thilburn＠generalpacific.com
When connecting an iscsi connection from an array I get the following popup "A database error occurred. Please contact your system administrator." I have checked everything and the only device connected right now is the single host in the datacenter. If I check the box " Approve operation" and click Ok it will error out with "A database error occurred. Please contact your system administrator." This is a new volume and no other machine is connected to this LUN or array. Below is from the vdsm log
2020-11-11 10:42:26,087-0800 INFO (jsonrpc/0) [vdsm.api] START getDeviceList(storageType=3, guids=[u'32021001378a6ddad'], checkStatus=True, options={}) from=::ffff:XXXXXX,46208, flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:48)
2020-11-11 10:42:26,650-0800 INFO (jsonrpc/0) [storage.LVM] Overriding read_only mode current=True override=False (lvm:398)
2020-11-11 10:42:26,822-0800 INFO (jsonrpc/0) [vdsm.api] FINISH getDeviceList return={'devList': [{'status': 'used', 'vendorID': 'ETIUSA', 'capacity': '3999688294400', 'fwrev': '10E', 'discard_zeroes_data': 0, 'vgUUID': '', 'pvsize': '', 'pathlist': [{'connection': u'10.87.172.100', 'iqn': u'XXXXXX.XXXXXX.XXXXXX:storage3', 'portal': '0', 'port': '3260', 'initiatorname': u'default'}], 'logicalblocksize': '512', 'discard_max_bytes': 0, 'pathstatus': [{'type': 'iSCSI', 'physdev': 'sdc', 'capacity': '3999688294400', 'state': 'active', 'lun': '0'}], 'devtype': 'iSCSI', 'physicalblocksize': '512', 'pvUUID': '', 'serial': 'SETIUSA_UltraStorRS8IP4_2021001378A6DDAD', 'GUID': '32021001378a6ddad', 'productID': 'UltraStorRS8IP4'}]} from=::ffff:XXXXX,46208, flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:54)
2020-11-11 10:42:26,823-0800 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getDeviceList succeeded in 0.74 seconds (__init__:312)
2020-11-11 10:42:27,158-0800 INFO (jsonrpc/2) [api.host] START getAllVmStats() from=::1,48480 (api:48)
2020-11-11 10:42:27,159-0800 INFO (jsonrpc/2) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48480 (api:54)
2020-11-11 10:42:27,159-0800 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
2020-11-11 10:42:27,393-0800 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::ffff:XXXXX,46208 (api:48)
2020-11-11 10:42:27,394-0800 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:XXXXX,46208 (api:54)
2020-11-11 10:42:27,394-0800 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
2020-11-11 10:43:12,323-0800 INFO (jsonrpc/6) [vdsm.api] START createVG(vgname=u'35e95355-75db-4640-bf99-e576b9ce39aa', devlist=[u'32021001378a6ddad'], force=True, options=None) from=::ffff:XXXXX,46208, flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:48)
2020-11-11 10:43:12,348-0800 INFO (jsonrpc/6) [storage.LVM] Overriding read_only mode current=True override=False (lvm:398)
2020-11-11 10:43:12,409-0800 INFO (jsonrpc/4) [api.host] START getAllVmStats() from=::ffff:XXXXXX,46208 (api:48)
2020-11-11 10:43:12,410-0800 INFO (jsonrpc/4) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:XXXXXXX,46208 (api:54)
2020-11-11 10:43:12,410-0800 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] pvcreate failed with rc=5 (lvm:988)
2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] [], [' Device /dev/mapper/32021001378a6ddad excluded by a filter.'] (lvm:989)
2020-11-11 10:43:12,520-0800 INFO (jsonrpc/6) [vdsm.api] FINISH createVG error=Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) from=::ffff:XXXXXX,46208, flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:52)
2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') Unexpected error (task:875)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run
return fn(*args, **kargs)
File "<string>", line 2, in createVG
File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2146, in createVG
force=force)
File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 1256, in createVG
_initpvs(pvs, metadataSize, force)
File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 990, in _initpvs
raise se.PhysDevInitializationError(str(devices))
PhysDevInitializationError: Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",)
2020-11-11 10:43:12,520-0800 INFO (jsonrpc/6) [storage.TaskManager.Task] (Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') aborting: Task is aborted: 'Failed to initialize physical device: ("[u\'/dev/mapper/32021001378a6ddad\']",)' - code 601 (task:1181)
2020-11-11 10:43:12,521-0800 ERROR (jsonrpc/6) [storage.Dispatcher] FINISH createVG error=Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) (dispatcher:83)
2020-11-11 10:43:12,521-0800 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call LVMVolumeGroup.create failed (error 601) in 0.20 seconds (__init__:312)
4 years, 4 months
Dependencies failure when upgrading from version 4.4.2 to 4.4.3
by jorgevisentini＠gmail.com
When I update the Engine and Host, many dependencies are missing, as shown by the host error log:
Error:
Problem 1: package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires ovirt-ansible-engine-setup >= 1.1.9, but none of the providers can be installed
- package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-engine-setup provided by ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
- cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch
- cannot install the best update candidate for package ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
Problem 2: package ovirt-host-4.4.1-4.el8.x86_64 requires ovirt-hosted-engine-setup, but none of the providers can be installed
- package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires ovirt-ansible-hosted-engine-setup >= 1.0.34, but none of the providers can be installed
- package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-hosted-engine-setup provided by ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
- cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64
- cannot install the best update candidate for package ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch
- package ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch is filtered out by exclude filtering
- package ovirt-ansible-hosted-engine-setup-1.1.5-1.el8.noarch is filtered out by exclude filtering
- package ovirt-ansible-hosted-engine-setup-1.1.6-1.el8.noarch is filtered out by exclude filtering
- package ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch is filtered out by exclude filtering
- package ovirt-hosted-engine-setup-2.4.4-1.el8.noarch is filtered out by exclude filtering
- package ovirt-hosted-engine-setup-2.4.5-1.el8.noarch is filtered out by exclude filtering
- package ovirt-hosted-engine-setup-2.4.7-1.el8.noarch is filtered out by exclude filtering
- package ovirt-hosted-engine-setup-2.4.8-1.el8.noarch is filtered out by exclude filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
4 years, 4 months
Single Node HCI upgrade procedure from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4?
by thomas＠hoberg.net
I can hear you saying: "You did understand that single node HCI is just a toy, right?"
For me the primary use of a single node HCI is adding some disaster resilience in small server edge type scenarios, where a three node HCI provides the fault tolerance: 3+1 with a bit of distance, warm or even cold stand-by, potentially manual switch and reduced workload in case disaster strikes.
Of course, another 3nHCI would be better, but who gets that type of budget, right?
What I am trying say: If you want oVirt to gain market share, try to give HCI more love. And while you're at it, try to make expanding from 1nHCI to 3nHCI (and higher counts) a standard operational procedure to allow expanding a disaster stand-by into a production setup, while the original 3nHCI is being rebuilt.
For me low-budget HCI is where oVirt has its biggest competitive advantage against vSan and Nutanix, so please don't treat the HCI/gluster variant like an unwanted child any more.
In the mean-time OVA imports (from 4.3.10 exports) on my 4.4.2 1nHCI fail again, which I'll report separately.
4 years, 4 months
Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3
by Andrei Verovski
Hi !
I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, running as KVM appliance (not hosted engine).
This sequence of commands
yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
engine-upgrade-check
yum update ovirt\*setup\*
Results in a long list of dependency errors, short excerpt below.
Looks like something (e.g. repo) is missing. How to fix this? Thanks in advance.
————— LOG ----------
Problem 1: problem with installed package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch
- package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed
Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be installed
- package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed
- package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed
- package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch
4 years, 4 months
Cluster with Hosted Engine update BIOS Setting Ovirt 4.4.3
by scrik787＠gmail.com
I changed the type in the cluster and now my hosted-engine machine won't start!. There
are no backups. How can I manually change the parameters of the machine from under the
roof so that it starts and I can restore ovirt to work
Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into
the PCI controller with index='0'. It requires a controller that accepts a
pcie-root-port
VDSM.log https://pastebin.com/vsAKy9rX
4 years, 4 months
Host NonResponsive after migration to oVirt 4.4
by tferic＠swissonline.ch
Hi
I am looking for help after my oVirt upgrade failed.
I have upgraded from ovirt 4.3 to 4.4 following the instructions here:
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 <https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3>
It's a single-host (standalone engine) test environment.
I wiped CentOS 7 and reinstalled a fresh CentOS 8.
I installed the oVirt 4.4 repo and all the necessary software packets.
I used `engine-backup --mode=restore --file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from a backup file I created before I started the upgrade.
After the restore, I ran `engine-setup`.
I did not get any errors during any of these steps on the console.
So the upgrade could be considered successful from that perspective.
After the upgrade, I login to the ovirt admin portal, and I try to "Activate" my host (was set to "Maintenance" mode before upgrade).
The Activation fails with error "NonResponsive" in the GUI.
Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non responsive.”
In /var/log/ovirt-engine/engine.log, I find the following error:
```
2020-11-09 23:12:21,080+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = nuc1.feric.ch, VdsIdAndVdsVDSCommandParametersBase:{hostId='d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb', vds=‘Host[nuc1.feric.h,d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb]'})' execution failed: java.net.ConnectException: Connection refused
```
`systemctl status ovirt-engine` shows that the engine is running.
I am able to reboot the host from the oVirt GUI directly.
Does anyone have an idea how to proceed?
Many thanks
Toni
4 years, 4 months
Clone a VM in the User Portal
by Nicolás
Hi,
We're using oVirt 4.3.8, having an organization that intensively uses
the User Portal. After upgrading from 4.2, we've noticed that cloning a
VM from within the User Portal is not possible anymore. In our case,
this feature was heavily used by hundreds of students deploying their VMs.
Is this feature in the roadmap yet? If not, do you consider it useful to
open a RFE?
Thank you.
Regards,
Nico
4 years, 4 months
Cannot restore engine from 4.3.9 to 4.4.3
by tferic＠swissonline.ch
Hi
I just tried to restore my engine backup taken from release 4.3.9.4 to a
newer oVirt installation release 4.4.3.11.
The restore process fails with a FATAL error.
I was under the impression that backups from all 4.3 versions were
supposed to be restorable on 4.4.
My installation is a single-box all-in-one (Standalone Engine installed
together with oVirt node).
# engine-backup --mode=restore
--file=/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
--provision-all-databases
Start of engine-backup with mode 'restore'
scope: all
archive file:
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
log file:
/var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log
Preparing to restore:
- Unpacking file
'/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup'
FATAL: Backup was created by version '4.3.9.4' and can not be restored
using the installed version 4.4.3.11
Complete content of the restore log file:
2020-11-11 03:15:00 23143: Start of engine-backup mode restore scope all
file
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
2020-11-11 03:15:00 23143: OUTPUT: Start of engine-backup with mode
'restore'
2020-11-11 03:15:00 23143: OUTPUT: scope: all
2020-11-11 03:15:00 23143: OUTPUT: archive file:
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
2020-11-11 03:15:00 23143: OUTPUT: log file:
/var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log
2020-11-11 03:15:00 23143: OUTPUT: Preparing to restore:
2020-11-11 03:15:01 23143: OUTPUT: - Unpacking file
'/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup'
2020-11-11 03:15:01 23143: Opening tarball
/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup
to /tmp/engine-backup.UAcLerghwY
2020-11-11 03:15:01 23143: Verifying hash
2020-11-11 03:15:01 23143: Verifying version
2020-11-11 03:15:01 23143: FATAL: Backup was created by version
'4.3.9.4' and can not be restored using the installed version 4.4.3.11
regards,
Toni Feric
4 years, 4 months
Problem with Cluster-wise BIOS Settings in oVirt 4.4
by Rodrigo G. López
Hi all,
We are running an oVirt 4.4 Hosted Engine as a VM, and after changing
the Cluster's BIOS type from Q35 with Legacy BIOS (the default one after
installation) to Preexistent, the VM fails with the following error:
XML error: The device at PCI address 0000:00:02.0 cannot be plugged into
the PCI controller with index='0'. It requires a controller that accepts
a pcie-root-port.
We need it so that we can run imported VMs from a previous version of
oVirt, namely 4.0.
Applying the BIOS settings individually works but as an attempt to
generalize the settings we decided to apply it to the full cluster.
Tell me if you need more data.
Cheers,
-rodri
4 years, 4 months
oVirt 4.4.2 MS Windows 10 sysprep floppy
by ozmen62＠hotmail.com
Hi,
I've cretated a template which has sysprep.
Every document about sysprep says use "Attach Floppy" , but we know this function has been disabled/deprecated
So, when i use Run One, attach windows cdrom and put in it definitions (domain name, user credentials etc) , nothing happens.
I also have correct properties and sysprep files in engine
Just windows boot like it is new machine and ask lots of questions for prepare itself.
Would someone please explain this?
How can i run sysprep correctly?
4 years, 4 months
