After doing a bit more research, I was able to get the engine to boot by
issuing CTRL-ALT-DEL through remote viewer. I am uncertain as to why that
appears to fix the problem with the engine, however after such I have added
additional hosts, and reinstalled the first host that failed on the
Hi,
Since the volume is full you will not be able to do any kind of file operations
until some space is free.
Go to Storage -> Disks in ui and find a disk which you are sure is safe to
delete and you won't miss it.
Note down the disk id.
locate the disk directory under the volume mount.
cd
Good morning, i have installed a new ovirt 4.3.10 enviroment but sometimes on
the events of some hosts i read this error message:
VDSM node-1-ra command Get Host Capabilities failed: Message timeout which can
be caused by communication issues
Due to this issue hosts are in unresponsive state
On Thu, Jul 16, 2020 at 12:00 PM 崔涛的公司邮箱 wrote:
>
> Could anyone give me some explain?
It's a place (virtual disk) on shared storage where the engine keeps
information about VMs (and templates). See also e.g.:
Could anyone give me some explain?
___
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:
i attach the hosts info :
Software
OS Version:
RHEL - 7 - 8.2003.0.el7.centos
OS Description:
CentOS Linux 7 (Core)
Kernel Version:
3.10.0 - 1062.el7.x86_64
KVM Version:
2.12.0 - 44.1.el7_8.1
LIBVIRT Version:
libvirt-4.5.0-33.el7_8.1
VDSM Version:
vdsm-4.30.46-1.el7
I also have this message with the deployment of Gluster. I tried the
modifications and it doesn't seem to work. Did you succeed ?
here error :
TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for RHEL
systems.] ***
task path:
Hi,
We did compare engine backups and found some differences in the LUNs
"public"."luns" (restored db from 2020.04.09)
physical_volume_id lun_idvolume_group_id
Hi,
I have a problem with Ubuntu 20.04 VM reporting the correct FQDN to the engine.
Starting with this release, the ovirt-guest-agent is not available anymore.
Therefore, I have installed qemu-geust-agent with package defaults.
Now in the Engine, I only see the hostname under FQDN tab, instead
What do you see in the engine's logs ?
Best Regards,
Strahil Nikolov
На 16 юли 2020 г. 13:24:03 GMT+03:00, lu.alfo...@almaviva.it написа:
>i attach the hosts info :
>
>Software
>OS Version:
>RHEL - 7 - 8.2003.0.el7.centos
>OS Description:
>CentOS Linux 7 (Core)
>Kernel Version:
>3.10.0 -
Can you share your /etc/hosts.
As far as I remember there was an entry like:
127.0.1.2 hostname
So you have to comment it out.
Best Regards,
Strahil Nikolov
На 16 юли 2020 г. 16:53:36 GMT+03:00, Florian Schmid via Users
написа:
>Hi,
>
>I have a problem with Ubuntu 20.04 VM reporting the
Hi,
if its the same LUN, then why not remove and import back?
On Thu, Jul 16, 2020 at 3:21 PM Arsène Gschwind
wrote:
> Hi,
>
> We did compare engine backups and found some differences in the LUNs
>
> "public"."luns" (restored db from 2020.04.09)
>
Same issue with ovirt-node-ng-installer 4.4.1-2020071311.el8 iso
[image: gluster-fail.PNG]
On Thu, Jul 16, 2020 at 9:33 AM wrote:
> I also have this message with the deployment of Gluster. I tried the
> modifications and it doesn't seem to work. Did you succeed ?
>
> here error :
>
> TASK
Have you tried to replace 'package' with 'dnf' in
/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/main.yml (somewhere
around line 33).
Best Regards,
Strahil Nikolov
На 16 юли 2020 г. 16:30:04 GMT+03:00, dominique.desche...@gcgenicom.com написа:
>I also have this message with the
Hi Strahil,
no, the hosts file should be OK:
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
When adding an additional
All,
I applied the recent update 4.4.1 -> 4.4.1.1 to a host in a cluster and it
failed. After reboot it was hund at the emergency console. I reinstalled 4.4.1
fresh on the host. Prior to adding it back to the cluster I applied the same
update with the same result. Is this just a bad update or
Thanks.
Using a proxy is my plan.
I was asked by my security team to add some more "distance" from users to
the server running the engine and the database.
Coming to think of it, maybe deploying the DB on a standalone server is a
better approach.
On Wed, Jul 15, 2020 at 10:08 PM Michal
Dear Strahil, Dominique and Edward:
I reimaged the three hosts with
ovirt-node-ng-installer-4.4.1-2020071311.el8.iso just to be sure everything was
stock (I had upgraded from v4.4) and attempted a redeploy with all suggested
changes EXCEPT replacing "package" with "dnf" --> same failure. I
HI,
Thank you for your answers
I tried to replace the "package" with "dnf". the installation of the gluster
seems to work well but I had the similar message during the deployment of the
Hosted engine.
Here is the error
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 10, "changed":
After working through some DNS problems I was able to install oVirt 4.4.1.1 and
progress the engine deployment stops within the ansible scripts. The system
deploys the gluster domain, creates the engine, starts the engine, however it
will never fully boot and complete the deployment. Bringing
20 matches
Mail list logo
