Q: libvirtd-tls startup failure on node (v4.4.10)
by Andrei Verovski
Hi,
I have one problematic node, and identified a culprit why vdsmd service
can't start:
-- The unit libvirtd-tls.socket has entered the 'failed' state with
result 'service-start-limit-hit'.
Aug 13 15:00:45 node14.starlett.lv systemd[1]: Closed Libvirt TLS IP socket.
-- Subject: Unit libvirtd-tls.socket has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
Node was installed on clean CentOS Stream from oVirt Web (not oVirt node
disk image), and was working fine until recent problem with certificates.
Can't reinstall/reconfigure node from oVirt Web since it is marked as
non-responsive.
How to fix this?
Thanks in advance for any help.
---------------------
[root@node14 vdsm]# cat /etc/centos-release
CentOS Stream release 8
[root@node14 vdsm]# rpm -qa | grep vdsm
vdsm-api-4.40.100.2-1.el8.noarch
vdsm-hook-openstacknet-4.40.100.2-1.el8.noarch
vdsm-client-4.40.100.2-1.el8.noarch
vdsm-network-4.40.100.2-1.el8.x86_64
vdsm-hook-vhostmd-4.40.100.2-1.el8.noarch
vdsm-4.40.100.2-1.el8.x86_64
vdsm-http-4.40.100.2-1.el8.noarch
vdsm-common-4.40.100.2-1.el8.noarch
vdsm-hook-fcoe-4.40.100.2-1.el8.noarch
vdsm-python-4.40.100.2-1.el8.noarch
vdsm-jsonrpc-4.40.100.2-1.el8.noarch
vdsm-hook-ethtool-options-4.40.100.2-1.el8.noarch
vdsm-yajsonrpc-4.40.100.2-1.el8.noarch
[root@node14 vdsm]# vdsm-tool validate-config
SUCCESS: ssl configured to true. No conflicts
[root@node14 vdsm]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● libvirtd.service loaded failed failed Virtualization daemon
● libvirtd-admin.socket loaded failed failed Libvirt admin socket
● libvirtd-ro.socket loaded failed failed Libvirt local read-only socket
● libvirtd-tls.socket loaded failed failed Libvirt TLS IP socket
● libvirtd.socket loaded failed failed Libvirt local socket
1 year, 8 months
RHV/oVirt and Ansible Tower/awx
by Colin Coe
Hey all
We've recently moved from RHV v4.3 to RHV v4.4SP1 (ovirt v4.5) and I'm
wanting to rebuild one of our application "clusters" (not HA, simply a
group of related nodes that run the application stack)
Ansible Tower is v3.8.5 and is running on RHEL7.
To further complicate matters, we've just gone from Arcserve UDP to Veeam
and Veeam for RHV.
As I need to ensure the new VMs are built with COW disks with backup
"incremental" enabled. After a lot of mucking about I find I have to fully
qualify the Ansible module names (i.e. ovirt_diskl becomes
ovirt.ovirt.ovirt_disk) but this has uncovered the next problem.
The workflow on Ansible Tower server is failing with "ovirtsdk4 version
4.4.0 or higher is required for this module".
So how can I wedge the v4.4 ovirt SDK onto this RHEL7 Ansible Tower node?
Thanks
1 year, 8 months
Nested Virtualization, please, help-me
by Jorge Visentini
Hi folks.
So... I read the documentation in many sites and this forum too, buuut the
nested feature do not worked yet.
*My host oVirt so far:*
cat /sys/module/kvm_intel/parameters/nested
1
Kernel parameters edited by Engine on *Edit Host -> Kernel*.
Reinstall the host and reboot.
*cat /proc/cmdline*
BOOT_IMAGE=(hd0,msdos1)//ovirt-node-ng-4.4.10.2-0.20220303.0+1/vmlinuz-4.18.0-365.el8.x86_64
crashkernel=auto resume=/dev/mapper/onn-swap
rd.lvm.lv=onn/ovirt-node-ng-4.4.10.2-0.20220303.0+1
rd.lvm.lv=onn/swap rhgb quiet
root=/dev/onn/ovirt-node-ng-4.4.10.2-0.20220303.0+1
boot=UUID=07e688ed-8d46-4932-b070-378c75ba1921 rootflags=discard
img.bootid=ovirt-node-ng-4.4.10.2-0.20220303.0+1 kvm-intel.nested=1
*On VM guest:*
Host set to "Specific Host" and "Pass-Through Host CPU"
vmx is ok
*root@kceve01:~# kvm-ok*
INFO: /dev/kvm exists
KVM acceleration can be used
*Result:*
I am trying to virtualize the EVE-NG. I can start the guest of the EVE-NG,
but I don't know why I can't access it. It's like blocking any package...
I don't know yet if it is a virtualization problem or network problem...
If you have other tips for me, I glad, very glad.
All the best!
--
Att,
Jorge Visentini
+55 55 98432-9868
1 year, 8 months
VM have illegal disk
by calvineadiwinata＠gmail.com
VM have illegal disk how to solve it
can't delete the Old snapshot
1 year, 8 months
Re: Problem with engine deployment
by Facundo Badaracco
Dear david.
U where right. The reinstall ansible collection solved all the problems. I
have deployed the engine vm without any issues.
Many thanks. Hope this help someone in the future.
El lun., 8 de agosto de 2022 02:44, Yedidyah Bar David <didi(a)redhat.com>
escribió:
> On Thu, Aug 4, 2022 at 6:05 PM Facundo Badaracco <varekoarfa(a)gmail.com>
> wrote:
> >
> > awesome david, im really thankful.
> >
> > [root@vs05 ~]# rpm -q rpm -q ovirt-ansible-collection
> > rpm-4.14.3-23.el8.x86_64
> > ovirt-ansible-collection-2.1.0-1.el8.noarch
> > [root@vs05 ~]# rpm -V ovirt-ansible-collection
> > S.5....T.
> /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults/main.yml
> > S.5....T.
> /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml
>
> Whoops! These files are changed/corrupted. That's the '5' there.
> Please check them.
> If you changed them manually for some reason, it might be enough to
> 'dnf reinstall ovirt-ansible-collection'. Otherwise, I'd suspect some
> bigger issue/corruption/whatever and check more carefully. If you are
> certain that the hardware is fine, and can't spot a specific issue
> leading to this, you might want to reinstall the OS.
>
> >
> > i have attached journal and messages...
>
> I didn't check them.
>
> >
> >
> > its a clean installation. i can reinstall everything if needed, even the
> SO.
>
> See above. I'd personally not reinstall the OS without first checking
> what caused this corruption - if it's a hardware issue, better handle
> it before continuing, especially if this installation is eventually
> intended for production work.
>
> Good luck and best regards,
>
> >
> >
> > El jue, 4 ago 2022 a la(s) 11:23, Yedidyah Bar David (didi(a)redhat.com)
> escribió:
> >>
> >> On Tue, Aug 2, 2022 at 3:51 PM Facundo Badaracco <varekoarfa(a)gmail.com>
> wrote:
> >>>
> >>> hi everyone, thanks for ur help.
> >>>
> >>> i tried what itforums suggested, but nothing worked.
> >>> cleaned the log, make a new run, i have found what u say david,
> "otopi_net_host" but i cant find something that helps me to fix it. i have
> attached the logs if u can help with this, will be greatly appreciated.
> >>
> >>
> >> In your ovirt-hosted-engine-setup-20220802093048-j34sz6.log.txt, there
> is this error:
> >>
> >> 2022-08-02 09:31:17,677-0300 DEBUG otopi.context
> context._executeMethod:145 method exception
> >> Traceback (most recent call last):
> >> File
> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-common/network/bridge.py",
> line 156, in _customization
> >> 'otopi_host_net'
> >> KeyError: 'otopi_host_net'
> >>
> >> And indeed, you can't find 'otopi_host_net' in
> ovirt-hosted-engine-setup-ansible-get_network_interfaces-20220802093113-agfg7e.log.txt.
> In fact, the last tasks there are 'Collect Team devices', then 'Filter team
> devices', then 'Fail if only team devices are available', and that's it -
> which is very weird, as these are in filter_team_devices.yml, which is
> imported in the middle of 001_validate_network_interfaces.yml - right after
> that, it imports filter_unsupported_vlan_devices.yml, but nothing from
> there is in the log. The next task you should have seen is 'Search VLAN
> devices', as I can see in my own log (for example).
> >>
> >> Please check:
> >>
> >> - rpm -q rpm -q ovirt-ansible-collection
> >> - rpm -V ovirt-ansible-collection
> >> - Perhaps some more logs, such as /var/log/messages, journalctl, etc.,
> that might include relevant errors from ansible. Weird.
> >>
> >>
> >>>
> >>>
> >>> if u run the deploy from cockpit, no logs are created but if i do it
> from cli, the logs are created.
> >>
> >>
> >> The cockpit deployment is deprecated. Not sure we ever announced this
> officially for oVirt.
> >>
> >> We did remove the cockpit-based installation guide from the
> documentation section on the website.
> >>
> >> It had too many problems and quite little use.
> >>
> >> So please use the CLI. Thanks.
> >>
> >> Best regards,
> >>
> >>>
> >>>
> >>>
> >>> El mar, 2 ago 2022 a la(s) 02:49, <itforums51(a)gmail.com> escribió:
> >>>>
> >>>> Hi, your issue is probably related to this
> https://www.mail-archive.com/users@ovirt.org/msg70657.html ....
> >>>>
> >>>> I also have 3x servers (using bond for storage network) and was able
> to successfully deploy the engine, but using the workaround suggested by
> 'Dax Kelson's thread above' and also later by editing a vars file on an
> ansible role: https://github.com/oVirt/ovirt-engine/issues/520
> >>>>
> >>>> I'd say give it a try and let us know the outcome.
> >>>> _______________________________________________
> >>>> Users mailing list -- users(a)ovirt.org
> >>>> To unsubscribe send an email to users-leave(a)ovirt.org
> >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >>>> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> >>>> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/647W6ROQFCD...
> >>>
> >>> _______________________________________________
> >>> Users mailing list -- users(a)ovirt.org
> >>> To unsubscribe send an email to users-leave(a)ovirt.org
> >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >>> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> >>> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/QD65NZ5TFLZ...
> >>
> >>
> >>
> >> --
> >> Didi
>
>
>
> --
> Didi
>
>
1 year, 8 months
struggling with 4.5.1 install
by Chris Smith
Hello,
Here's the general gist of what I've done so far:
graphical install from el8 and el9 iso, using as few modifications as
possible with dhcp networking.
3.6TB of disk space for ovirt install dest.
system comes up, dashboard is online, i try to deploy hosted engine, no
dice.
[image: image.png]
it's similar to this:
https://bugzilla.redhat.com/show_bug.cgi?id=1946095
ok, so i go for cli install
i manually install ovirt-engine-appliance and that seems to go ok
i kick off ovirt-hosted-engine-setup and follow the prompts
i watch the logs and such and seems to be ok
i have to make entry in /etc/hosts to have new hostname for not yet built
hosted engine VM to resolve to IP address ( I don't have "real" DNS at the
moment)
that succeeds but then new engine VM is spun up in new IP subnet
192.168.222.0/24 that is different from primary 192.168.1.0/24 not sure why.
i am at a point where i can't get a GUI to the hosted engine IP because
it's only available to the internal adapter on the node.
i feel like the installers in the el8 and el9 iso's is just completely
b0rked.
what am I doing wrong?
oh, and where is everyone at in the IRC chat room?
thanks,
Chris
1 year, 8 months
No "Virtualization" tab on Node cockpit
by giuliano.david＠nvgroup.it
Hi. I'm new to oVirt.
Trying to install the first node with hosted engine on it.
The node bare install process from the iso image (ovirt-node-ng-installer-4.5.1-2022062306.el9.iso) is fine on a Fujitsu server.
Accessing via browser the node cockpit at port 9090, on the left panel the entry "Virtualization" is missing (installing Node version 4.4.6 it was present and working), so I can't launch the hosted engine setup via UI.
Trying to deploy via command line ( $ hosted-engine --deploy ), the installation process stops with the error:
[ ERROR ] {'changed': True, 'stdout': '', 'stderr': '', 'rc': 1, 'cmd': "[ -r /etc/sysconfig/libvirtd ] && sed -i '/## beginning of configuration section by vdsm-4.[0-9]\\+.[0-9]\\+/,/## end of configuration section by vdsm-4.[0-9]\\+.[0-9]\\+/d' /etc/sysconfig/libvirtd", 'start': '2022-08-04 18:24:31.817314', 'end': '2022-08-04 18:24:31.819845', 'delta': '0:00:00.002531', 'failed': True, 'msg': 'non-zero return code', 'invocation': {'module_args': {'warn': False, '_raw_params': "[ -r /etc/sysconfig/libvirtd ] && sed -i '/## beginning of configuration section by vdsm-4.[0-9]\\+.[0-9]\\+/,/## end of configuration section by vdsm-4.[0-9]\\+.[0-9]\\+/d' /etc/sysconfig/libvirtd", '_uses_shell': True, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': [], '_ansible_no_log': False, 'item': '/etc/sysconfig/libvirtd', 'ansible_loop_var': 'item', '_ansible_
item_label': '/etc/sysconfig/libvirtd'}
I can't really understand what's going on ...
Can anyone please point me in the right direction to fix that? Is it a bug?
Thanks!!!
g
1 year, 8 months
how to use ovirt-engine on a new Architecture
by zhangwenlong＠loongson.cn
Hello, I am using ovirt-engine-4.4.10.7 on a new Architecture(LoongArch64), but an error is reported during use, the error message is:
2022-08-04 12:03:30,762-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-72) [4fad3531] EVENT_ID: CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION(156), Host node210 moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all,
which CPUs are supported by ovirt-engine-4.4.10.7? how can i get the support list of CPUs, If i want to use ovirt-engine-4.4.10.7 on a new Architecture, what should i do, thank you
the CPU information about LoongArch just like:
system type : generic-loongson-machine
processor : 0
package : 0
core : 0
cpu family : Loongson-64bit
model name : Loongson-3A5000LL
CPU Revision : 0x11
FPU Revision : 0x00
CPU MHz : 2000.00
BogoMIPS : 4000.00
TLB entries : 2112
Address sizes : 48 bits physical, 48 bits virtual
isa : loongarch32 loongarch64
features : cpucfg lam ual fpu lsx lasx complex crypto lvz lbt_x86 lbt_arm lbt_mips
hardware watchpoint : yes, iwatch count: 8, dwatch count: 8
processor : 1
package : 0
core : 1
cpu family : Loongson-64bit
model name : Loongson-3A5000LL
CPU Revision : 0x11
FPU Revision : 0x00
CPU MHz : 2000.00
BogoMIPS : 4000.00
TLB entries : 2112
Address sizes : 48 bits physical, 48 bits virtual
isa : loongarch32 loongarch64
features : cpucfg lam ual fpu lsx lasx complex crypto lvz lbt_x86 lbt_arm lbt_mips
hardware watchpoint : yes, iwatch count: 8, dwatch count: 8
1 year, 8 months
Manager crash
by teemu.saarinen＠netum.fi
Hi,
I was wondering If I have HA- setup of manager + 2 hosts. If manager crashes, does 2 host crash also or do they still continue working normally?
Thanks,
Teemu S.
1 year, 8 months
Failover IP on Hetzner
by Tommaso - Shellrent
Hi to all.
we want to configure a failover ip on an Hetzner host. Anyone can be
able of make it works?
Ip failover does not include a MAC address, so it cant't work on a
bridged network. They sauggest su confure it on a routed network.
On ovirt, how can we make it work?
Regards,
Tommaso.
--
--
Shellrent - Il primo hosting italiano Security First
*Tommaso De Marchi*
/COO - Chief Operating Officer/
Shellrent Srl
Via dell'Edilizia, 19 - 36100 Vicenza
Tel. 0444321155 <tel:+390444321155>
1 year, 8 months
