[ovirt-users] Geo-replication configuration problem
Hello,
I have two GlusterFS clusters with Centos 9 Stream managed by oVirt 4.5
(standalone Manager with local databases) and when I want to configure
geo-replication I receive this error message:
Oct 10 15:15:15 myhostname vdsm[222665]: ERROR TypeError raised by dispatched
function
Traceback (most recent call last):
File
"/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 194, in
_dynamicMethod
result = fn(*methodArgs)
File
"/usr/lib/python3.9/site-packages/vdsm/gluster/apiwrapper.py", line 300, in
geoRepKeysUpdate
return
self._gluster.geoRepKeysUpdate(userName, geoRepPubKeys)
File
"/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 95, in wrapper
rv = func(*args, **kwargs)
File
"/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 720, in
geoRepKeysUpdate
self.svdsmProxy.glusterUpdateGeoRepKeys(userName, geoRepPubKeys)
File
"/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 56, in
__call__
return callMethod()
File
"/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in
getattr(self._supervdsmProxy._svdsm,
self._funcName)(*args,
File "", line 2, in
glusterUpdateGeoRepKeys
File
"/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod
raise convert_to_error(kind, result)
TypeError: a bytes-like object is
required, not 'str'
Oct 10 15:15:15 myhostname vdsm[222665]: ERROR Internal server error
Traceback (most recent call last):
File
"/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 194, in
_dynamicMethod
result = fn(*methodArgs)
File
"/usr/lib/python3.9/site-packages/vdsm/gluster/apiwrapper.py", line 300, in
geoRepKeysUpdate
return
self._gluster.geoRepKeysUpdate(userName, geoRepPubKeys)
File
"/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 95, in wrapper
rv = func(*args, **kwargs)
File
"/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 720, in
geoRepKeysUpdate
self.svdsmProxy.glusterUpdateGeoRepKeys(userName, geoRepPubKeys)
File
"/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 56, in
__call__
return callMethod()
File
"/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in
getattr(self._supervdsmProxy._svdsm,
self._funcName)(*args,
File "", line 2, in
glusterUpdateGeoRepKeys
File
"/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod
raise convert_to_error(kind, result)
TypeError: a bytes-like object is
required, not 'str'
During handling of the above exception,
another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3.9/site-packages/yajsonrpc/__init__.py", line 349, in
_handle_request
res = method(**params)
File
"/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 201, in
_dynamicMethod
raise InvalidCall(fn, methodArgs, e)
vdsm.rpc.Bridge.InvalidCall: Attempt to
call function: > with
arguments: ('geoaccount', ['command="/usr/libexec/glusterfs/gsyncd" ssh-rsa
...']) error: a bytes-like object is required, not 'str'
Can you tell me what is wrong?
Thank you,
Dan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovir
[ovirt-users] hosted-engine-setup --deploy fail on Centos Stream 8
Hy,
I am trying to install ovirt 4.5 on a 4-host cluster running Centos Stream 8,
but the engine does not start and the whole process fails.
Here is my procedure
dnf install centos-release-ovirt45
dnf module reset virt
dnf module enable virt:rhel
dnf install ovirt-engine-appliance
dnf install ovirt-hosted-engine-setup
The latest version of ansible [ansible-core 2.13] uses python3.9 and the
installation fails because some python3.9 modules are missing
[python39-netaddr, python39-jmespath] and cannot be installed [conflict
python3-jmespath]. So I downgraded ansible to ansible-core 2.12
dnf downgrade ansible-core
Now
hosted-engine-setup --deploy --4
goes proceed further but stops because it cannot start the engine
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a
failure]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not
up, please check logs, perhaps also on the engine machine"}
I looked into the log file
/var/log//ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm-20221007132728-yp7cd1.log
and I found the following error:
2022-10-07 13:28:30,881+0200 ERROR ansible failed {
"ansible_host": "localhost",
"ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml",
"ansible_result": {
"_ansible_no_log": false,
"changed": false,
"cmd": [
"virsh",
"net-undefine",
"default"
],
"delta": "0:00:00.039258",
"end": "2022-10-07 13:28:30.710401",
"invocation": {
"module_args": {
"_raw_params": "virsh net-undefine default",
"_uses_shell": false,
"argv": null,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"stdin": null,
"stdin_add_newline": true,
"strip_empty_ends": true,
"warn": false
}
},
"msg": "non-zero return code",
"rc": 1,
"start": "2022-10-07 13:28:30.671143",
"stderr": "error: failed to get network 'default'\nerror: Network not
found: no network with matching name 'default'",
"stderr_lines": [
"error: failed to get network 'default'",
"error: Network not found: no network with matching name 'default'"
],
"stdout": "",
"stdout_lines": []
},
"ansible_task": "Update libvirt default network configuration, undefine",
"ansible_type": "task",
"status": "FAILED",
"task_duration": 0
}
Needless to say
firewalld and libvirtd are both up
and virsh net-list gives:
Name StateAutostart Persistent
;vdsmdummy; active no no
default active no yes
I googled around without success.
Has anyone had similar problems?
End of past July I installed Ovirt on another cluster running Centos Stream 8
following the procedure I just described with no problem.
If needed I can post all log files.
Thanks for the help.
Best
Andrea
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JI72US3JIOXBWTMTVVGDLVAZV7UJXBYF/
[ovirt-users] Re: OVS Task Error when Add EL Host
I just hit the same error. Initially I got it on the beginning of installation (both netaddr and jmespath were not found). Seems that python3.9 is used so initially I solved it via pip3.9 install. Alternatively you can get the rpm packages from epel. The same issues is on ovirt VM side. As a workaround I started deployment with pause (hosted-engine --deploy --ansible-extra-vars=he_pause_host=true). With that you can ssh to the instance, and manually run pip install which got me: 'Successfully installed jmespath-1.0.1 netaddr-0.8.0'. This is just a workaround and proper fix should be reflected in engine VM image, or on the repos side. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YBFXY5GZGRNYIBIZOMW6Y6Y2NHC7R46B/
[ovirt-users] SSL error on oVirt 4.2.4
Hello I have oVirt cluster with 25 hypervisors that has been running fine for a couple of years and today all of a sudden engine was getting ssl errors talking to the hypervisors. Error in engine.log is: 2022-10-10 16:20:23,562-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Received fatal alert: unknown_ca Certificates don't seem expired and I ran the command: openssl x509 -noout -in /etc/pki/ovirt-engine/ca.pem -fingerprint openssl x509 -noout -in /etc/pki/vdsm/certs/cacert.pem -fingerprint # openssl x509 -noout -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -fingerprint # openssl x509 -noout -in /etc/pki/vdsm/libvirt-vnc/ca-cert.pem -fingerprint # openssl x509 -noout -in /etc/pki/CA/cacert.pem -fingerprint Those commands show that the fingerprints are the same. openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/engine.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/apache.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/websocket-proxy.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/jboss.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/imageio-proxy.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer These verification commands come back as OK. I am having trouble finding my problem. Does anyone have any suggestions? I am not finding any hits on google and unknown_ca. Also the vdsm log on hypervisors has this: 2022-10-10 15:54:42,843-0500 ERROR (Reactor thread) [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: SSLError, address: :::192.168.50.26 (sslutils:263) Thanks Don ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OQMJ6FOO3YZW4XIOIDYO235KKGKLCH67/
[ovirt-users] Re: Network Interface Already In USe - Self-Hosted Install
Hi All, OK, so after much reading of logs, Ansible files, blog posts, documentation, and much gnashing of teeth, glasses of bourbon, language to make a sailor blush, tears, blood, sweat, and various versions of "DOH!", I finally worked out what was wrong - what I did wrong - and so I'm putting it down here so that the next person who comes along with the same (or a similar) issue doesn't have to go through what I went through - and I'm including a couple of suggestions to the devs/doco writers which (I believe) would have stopped me from making my mistake in the first place. When I did my install I used the command: ~~~ hosted-engine --deploy --4 --ansible-extra-vars=he_ipv4_subnet_prefix=172.16.1 ~~~ I did this because we're running an IPv4 network and because the oVirt Engine needs to be on the 172.16.1.0/24 network - and that's what I thought the "he_ipv4_subnet_prefix" option did, and I was trying to let the deployment script know this in advance instead of having to discover this itself. Now that I've gone back over *all* the doco I realise that the "he_ipv4_subnet_prefix" option is *not* used for this purpose, but is instead used for the *temporary* ip address of the deployment engine when the default subnet of 192.168.222.0/24 is not available. Because I was specifying the 172.16.1.0/24 network (which is already in use) the deployment failed because it was attempting to create that network as a temporary network for the initial deployment. So yes, as I said, my fault - no question about that at all. Some suggestions: Although it is stated in the documentation - Installing oVirt As A Self-Hosted Engine Using The Command Line, section 2.3.2 (https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#Network-range-for-SHE-deployment_SHE_cli_deploy) - (I believe) it is not very clear what is happening here, so a "Note:" or some sort of statement explicitly stating what this is used for might be in order. For example, here is the note I made for our team in our internal documentation: ~~~ **Note:** he_ipv4_subnet_prefix=x.x.x: - This is a temporary network prefix if 192.168.222.0/24 (the default) is not available - this is ***NOT*** the final working subnet of the oVirt Engine. ~~~ I also believe - quite strongly, in fact - that having the entire deployment hidden behind the "black box" that is the Ansible deployment - while making things easy by automating the deployment - makes troubleshooting more difficult. I believe that if there was a definite "Step-By-Step" list of what was going on behind the scenes - perhaps as an Appendix to the documentation - then the mistake I made would have been a lot harder to make - ie if there was such a list then it would have been less likely to make the assumption I made. I'm thinking something along the lines of (and I am aware that what follows is not correct): ~~~ 1. Collect info - this is stored in "/path/file" temporarily. 2. Install Deployment VM. 3. Deployment VM creates internal bridge - this uses 192.168.222.0/24 by default but can be overridden by "he_ipv4_subnet_prefix". 4. Deployment Engine creates oVirt Engine. etc, etc, etc ~~~ Anyway, that's my feedback / suggestions / mea culpa / whatever. :-) Cheers Dulux-Oz ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FUBH7MVCYMSGLWXEXCVQIM6QHDJUM6GV/
[ovirt-users] Re: Pre-Installing OpenVSwitch For oVirt Self-Hoster Install - Issues?
Hi All, OK, so I actually ended up solving the underlying issue that I was trying to work around with this - see https://lists.ovirt.org/archives/list/users@ovirt.org/thread/UYX2L76UOAMAOQ2IWCQ4KJIJHOFXKNFJ/ for details Cheers Dulux-Oz ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZMSTBZBB4RNUXEEXC5KPPBZJEAST7EGL/
[ovirt-users] Convert raw images to qcow format
Hi there I want to create incremental backups of a few imported VMs, but the VM disks are in the raw disk format which does not support incremental backup. Is there a way to convert existing disks from raw to qcow in oVirt? Since qemu-img can do this,I assume there must be a way.. Thank you Jonas___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OYDUK5LEV2HPZNGHT5KBNXVNCMLMNNY2/
