Continuing HE install from lost connection
by Glenn Marcy
I ran the Prepare VM stage of the GUI HostedEngine install and when I came back it had disconnected. Looking at the logs and the current status everything appears to be just fine, but there doesn't seem to be any way in the GUI to continue where it left off. I was wondering if there was some way to provide the hosted_storage information requested in the next panel and complete the installation, perhaps with the command line, instead of redoing all of the work that has already been completed successfully?
Regards,
Glenn Marcy
3 years, 10 months
Advise Needed - Hosted Engine Minor Update
by jrbdeguzman05＠gmail.com
Hi Guys!
How do you usually backup your hosted engine prior minor updates?
I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently. I’ve used engine-backup before updating and for restore. However, the problem I’m encountering now is that, it looks like the hosted-engine settings are only being restored. The version is still 4.3.9 when I’m trying to revert it to 4.3.8.
Am I missing some steps aside from engine-backup —restore? I saw on old posts that snapshots of hosted engine is not a recommended step before upgrade/update.
Appreciate your help in advance!
3 years, 10 months
LDAP setup fails on 4.4 reading PEM file
by Stack Korora
Greetings,
I'm having some issues getting LDAP working on CentOS 8 with oVirt 4.4.
I would appreciate some help please.
When I run ovirt-engine-extension-aaa-ldap-setup I choose "11 - RFC-2307
Schema (Generic)" because that's what my LDAP guy said I should do. :-)
Next I select the default Yes for "Use DNS".
I select 4 for "Failover between multiple hosts".
I put in my two hosts "svr1.my.domain srv2.my.domain".
To select the protocol I type "ldaps".
To select the method to obtain the PEM I type "File".
Then the "File path". A full path to the file. Not quoted. Yes, I
checked that I typed it correct. I can copy-paste into "ls" and it's
fine with the correct read permissions and everything. (I can't copy
paste into the script but that's another issue.)
It immediately fails with:
[ ERROR ] Failed to execute stage 'Environment customization': a
byte-like object is required, not 'str'
There is a log file, here is the snippet at the point it goes wrong.
2020-06-11 11:35:49,915-0500 DEBUG otopi.plugins.otopi.dialog.human
dialog.__logString:204 DIALOG:SEND File path:
2020-06-11 11:36:24,373-0500 DEBUG otopi.plugins.otopi.dialog.human
dialog.__logString:204 DIALOG:RECEIVE
/etc/pki/ca-trust/source/anchors/Infrastructure.pem
2020-06-11 11:36:24,375-0500 DEBUG otopi.context
context._executeMethod:145 method exception
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-engine-extension-aaa-ldap/setup/bin/../plugins/ovirt-engine-extension-aaa-ldap/ldap/common.py",
line 781, in _customization_late
cacert, cacertfile, insecure = self._getCACert()
File
"/usr/share/ovirt-engine-extension-aaa-ldap/setup/bin/../plugins/ovirt-engine-extension-aaa-ldap/ldap/common.py",
line 357, in _getCACert
_cacertfile.write('\n'.join(cacert) + '\n')
File "/usr/lib64/python3.6/tempfile.py", line 485, in func_wrapper
return func(*args, **kwargs)
TypeError: a bytes-like object is required, not 'str'
2020-06-11 11:36:24,376-0500 ERROR otopi.context
context._executeMethod:154 Failed to execute stage 'Environment
customization': a bytes-like object is required, not 'str'
2020-06-11 11:36:24,376-0500 DEBUG otopi.context
context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN
2020-06-11 11:36:24,376-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV BASE/error=bool:'True'
2020-06-11 11:36:24,376-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class
'TypeError'>, TypeError("a bytes-like object is required, not 'str'",),
<traceback object at 0x7f7e053a4448>)]'
2020-06-11 11:36:24,377-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/hosts=str:'svr1.my.domain
srv2.my.domain'
2020-06-11 11:36:24,377-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/protocol=str:'ldaps'
2020-06-11 11:36:24,377-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/serverset=str:'failover'
2020-06-11 11:36:24,377-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/useDNS=bool:'True'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV
QUESTION/1/OVAAALDAP_LDAP_CACERT_FILE=str:'/etc/pki/ca-trust/source/anchors/Infrastructure.pem'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV
QUESTION/1/OVAAALDAP_LDAP_CACERT_METHOD=str:'file'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV
QUESTION/1/OVAAALDAP_LDAP_PROTOCOL=str:'ldaps'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_SERVERSET=str:'4'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_USE_DNS=str:'yes'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:775 ENV
QUESTION/2/OVAAALDAP_LDAP_SERVERSET=str:'svr1.my.domain srv2.my.domain'
2020-06-11 11:36:24,378-0500 DEBUG otopi.context
context.dumpEnvironment:779 ENVIRONMENT DUMP - END
Can someone help please?
Thanks!
3 years, 10 months
It looks like big changes are happening, Centos moving from 8.1.1911 to 8.2.2004 perhaps
by Glenn Marcy
I hope this situation settles down before rc5
trying to run 4.4.1-rc4 hosted engine setup, got
[ ERROR ] fatal: [localhost -> ovirt-engine.example.com]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured:
Problem: package ovirt-engine-4.4.1.3-1.el8.noarch requires ovirt-provider-ovn >= 1.2.1, but none of the providers can be installed
- package ovirt-provider-ovn-1.2.30-1.el8.noarch requires openvswitch >= 2.7, but none of the providers can be installed
- cannot install the best candidate for the job
- nothing provides librte_bitratestats.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_bus_pci.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_bus_vdev.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_bus_vmbus.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_cmdline.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_common_cpt.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_eal.so.9()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_eal.so.9(DPDK_17.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_eal.so.9(DPDK_18.11)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_eal.so.9(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11(DPDK_17.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11(DPDK_18.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11(DPDK_18.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11(DPDK_18.11)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ethdev.so.11(DPDK_2.2)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_gro.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_gso.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_hash.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ip_frag.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_kvargs.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_latencystats.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mbuf.so.4()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mbuf.so.4(DPDK_2.1)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_member.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mempool.so.5()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mempool.so.5(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mempool.so.5(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mempool_bucket.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mempool_ring.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_mempool_stack.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_meter.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_meter.so.2(DPDK_18.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_meter.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_metrics.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_net.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pci.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pdump.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_bnxt.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_e1000.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_enic.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_failsafe.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_i40e.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_ixgbe.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_mlx4.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_mlx5.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_netvsc.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_nfp.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_qede.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_ring.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_ring.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_tap.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_vdev_netvsc.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_vhost.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_pmd_virtio.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ring.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_ring.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_vhost.so.4()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_vhost.so.4(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_vhost.so.4(DPDK_17.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_vhost.so.4(DPDK_17.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_vhost.so.4(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64
- nothing provides librte_vhost.so.4(DPDK_2.1)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64", "rc": 1, "results": []}
3 years, 10 months
Re: Problem with oVirt 4.4
by Yedidyah Bar David
On Mon, Jun 15, 2020 at 2:13 PM minnie.du(a)vinchin.com
<minnie.du(a)vinchin.com> wrote:
>
> Hi,
>
> I tried to send the log to you by email, but it fails. So I have sent them to Google Drive. Please go to the link below to get them:
>
> https://drive.google.com/file/d/1c9dqkv7qyvH6sS9VcecJawQIg91-1HLR/view?us...
> https://drive.google.com/file/d/1zYfr_6SLFZj_IpM2KQCf-hJv2ZR0zi1c/view?us...
I did get them, but not engine logs. Can you please attach them as well? Thanks.
vdsm.log.61 has:
2020-05-26 14:36:49,668+0000 ERROR (jsonrpc/6) [virt.vm]
(vmId='e78ce69c-94f3-416b-a4ed-257161bde4d4') Live merge failed (job:
1c308aa8-a829-4563-9c01-326199c3d28b) (vm:5381)
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 5379, in merge
bandwidth, flags)
File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f
ret = attr(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py",
line 131, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/common/function.py",
line 94, in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python3.6/site-packages/libvirt.py", line 728, in blockCommit
if ret == -1: raise libvirtError ('virDomainBlockCommit() failed', dom=self)
libvirt.libvirtError: internal error: qemu block name
'json:{"backing": {"driver": "qcow2", "file": {"driver": "file",
"filename": "/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/08f91e3f-f37b-4434-a183-56478b732c1b"}},
"driver": "qcow2", "file": {"driver": "file", "filename":
"/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/5ba0d7e5-afa8-4d75-bc5a-1b077955a990"}}'
doesn't match expected
'/rhev/data-center/mnt/192.168.67.8:_root_nfs_ovirt44__vm/01477dfd-1f4c-43d4-b000-603c6ed839b6/images/6140b67d-9895-4ee6-90a9-5410de8b5a01/5ba0d7e5-afa8-4d75-bc5a-1b077955a990'
Adding Eyal. Eyal, can you please have a look? Thanks.
>
> Best regards,
>
> Minnie Du--Presales & Business Development
>
> Mob : +86-15244932162
> Tel : +86-28-85530156
> Skype :minnie.du@vinchin.com
> Email: minnie.du(a)vinchin.com
> Website: www.vinchin.com
>
> F5, Building 8, National Information Security Industry Park, No.333 YunHua Road, Hi-Tech Zone, Chengdu, China
>
>
> From: Yedidyah Bar David
> Date: 2020-06-15 15:42
> To: minnie.du
> CC: users
> Subject: Re: [ovirt-users] Problem with oVirt 4.4
> On Mon, Jun 15, 2020 at 10:39 AM <minnie.du(a)vinchin.com> wrote:
> >
> > We have met a problem when testing oVirt 4.4.
> >
> > Our VM is on NFS storage. When testing the snapshot function of oVirt 4.4, we created snapshot 1 and then snapshot 2, but after clicking the delete button of snapshot 1, snapshot 1 failed to be deleted and the state of corresponding disk became illegal. Removing the snapshot in this state requires a lot of risky work in the background, leading to the inability to free up snapshot space. Long-term backups will cause the target VM to create a large number of unrecoverable snapshots, thus taking up a large amount of production storage. So we need your help.
>
> Can you please share relevant parts of engine and vdsm logs? Perhaps
> open a bug and attach all of them, just in case.
>
> Thanks!
> --
> Didi
>
>
--
Didi
3 years, 10 months
Re: [ANN] oVirt 4.4.1 Fourth Release Candidate is now available for testing
by Glenn Marcy
This candidate changes the version of the OpenStack Java API from 3.2.8 to
3.2.9, which isn't available in the repositories.
Installation produces the error:
[ ERROR ] fatal: [localhost -> ovirt-engine.example.com]: FAILED! =>
{"changed": false, "failures": [], "msg": "Depsolve Error occured:
Problem: cannot install the best candidate for the job
- nothing provides openstack-java-cinder-client >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-cinder-model >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-client >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-glance-client >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-glance-model >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-keystone-client >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-keystone-model >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-quantum-client >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-quantum-model >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch
- nothing provides openstack-java-resteasy-connector >= 3.2.9 needed by
ovirt-engine-4.4.1.3-1.el8.noarch", "rc": 1, "results": []}
Regards,
Glenn Marcy
3 years, 10 months
Ansible ovirt.hosts has no port setting
by Paul-Erik Törrönen
Running oVirt 4.4.
While setting up ovirt with ansible, I noticed that there is no
parameter for setting the ssh port of the hosts (which is present if one
adds an host on the GUI).
I tried adding the port as a part of the address, but that field is
apparently evaluated as FQDN only.
I did circumvent this by adding FQDN-labeled sections with
Port-definition ~/.ssh/config for ovirt-user on the engine-machine (not
hosted), but this only got me a step further since the configuration in
the engine still is without a port definition and falls back to 22 as a
result.
Running the ansible playbook with -vvv I can see the following:
Using module file
/usr/lib/python3.6/site-packages/ansible/modules/cloud/ovirt/ovirt_host.py
<127.0.0.1> PUT
/root/.ansible/tmp/ansible-local-3041af74sxb1/tmpjlyq4ic8 TO
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/AnsiballZ_ovirt_host.py
<127.0.0.1> EXEC /bin/sh -c 'chmod u+x
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/AnsiballZ_ovirt_host.py
&& sleep 0'
<127.0.0.1> EXEC /bin/sh -c '/usr/bin/python3.6
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/AnsiballZ_ovirt_host.py
&& sleep 0'
<127.0.0.1> EXEC /bin/sh -c 'rm -f -r
/root/.ansible/tmp/ansible-tmp-1592049378.2474232-3179-247712281303744/
> /dev/null 2>&1 && sleep 0'
The full traceback is:
Traceback (most recent call last):
File
"/tmp/ansible_ovirt_host_payload_zeyzwhlj/ansible_ovirt_host_payload.zip/ansible/modules/cloud/ovirt/ovirt_host.py",
line 639, in main
File
"/tmp/ansible_ovirt_host_payload_zeyzwhlj/ansible_ovirt_host_payload.zip/ansible/module_utils/ovirt.py",
line 785, in action
poll_interval=self._module.params['poll_interval'],
File
"/tmp/ansible_ovirt_host_payload_zeyzwhlj/ansible_ovirt_host_payload.zip/ansible/module_utils/ovirt.py",
line 359, in wait
raise Exception("Error while waiting on result state of the entity.")
Exception: Error while waiting on result state of the entity.
failed: [localhost] (item=myHost) => {
"ansible_loop_var": "item",
"changed": false,
"invocation": {
"module_args": {
"activate": true,
"address": null,
"check_upgrade": true,
"cluster": null,
"comment": null,
"fetch_nested": false,
"force": false,
"hosted_engine": null,
"id": null,
"iscsi": null,
"kdump_integration": null,
"kernel_params": null,
"name": "myHost",
"nested_attributes": [],
"override_display": null,
"override_iptables": null,
"password": null,
"poll_interval": 3,
"power_management_enabled": null,
"public_key": true,
"reboot_after_upgrade": true,
"spm_priority": null,
"state": "reinstalled",
"timeout": 600,
"vgpu_placement": null,
"wait": true
}
},
"item": {
"address": "myHost.myDomain",
"affinity_labels": [],
"auto_numa_status": "unknown",
"certificate": {
"organization": "myDomain",
"subject": "O=myDomain,CN=myHost.myDomain"
},
"cluster": {
"href":
"/ovirt-engine/api/clusters/3642e08b-1311-4f8a-803b-897321513b0b",
"id": "3642e08b-1311-4f8a-803b-897321513b0b"
},
"comment": "",
"cpu": {
"speed": 0.0,
"topology": {}
},
"device_passthrough": {
"enabled": false
},
"devices": [],
"external_network_provider_configurations": [],
"external_status": "ok",
"hardware_information": {
"supported_rng_sources": []
},
"hooks": [],
"href":
"/ovirt-engine/api/hosts/22623d77-069e-4feb-86db-03b08bc67c1a",
"id": "22623d77-069e-4feb-86db-03b08bc67c1a",
"katello_errata": [],
"kdump_status": "unknown",
"ksm": {
"enabled": false
},
"max_scheduling_memory": 0,
"memory": 0,
"name": "myHost",
"network_attachments": [],
"nics": [],
"numa_nodes": [],
"numa_supported": false,
"os": {
"custom_kernel_cmdline": ""
},
"permissions": [],
"port": 54321,
"power_management": {
"automatic_pm_enabled": true,
"enabled": false,
"kdump_detection": true,
"pm_proxies": []
},
"protocol": "stomp",
"se_linux": {},
"spm": {
"priority": 5,
"status": "none"
},
"ssh": {
"fingerprint": "SHA256:abc...",
"port": 22
},
"statistics": [],
"status": "install_failed",
"storage_connection_extensions": [],
"summary": {
"total": 0
},
"tags": [],
"transparent_huge_pages": {
"enabled": false
},
"type": "rhel",
"unmanaged_networks": [],
"update_available": false,
"vgpu_placement": "consolidated"
},
"msg": "Error while waiting on result state of the entity."
}
The ssh-key containing the fingerprint still has the port set as 22.
Any chance of getting the port added to the ansible ovirt.hosts module?
With regards,
Poltsi
3 years, 10 months
Problem with oVirt 4.4
by minnie.du＠vinchin.com
We have met a problem when testing oVirt 4.4.
Our VM is on NFS storage. When testing the snapshot function of oVirt 4.4, we created snapshot 1 and then snapshot 2, but after clicking the delete button of snapshot 1, snapshot 1 failed to be deleted and the state of corresponding disk became illegal. Removing the snapshot in this state requires a lot of risky work in the background, leading to the inability to free up snapshot space. Long-term backups will cause the target VM to create a large number of unrecoverable snapshots, thus taking up a large amount of production storage. So we need your help.
3 years, 10 months
Engine is one month ahead
by Strahil Nikolov
Hello All,
I have a problem which started after the latest patching 4.3.9 to 4.3.10 .
Symptoms so far:
1. Engine reports that Hypervisours are drifting too much
2. ETL service stopped working
3. Web UI constantly notifies me that the nodes are again active (fills the screen till the bottom)
So far I have found an issue with one of the Hypervisours and after removing chrony's drift file and reboot - no more issues are observed.
I found in the DB that DWH last update was one month (yes, that's July) ahead , so updating it to June has fixed the ETL issue.
The problem with the constant "Host has been activated" was fixed by updating the Engine database , table Job (July was changed with June).
The only problem I have now is that every event in the Web (and in the DB of course) is pointing to July.
Any ideas how the engine is taking the time ,cause a restart doesn't fix the issue?
As you can see both Hypervisours and HE VM are OK:
[root@engine ~]# ntpdate -q time.cloudflare.com
server 162.159.200.1, stratum 3, offset 0.000816, delay 0.02812
server 162.159.200.123, stratum 3, offset 0.000939, delay 0.02834
14 Jun 11:40:05 ntpdate[30135]: adjust time server 162.159.200.1 offset 0.000816 sec
[root@engine ~]# logout
Connection to engine closed.
[root@ovirt1 ~]# for i in ovirt{1..3} ; do ntpdate -q time.cloudflare.com ; done
server 162.159.200.123, stratum 3, offset 0.002658, delay 0.02948
server 162.159.200.1, stratum 3, offset 0.001741, delay 0.02768
14 Jun 11:40:24 ntpdate[29562]: adjust time server 162.159.200.1 offset 0.001741 sec
server 162.159.200.1, stratum 3, offset 0.002529, delay 0.02914
server 162.159.200.123, stratum 3, offset 0.001931, delay 0.02788
14 Jun 11:40:31 ntpdate[29597]: adjust time server 162.159.200.123 offset 0.001931 sec
server 162.159.200.123, stratum 3, offset 0.001765, delay 0.02742
server 162.159.200.1, stratum 3, offset 0.002551, delay 0.02924
14 Jun 11:40:37 ntpdate[29618]: adjust time server 162.159.200.123 offset 0.001765 sec
Best Regards,
Strahil Nikolov
3 years, 10 months
ovirt 4.3.10 Web UI constantly "finished activating host"
by Strahil Nikolov
I'm not sure if this one is related to "time shift" in the DB (as I found that dwh_history_timekeeping had some entries 1 month ahead/ETL service issues also/, but I keep getting spammed that the host has been activated.
Any hint ?
Best Regards,
Strahil Nikolov
3 years, 10 months
