Krutika Dhananjay wrote:
Yes, so the bug has been fixed upstream and the backports to release-7
and release-8 of gluster pending merge. The fix should be available in
the next .x release of gluster-7 and 8. Until then like Nir suggested,
please turn off performance.stat-prefetch on your
Hi,
Your gluster mount option is not correct.
> You need 'backup-volfile-servers=storagehost2:storagehost3' (without the
> volume name as they all have thaylt volume) .
yes, of course. I'm sorry but the appended volume name was a mistake I made
for the email and not during deployment where only
Hi,
I have the following two components:
1.) A freshly installed VM host (oVirt Node 4.4.0 release ISO)
2.) 3 storage hosts, also freshly installed from oVirt Node 4.4.0
release ISO
The storage hosts have been successfully installed with Gluster (through
Cockpit). They have two volumes,
Hi,
I think I know (it's hard to tell without more logs, but anyway):
It's because your PKI was expired and thus renewed. If you used the
command line to restore/deploy, you were also asked:
'Renew engine CA on restore if needed? Please notice '
Hi,
Yedidyah Bar David wrote:
In any case (perhaps not relevant to you right now, if indeed engine-setup
succeeded), usually the engine vm is left running at the end of a failed
deploy. If it's still the local vm, you can find its IP address by searching
the ansible logs for local_vm_ip, then
Hi there,
You should also see one or more ERROR messages, can you check/post them?
There is one error message that immediately follows, if that helps:
2020-05-27 00:17:12,397+0200 ERROR otopi.context
context._executeMethod:154 Failed to execute stage 'Closing up': Failed
executing
Hi there,
I'm a bit puzzled about an possible upgrade paths from a 4.3 cluster to
version 4.4 in a self-hosted engine environment.
My idea was:
Set up a new host with a clean ovirt node 4.4 installation, then deploy the
hosted engine on this with a restored backup from the production cluster
7 matches
Mail list logo
