Upgrading manger from 4.4 to 4.5 - repo/dependency issues
by jeremy_tourville@hotmail.com
My system is Rocky 8.9
I am running into some issues with upgrading. I am following the guide - https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_th...
I also followed https://www.ovirt.org/download/install_on_rhel.html and took care of the Rocky sepecific section along with the "Common to RHEL 8.6 and derivatives"
When running the upgrade 3.2. Updating the oVirt Engine, step #3 engine-setup fails with:
[ ERROR ] DNF
Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2. 14, but none of the providers can be installed
- cannot install the best candidate for the job
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
Problem 2: problem with installed package ovirt-engine-4.4.10.7-1.el8.noarch
- cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch
- cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch
- package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
Problem 3: problem with installed package ansible-runner-service-1.0.7-1.el8.noarch
- cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch
- cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch
- package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
Problem 4: problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch
- cannot install the best update candidate for package python3-ansible-runner-1.4.6-1.el8.noarch
- package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
[ INFO ] DNF Performing DNF transaction rollback
[ ERROR ] Failed to execute stage 'Environment customization':
Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2. 14, but none of the providers can be installed
- cannot install the best candidate for the job
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
Problem 2: problem with installed package ovirt-engine-4.4.10.7-1.el8.noarch
- cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch
- cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch
- package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
Problem 3: problem with installed package ansible-runner-service-1.0.7-1.el8.noarch
- cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch
- cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch
- package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
Problem 4: problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch
- cannot install the best update candidate for package python3-ansible-runner-1.4.6-1.el8.noarch
- package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed
- package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed
- package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring
- package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering
- package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering
[ INFO ] Stage: Clean up
Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20231124095827-ytworo.log
[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20231124100101-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
I recall running into a similar issue before with modules that were causing upgrade issues. Sometimes the easiest thing is to reset a module, but I am not sure in this case.
Here is what repos I have on my system:
[root@engine ~]# dnf repolist
repo id repo name
appstream Rocky Linux 8 - AppStream
baseos Rocky Linux 8 - BaseOS
centos-ceph-pacific CentOS-8-stream - Ceph Pacific
centos-gluster10 CentOS-8-stream - Gluster 10
centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch
centos-ovirt45 CentOS Stream 8 - oVirt 4.5
cs8-extras CentOS Stream 8 - Extras
cs8-extras-common CentOS Stream 8 - Extras common packages
devel Rocky Linux 8 - Devel WARNING! FOR BUILDROOT AND KOJI USE
epel-debuginfo Extra Packages for Enterprise Linux 8 - x86_64 - Debug
epel-modular Extra Packages for Enterprise Linux Modular 8 - x86_64 - RETIRED
epel-modular-debuginfo Extra Packages for Enterprise Linux Modular 8 - x86_64 - Debug - RETIRED
epel-modular-source Extra Packages for Enterprise Linux Modular 8 - x86_64 - Source - RETIRED
epel-source Extra Packages for Enterprise Linux 8 - x86_64 - Source
epel-testing Extra Packages for Enterprise Linux 8 - Testing - x86_64
epel-testing-debuginfo Extra Packages for Enterprise Linux 8 - Testing - x86_64 - Debug
epel-testing-modular Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - RETIRED
epel-testing-modular-debuginfo Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - Debug - RETIRED
epel-testing-modular-source Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - Source - RETIRED
epel-testing-source Extra Packages for Enterprise Linux 8 - Testing - x86_64 - Source
ha Rocky Linux 8 - HighAvailability
ovirt-4.4 Latest oVirt 4.4 Release
ovirt-4.4-centos-advanced-virtualization CentOS-8 - Advanced Virtualization
ovirt-4.4-centos-ceph-pacific CentOS-8-stream - Ceph Pacific
ovirt-4.4-centos-gluster8 CentOS-8-stream - Gluster 8
ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch
ovirt-4.4-centos-openstack-victoria CentOS-8 - OpenStack victoria
ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-opstools-vault CentOS-8 - OpsTools - collectd - vault
ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL
ovirt-45-centos-stream-openstack-yoga CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository
ovirt-45-upstream oVirt upstream for CentOS Stream 8 - oVirt 4.5
powertools Rocky Linux 8 - PowerTools
Can anyone advise the steps to get this system to upgrade as expected?
1 year, 2 months
Cannot successfully import Windows vm to new ovirt deployment
by netracerx@mac.com
I am running into an issue that, from what little Google-fu I've been able to use, should be solved in oVirt 4.5. I'm trying to import WS2019 VMs from ESXi 7 as OVFs or even OVAs. But when I do the import and set the OS to Windows Server 2019 x64 in the admin portal, I get the error "Invalid time zone for the given OS type ". If I leave it at Other OS, the import fails with event ID 1153. I've been banging my head against this for over a week (previously couldn't get the management VM to complete setup), so any guidance is appreciated. Let me know what to pull to help me pin this down?
BTW, yes this is a self hosted install as a nested VM on ESXi. Kinda have to right now to test everything (easiest for me over doing a bare metal on my old PowerEdge 2900 at the moment). Running CentOS 9 Stream.
1 year, 2 months
I added a new host not show interface network
by stevenmendoza2103@gmail.com
When I add a new host and I want to assign a logical network to the host interface, the host interface does not appear and I cannot assign the logical network. And it gives me an alert that the installation failed and has an item that says Host has not default route.
1 year, 2 months
Ovirt API: get guest current user
by Giulio Casella
Hi,
is there a way to retrieve user currently logged in on a guest using API
calls?
I see such information in database (specifically in vm_dynamic table),
but nothing in API docs.
Any hints?
TIA,
gc
1 year, 2 months
Cannot find URL for VM Portal
by dirk.westphal@business-it-kiel.de
Hi.
This is my first install of 4.5.4 from the DVD ISO.
I dont find any about the URL for the VM Portal. I have have only the link to the system at port https9090. Did i forgott to install or enable a service?
Regards
Dirk
1 year, 2 months
Hosted-engine restore failing
by Devin A. Bougie
Hi, All. We are attempting to migrate to a new storage domain for our oVirt 4.5.4 self-hosted engine setup, and are failing with "cannot import name 'Callable' from 'collections'"
Please see below for the errors on the console.
Many thanks,
Devin
------
hosted-engine --deploy --restore-from-file=backup.bck --4
...
[ INFO ] Checking available network interfaces:
[ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n'
[ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot load: cannot\n'
[ ERROR ] b"import name 'Callable' from 'collections'\n"
[ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n'
[ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot import name 'Callable' from 'collections' (/usr/lib64/python3.11/collections/__init__.py)\n"
[ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook
[ INFO ] Stage: Clean up
[ INFO ] Cleaning temporary resources
[ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n'
[ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot load: cannot\n'
[ ERROR ] b"import name 'Callable' from 'collections'\n"
[ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n'
[ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot import name 'Callable' from 'collections' (/usr/lib64/python3.11/collections/__init__.py)\n"
[ ERROR ] Failed to execute stage 'Clean up': Failed executing ansible-playbook
[ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20231011110358.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-20231011110352-raupj9.log
1 year, 2 months
hosted-engine --deploy fails with "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined"
by drew.tonnesen@emc.com
As basic as can be install/deploy. Used ovirt-node-ng-installer-latest-el8.iso. Followed steps exactly. Took all defaults possible. After step 23 (Specify the hostname of the deployment host:) the deployment starts. It goes for quite a long time until it fails here, never getting to step 25 and asking me for storage:
2023-11-19 22:19:45,568+0000 DEBUG var changed: host "localhost" var "module_setup" type "<class 'bool'>" value: "true"
1888 2023-11-19 22:19:45,568+0000 DEBUG var changed: host "localhost" var "discovered_interpreter_python" type "<class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>" value: ""/usr/libexec/platform-python""
1889 2023-11-19 22:19:45,568+0000 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'For ce facts gathering', 'task_duration': 1}
1890 2023-11-19 22:19:45,568+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f2028102220> kwargs
1891 2023-11-19 22:19:45,664+0000 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engin e_setup : Set the name for add_host'}
1892 2023-11-19 22:19:45,664+0000 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Set the name for add_host kwargs is_conditional:False
1893 2023-11-19 22:19:45,664+0000 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : Set the name for add_host kwargs
1894 2023-11-19 22:19:45,759+0000 ERROR ansible failed {
1895 "ansible_host": "localhost",
1896 "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml",
1897 "ansible_result": {
1898 "_ansible_no_log": false,
1899 "msg": "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_en gine_setup/tasks/sync_on_engine_machine.yml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for add_host\n ^ he re\n"
1900 },
1901 "ansible_task": "Set the name for add_host",
1902 "ansible_type": "task",
1903 "status": "FAILED",
1904 "task_duration": 0
1905 }
Summary is:
2197 2023-11-19 22:20:02,141+0000 INFO SUMMARY:
2198 Duration Task Name
2199 -------- --------
2200 [ < 1 sec ] Execute just a specific set of steps
2201 [ 00:01 ] Force facts gathering
2202 [ FAILED ] Set the name for add_host
2203 [ < 1 sec ] Fetch the value of HOST_KEY_CHECKING
2204 [ < 1 sec ] Get the username running the deploy
2205 [ FAILED ] Register the engine FQDN as a host
2206 [ FAILED ] Sync on engine machine
2207 [ < 1 sec ] Fetch logs from the engine VM
2208 [ < 1 sec ] Set destination directory path
2209 [ < 1 sec ] Create destination directory
2210 [ < 1 sec ] Find the local appliance image
2211 [ 00:10 ] Give the vm time to flush dirty buffers
2212 [ < 1 sec ] Change ownership of copied engine logs
2213 [ < 1 sec ] Remove local vm dir
2214 [ < 1 sec ] Remove temporary entry in /etc/hosts for the local VM
2215 [ < 1 sec ] Clean local storage pools
2216 [ FAILED ] Destroy local storage-pool localvmk0rv3u2g
2217 [ FAILED ] Undefine local storage-pool localvmk0rv3u2g
2218 [ FAILED ] Destroy local storage-pool {{ local_vm_disk_path.split('/')[5] }}
2219 [ FAILED ] Undefine local storage-pool {{ local_vm_disk_path.split('/')[5] }}
I am using a viable FQDN and IP for my engine which is on the same network as the host. I've been at this for more than a week with different options/OSs. Figured this was the most basic possible configuration and yet it still doesn't work. Incredibly frustrating product.
1 year, 2 months
Weirdness with attempting NFS mount
by Michaal R
I'm attempting to mount a share from a TrueNAS server in oVirt through the Storage > Storage Domains UI as a New Domain. Whenever I try to add the domain (as server:share), it kicks back a Permission Denied error. Looking at the vdsm.log file, I see the below snippet:
2023-11-17 10:05:32,059-0600 INFO (jsonrpc/7) [vdsm.api] START connectStorageServer(domType=1, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'protocol_version': 'auto', 'port': '', 'iqn': '', 'connection': '192.168.1.11:/mnt/POOL0', 'ipv6_enabled': 'false', 'id': '00000000-0000-0000-0000-000000000000', 'user': '', 'tpgt': '1'}]) from=::ffff:192.168.1.16,50468, flow_id=31d18c09-2e12-480f-8d6d-722a9fe78029, task_id=05818e9d-562f-4ca7-a19b-5c3b5a02bae8 (api:31)
2023-11-17 10:05:32,060-0600 INFO (jsonrpc/7) [storage.storageServer] Creating directory '/rhev/data-center/mnt/192.168.1.11:_mnt_POOL0' (storageServer:217)
2023-11-17 10:05:32,060-0600 INFO (jsonrpc/7) [storage.fileutils] Creating directory: /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 mode: None (fileUtils:213)
2023-11-17 10:05:32,060-0600 INFO (jsonrpc/7) [storage.mount] mounting 192.168.1.11:/mnt/POOL0 at /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 (mount:190)
2023-11-17 10:05:32,150-0600 WARN (jsonrpc/7) [storage.oop] Permission denied for directory: /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 with permissions:7 (outOfProcess:176)
2023-11-17 10:05:32,150-0600 INFO (jsonrpc/7) [storage.mount] unmounting /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0 (mount:198)
2023-11-17 10:05:32,200-0600 ERROR (jsonrpc/7) [storage.storageServer] Could not connect to storage server (storageServer:75)
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/vdsm/storage/fileSD.py", line 64, in validateDirAccess
getProcPool().fileUtils.validateAccess(dirPath)
File "/usr/lib/python3.9/site-packages/vdsm/storage/outOfProcess.py", line 178, in validateAccess
raise OSError(errno.EACCES, os.strerror(errno.EACCES))
PermissionError: [Errno 13] Permission denied
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 73, in connect_all
con.connect()
File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 507, in connect
return self._mountCon.connect()
File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 241, in connect
six.reraise(t, v, tb)
File "/usr/lib/python3.9/site-packages/six.py", line 709, in reraise
raise value
File "/usr/lib/python3.9/site-packages/vdsm/storage/storageServer.py", line 233, in connect
fileSD.validateDirAccess(
File "/usr/lib/python3.9/site-packages/vdsm/storage/fileSD.py", line 75, in validateDirAccess
raise se.StorageServerAccessPermissionError(dirPath)
vdsm.storage.exception.StorageServerAccessPermissionError: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/192.168.1.11:_mnt_POOL0'
Stepping it through, am I correct that I'm seeing vdsm not able to create the local directory for the NFS mount? It previously was able to mount an NFS share from the host to itself when I initially setup the server for testing.
When I do an ls -l on the directory it's trying to create the mount point in, I see ownership looks correct.
[root@ovirt ~]# cd /rhev/data-center/
[root@ovirt data-center]# ls
c7d57de0-6ba8-11ee-9a48-00163e1989b9 mnt
[root@ovirt data-center]# ls -l
total 0
drwxr-xr-x. 2 vdsm kvm 66 Nov 15 23:32 c7d57de0-6ba8-11ee-9a48-00163e1989b9
drwxr-xr-x. 3 vdsm kvm 59 Nov 17 10:05 mnt
[root@ovirt data-center]# cd mnt
[root@ovirt mnt]# ls -l
total 0
drwxr-xr-x. 3 vdsm kvm 50 Nov 17 10:14 ovirt.theclocktower.home:_home_ovirt__storage
[root@ovirt mnt]#
Is there something missing? Something that got misconfigured, maybe? Or something I can configure to fix this?
1 year, 2 months
I need help to understand...
by martind@towebs.com
Hi my name is Martin and im currently working in a Hosting Company, we want to Migrate our servers to Ovirt VMS. We want to know if Ovirt is capable of Hosting Loads and we want to know what type of Environment we need to create for this. Thank you
1 year, 2 months