I have an environment where the engine wouldn’t start and the certificate
expiry dates were as follows.
Host1 - 25th Sep 2022
Host2 - 11th Aug 2022
Host3 - 11th Aug 2022
I copied the vdsm certs from Host1 to Host2 & Host3
Engine then started on Host1 and then backed up.
Engine cert expiry
I made a backup of the /etc/pki/ directory and subfolders prior to overwriting
the certs.
Copying an indate cert was the only way I couldget the engine started.
Is there a commandline procedure to do the same task as 'Enroll Certificates'
via the WebUI?
Shimme
Hi,
I hope you have not erased old certificates which you must restore back.
You can't copy certificates from one host to another, it will not work.
Try restore old certificates and simply run again engine-setup.
On 9/6/22 23:06, si...@justconnect.ie wrote:
I have an environment where the
I tried your 'Try restore old certificates and simply run again engine-setup'
but the validation fails with:
-
[ ERROR ] It seems that you are
Hi there,
last days we are facing issues with paused VMs (in past it was for few
second to resize lv device), but now it doesn't resume. we migrated to
4.5.2 cluster, this never happened before with the same storage.
there is almost notning in engine log
2022-09-06 09:47:11,160+02 INFO
Hi, for those who remember the Linux Counter project, if you'd like other
to know you're using oVirt and know some details about your deployment,
here's a way to count you in:
https://ovirt.org/community/ovirt-counter.html
Enjoy!
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R
Hi all,
as a final stage of out gerrit to github transition that started ~9 months ago
we are planning to eliminate the use of bugzilla.redhat.com for all oVirt
projects (bugs with Classification: "oVirt") and use the native issue tracking
in github as well. We used to have integrations with
I really don't understand, I was monitoring vdsm.log of one node (node2)
And I saw a complain:
2022-09-06 14:08:27,105+ ERROR (check/loop) [storage.monitor] Error
checking path
/rhev/data-center/mnt/glusterSD/ovirt-node2.ovirt:_gv1/45b4f14c-8323-482f-90ab-99d8fd610018/dom_md/metadata
It appears that this error is somehow related to the infiniband network. I
found that if I did not assign an IP to the ib0 adapter then
ovirt-hosted-engine-setup would complete successfully. Once the cluster was
up, I could go in and create a new non-vm network, assign gluster and
migration roles,
9 matches
Mail list logo