On Thu, Nov 4, 2021 at 6:51 PM Kapetanakis Giannis <
bil...@edu.physics.uoc.gr> wrote:
> On 27/04/2021 17:12, cape...@labri.fr wrote:
> > Hi,
> >
> > Since a few weeks, we are not able to connect to the vmconsole proxy:
> > $ ssh -t -p ovirt-vmconsole@ovirt
> > ovirt-vmconsole@ovirt: Permissi
running engine-setup should give you the
opportunity to update expired or expiring certificates.
>
> If you don't want to upgrade your system you can run it with the --offline
> option.
>
>
Thank you!
Richard Chan
___
Users mail
On Thu, Nov 18, 2021 at 2:14 PM Christoph Timm wrote:
>
> looks like they are already aware of it:
Indeed.
> https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/BDYP62MAJL2QVQZ7RHM2USZD4HXBGUA6/
Now replied there, and created this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=20246
We had the same problem when updating to 4.4.9 on RHEL 8.4
Essentially to get past the problem we installed the following repo
# /etc/yum/repos.d/ovirt-4.4-stream-advanced-virt.repo
[ovirt-centos-stream-advanced-virtualization]
name=Advanced Virtualization CentOS Stream testing packages for $basea
looks like they are already aware of it:
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/BDYP62MAJL2QVQZ7RHM2USZD4HXBGUA6/
Am 18.11.21 um 11:10 schrieb Yoann Laissus:
It's also working with 6.0.0. So the problem definitely appears on 6.1.0.
The latest build https://cbs.centos.org/k
Hello Richard,
running engine-setup should give you the opportunity
to update expired or expiring certificates.
If you don't want to upgrade your system you can run it with the --offline
option.
Regards,
Paul S.
From: Ric
This single cert has expired; how would I renew just this one certificate?
--
Richard Chan
___
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
It's also working with 6.0.0. So the problem definitely appears on 6.1.0.
The latest build https://cbs.centos.org/koji/taskinfo?taskID=2604860 is also
impacted.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.o
Hi,
After we upgraded to vdsm-4.40.90.4-1.el8 on our two node cluster two things
has happned:
1. First node that was upgraded now continuously logs this error:
VDSM command Get Host Statistics failed: Internal JSON-RPC error:
{'reason': "'str' object has no attribute 'decode'"}
2. During import
We have exactly the same issue. Qemu 6.1 is totally broken or incompatible with
libvirt / vdsm.
The qemu process is launched properly (no libvirt / vdsm error, and no error in
the qemu log file) but it doesn't boot at all, no spice, no network, nothing.
Downgrading to 5.2.0 (from 6.1.0) has fixe
When checking SSH keys ovirt-vmconsole-proxy-keys is having the following
errors
ovirt-vmconsole[1583190]: 2021-11-18 17:21:42,503+0800
ovirt-vmconsole-list: ERROR main:265 Error: HTTP Error 403: Forbidden
ovirt-vmconsole-proxy-keys[1583186]: ERROR Key list execution failed rc=1
My Wildfly/vmcon
Hello,
The VMs can get created from a template otherwise the blank
template is used if a particular template is used it can be thin dependent VM
the VMs disks is linked to the Templates disk and it just carries the changes
made in the VMs disk (this is quicker and uses less space if
12 matches
Mail list logo