Unable to change the admin passsword on oVirt 4.5.2.5
by Ayansh Rocks
Hi All,
Any idea hot to change password of admin user on oVirt 4.5.2.5 ?
Below is not working -
[root@ovirt]# ovirt-aaa-jdbc-tool user password-reset admin
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
Password:
Reenter password:
updating user admin...
user updated successfully
[root@delhi-test-ovirtm-02 ~]#
Above shows successful but password not changed.
Thanks
1 year, 6 months
Illegal Disk after Removing Snapshot
by Nur Imam Febrianto
Hi,
Using ovirt 4.5.4 with all CentOS 8 Stream Host. Having an issue, whenever we tried to delete any snapshot of any vm, it will failed. Second try will get us succeed. But if the snapshot already deleted, and we shutdown the VM, we cannot turned it on again. It showing illegal disk error. Any idea about this issue ?
Thanks.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
1 year, 6 months
cannot update expired engine certificates?
by michael.d1.holt＠lmco.com
ovirt 4.4.10.x, using self signed certificates with a self hosted engine. apache certs expired, renewed manually via guides provided by RHEL and oVirt using the pki_enroll_pkcs12.sh script. Engine certs are also expired and cannot update certs via gui and no option to renew the certs when running using engine-setup --offline. The error I am getting is a VDSM certificate error on the hosted engine in the engine.log file. I have attempted to manually run the pki_enroll_pkcs12.sh script with "engine" in the name and the subject of the previous engine.cer file with no luck. I copied the p12, key and cert from that attempt into the engine.cer, engine.p12 and engine_id_rsa files, but when booting the hosted engine VM, the first error in the engine.log is "VDC cannot find the engine certificate". This also breaks my access to the web interface for oVirt administration. When the expired engine certs are restored, I have GUI access but still see the VDSM errors on the ovirt-engine. That I hav
e web access with the expired engine certs indicate to me that the apache certificates are correct (but i could be wrong in that evaluation).
Basically i am looking for a way to either force the enroll pki option in the engine-setup --offline script or manually generate and update the engine.cer, engine.p12 (and if needed, but i couldn't determine where it was used) the engine_id_rsa key.
1 year, 6 months
GlusterFS+Virt
by antony.parkin＠graidtech.com
Hi,
Could somebody comment on storage options i.e Gluster or Ceph and when to use each one?
Looking for an architecture which is fully redundant, both at the hypervisor level and at the storage level so needs to include data replication.
thx
1 year, 6 months
VDSM certs expired, manual renewal not working
by cen
Hi
Our VDSM certs have expired, both hosts are unassigned and can't be put
into maintenance from UI.
vdsm-client is not working, times out even with --insecure flag. Does
host and port need to be specified when run locally or should defaults work?
Error in console events is: Get Host Capabilities Failed: PKIX path
validation failed...
I followed a RHV guide for this exact situation and generated new vdsm
certificate using the ovirt-engine CA.
The new cert seems identical to the old one, everything matches (algos,
extensions, CA, CN, SAN etc) just new date.
After restarting libvirtd and vdsmd on the host with new cert in place
the host is still not reachable.
However, error message is now slightly different:
get Host Capabilities failed: Received fatal error: certificate_expired
Cert was replaced in the following locations:
/etc/pki/vdsm/certs/vdsmcert.pem
/etc/pki/vdsm/libvirt-spice/server-cert.pem
/etc/pki/libvirt/clientcert.pem
Is there another location missing? What else can I try?
All help appreciated in advance
1 year, 6 months
ovirt 4.5.4 install failure
by Selçuk N
Hello all,
I tried to install ovirt 4.5.4 on ovirt node install.
*hosted-engine --deploy*
After this step installation is stuck.
*[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be
up]*
I checked the log file and details below.
Apr 20 22:10:18 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running
(85405)
Apr 20 22:10:19 ovirt3 python3[51367]: ansible-ovirt_host_info Invoked with
pattern=name=ovirt3.44c.net auth={'token':
'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJOTXdyenhDY284eERxZVlLaFRhWG5xblVpV0lFNDVBM2VmRzhXdndTaDVBIn0.eyJleHAiOjE2ODIwMzQzNzgsImlhdCI6MTY4MjAxNzA5OCwianRpIjoiODdjNDAwZTItNDZiMS00NmY1LTk2MWMtMWJhMDA3MDAxOGQxIiwiaXNzIjoiaHR0cHM6Ly9lbmcuNDRjLm5ldC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZmFiMDNmM2UtODVmZS00YjQ5LWE5ZWItZTExODRjOTYzYzdjIiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjYwOWJiMmMxLTJkNTItNDc4Zi1hYzg2LWMyMjVlNTVmYTMwNyIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9lbmcuNDRjLm5ldCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWFwcC1hcGkgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIG92aXJ0LWV4dD10b2tlbi1pbmZvOnB1YmxpYy1hdXRoei1zZWFyY2ggcHJvZmlsZSBvdmlydC1leHQ9dG9rZW46cGFzc3dvcmQtYWNjZXNzIiwic2lkIjoiNjA5YmIyYzEtMmQ1Mi00NzhmLWFjODYtYzIyNWU1NWZhMzA3IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.e47PgAtt_Sj-_4IQ8OIQynAV_AvrOfzalhwi1VJapCQB_sdQqxd0jIH7JGVM1a4TGEJb6E5ffTXBocqQabe5pBPIv4kqsgU1iadyTjjDjZ1elECnahPf6lrze-8hEO92GKFOepGLQ-iu7gRilAknvaXhoc309G1hyQvnP4Q-syffw6Eoo4RmgnLnztnPzsxBtGgkZrzAwFfTNDtdS2uj5lvzzAEIfvDPRFTjJhYwKXSx2hC1lnhXnmv1XEtCfXZZ3qqarXw8GAvOQbe10xklm5UAtu--C8NX32DE6659QtEqk-5g52SdFWIic_OlZ5-obHn3jOllo8qnsb-6mfEn_w',
'url': 'https://eng.44c.net/ovirt-engine/api', 'ca_file': None, 'insecure':
True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None,
'hostname': None, 'username': None, 'password': None} fetch_nested=False
nested_attributes=[] follow=[] all_content=False cluster_version=None
*Apr 20 22:10:22 ovirt3 journal[47971]: Invalid value '-1' for 'cpu.max':
Invalid argument*
Apr 20 22:10:23 ovirt3 sssd_kcm[50811]: Shutting down (status = 0)
Apr 20 22:10:23 ovirt3 systemd[1]: sssd-kcm.service: Deactivated
successfully.
Apr 20 22:10:23 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running
(85400)
Apr 20 22:10:28 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running
(85395)
What did I did wrong?
Thanks.
1 year, 6 months
checking engine vm status during global maintenance
by Alexey Valkov
Hi all,
I tried to check engine status (via hosted-engine --vm-status) during global maintenance in oVirt 4.5.1 and discovered that
it showed me status as it was just before entering global maintenance.
Is it by design? And HA agent doesn't monitor and therefore doesn't update Engine VM status?
If I remember right in oVirt 4.2 hosted-engine --vm-status showed correct status of Engine VM regardless of Global maintenance.
I shutted down the engine but the output of hosted-engine --vm-status was
Engine status : {"vm": "up", "health": "good", "detail": "Up"}
Notice
!! Cluster is in GLOBAL MAINTENANCE mode !!
existed in the output.
Host timestamp and extra metadata was up to date.
All rest info looked good.
Thi is my second attempt to ask the question (first was at 24/04 and still is being moderated).
--
Best regards
Alexei
1 year, 6 months
richiesta accesso Zanata
by Rosario Grasso
Buongiorno,
la presente per richiedere l'accesso a Zanata in lingua inglese e se
possibile anche in italiano.
Saluti,
RG
1 year, 6 months
