[ovirt-users] Re: Enroll Host Certificate
Oh no! :) just posted here and an invalid certificate message came ___ 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: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VO2T3LWINEKN6TZJFR7IMHECFN44RWE2/
[ovirt-users] Re: Enroll Host Certificate
> On Tue, Mar 29, 2022 at 5:43 AM dlotarev--- via Users wrote: > > > Hi, > > Enroll certificate function re-enrolls certificates only hosts. If your > engine certificate is going to expire, then you need to run engine-setup to > renew engine certificate. > > Regards, > Martin Oh im assume, that anything was re-applied, a didn't see this messages anymore, but how can i check this, or i should reboot node for sure? ___ 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: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/N5QT7YOEKOO5VJBBLBJ6TSTO5LV5S4KE/
[ovirt-users] Re: Enroll Host Certificate
> On Tue, Mar 29, 2022 at 5:43 AM dlotarev--- via Users wrote: > > > Hi, > > Enroll certificate function re-enrolls certificates only hosts. If your > engine certificate is going to expire, then you need to run engine-setup to > renew engine certificate. > > Regards, > Martin Hi Martin! No, this messages for one host only: Time:2022-03-29 08:07:28.923 Message:Host ovirt-h1.local certification is about to expire at 2022-04-18. Please renew the host's certification. Severity:WARNING Host Name: ovirt-h1.local ___ 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: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4SKPONNGW7JXQAPL7Q7SQ3IVZ33VQPNW/
[ovirt-users] Re: Enroll Host Certificate
On Tue, Mar 29, 2022 at 5:43 AM dlotarev--- via Users wrote: > Hi there! I have a problem to enroll host certificate. > Hi, Enroll certificate function re-enrolls certificates only hosts. If your engine certificate is going to expire, then you need to run engine-setup to renew engine certificate. Regards, Martin > The steps that I took: > 1) Move host to maintenance mode (all VMs transferred to another host > including HE VM) > 2) Enroll certificate via web interface without errors > 3) Exit from maintenance mode (transferred all VMs back including HE VM) > 4) Restart ovirt-engine service > > But my problem that after 6 hours i get message from oVirt engine notifier > that my certificate expired soon. > I know that my oVirt installation is old (4.1.9), but what can i do with > that? Maybe i missed something. I didn't reboot the host after renewing the > certificate > > Thank you for any advice! > ___ > 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: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/RJYOYBINZYBMJMIZMWKP5PKMIYBWT6WL/ > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. ___ 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: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/E7PHLH3452ZMQHJU5FSZ5ZAEZL5RVHA5/
[ovirt-users] Re: No bootable device
El 2022-03-28 13:12, Nir Soffer escribió:
On Mon, Mar 28, 2022 at 11:01 AM wrote:
Hi Nir,
El 2022-03-27 10:23, Nir Soffer escribió:
> On Wed, Mar 23, 2022 at 3:09 PM wrote:
>> We're running oVirt 4.4.8.6. We have uploaded a qcow2 image
>> (metasploit
>> v.3, FWIW)
>
> Is it Metasploitable3-0.1.4.ova from the github releases page?
> https://github.com/brimstone/metasploitable3/releases
>
Actually, the disk has been shared with us by one of our professors.
It
has been provided in qcow2, vmdk and raw formats, still the result was
the same. I don't actually know which exact version is it, I just know
the version is "3".
> If not, can you share the image? It will help if we can reproduce this
> problem
> locally with the same image you are using.
I will provide the link off-list because it belongs to the professor.
>
>> using the GUI (Storage -> Disks -> Upload -> Start). The
>> image is in qcow2 format.
>
> Did you convert the vmdk file from the ova to qcow2?
Yes, I also tried these steps with the same result.
>
>> No options on the right side were checked. The
>> upload went smoothly, so we now tried to attach the disk to a VM.
>>
>> To do that, we opened the VM -> Disks -> Attach and selected the disk.
>> As interface, VirtIO-iSCSI was chosen, and the disk was marked as OS,
>> so
>> the "bootable" checkbox was selected.
>>
>> The VM was later powered on, but when accessing the console the
>> message
>> "No bootable device." appears. We're pretty sure this is a bootable
>> image, because it was tested on other virtualization infrastructure
>> and
>> it boots well. We also tried to upload the image in RAW format but the
>> result is the same.
>>
>> What are we missing here? Is anything else needed to do so the disk is
>> bootable?
>
> It sounds like you converted an image from another virtualization
> system (virtualbox)
> to qcow2 format, which may not be good enough to use the virtual
> machine.
>
> oVirt supports importing OVA, but based on the UI, it supports only OVA
> created
> by oVirt.
>
> You can try virt-v2v - this is an example command, you need
> to fill in the {} parts:
>
> virt-v2v \
> -i ova {path-to-ova-file} \
> -o rhv-upload \
> -oc https://{engine-address}/ovirt-engine/api \
> -op {engine-password-file} \
> -on {vm-name} \
> -os {storrage-domain-name} \
> -of qcow2 \
> -oo rhv-cafile={engine-ca-file} \
> -oo rhv-cluster={cluster-name}
>
> I tried to import the Metasploitable3-0.1.4.ova, and virt-v2 fails
> with this error:
>
> virt-v2v: error: inspection could not detect the source guest (or
> physical machine).
>
> attached virt-v2v log.
>
Actually, the professor also provided the OVA from which he extracted
the disk files and the import process in oVirt worked with no issues.
I
can now boot the VM, not sure what difference made the OVA but now it
works.
Great that you solved this issue.
For the benefit of the community, can you explain how you imported the
OVA?
I uploaded the OVA to one of the hosts. Then in the GUI, went to Compute
> Virtual Machines and chose the '...' icon on the right, and clicked on 'Import'. As the source, I chose "Virtual Appliance (OVA)" and wrote down the path of the OVA I uploaded before. Then I just dragged the VM to the right and clicked ok, the import process went perfectly.
Thanks.
Regards.
___
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:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RJC7WG2QXOTOYXPB4Q6Q747TJE62A6LX/
[ovirt-users] Re: Wait for the engine to come up on the target vm
On Tue, Mar 29, 2022 at 12:21 PM Vladimir Belov wrote:
>
>
> I'm trying to deploy oVirt from a self-hosted engine, but at the last step I
> get an engine startup error.
>
> [ INFO ] TASK [Wait for the engine to come up on the target VM]
> [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
> "cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.181846",
> "end": "2022-03-28 15:41:28.853150", "rc": 0, "start": "2022-03-28
> 15:41:28.671304", "stderr": "", "stderr_lines": [], "stdout": "{\"1\":
> {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
> Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537
> (Mon Mar 28 15:41:20
> 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\":
> {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\":
> \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false,
> \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\":
> 5537, \"host-ts\": 5537}, \"global_maintenance\": false}", "stdout_lines":
> ["{\"1\": {\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
> \"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
> Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537
> (Mon Mar 28 15:41:20
> 2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
> \"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\":
> {\"reason\": \"failed liveliness check\", \"health\": \"bad\", \"vm\":
> \"up\", \"detail\": \"Up\"}, \"score\": 3400, \"stopped\": false,
> \"maintenance\": false, \"crc32\": \"4d2eeaea\", \"local_conf_timestamp\":
> 5537, \"host-ts\": 5537}, \"global_maintenance\": false}"]}
>
> Аfter the installation is completed, the condition of the engine is as
> follows:
> Engine status: {"reason": "failed liveliness check", "health": "bad", "vm":
> "up", "detail": "Up"}
>
> After reading the vdsm.logs, I found that qemu-guest-agent failed to connect
> to the engine for some reason.
>
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5400, in
> qemuGuestAgentShutdown
> self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)
> File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in
> f
> ret = attr(*args, **kwargs)
> File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
> line 130, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92,
> in wrapper
> return func(inst, *args, **kwargs)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in
> shutdownFlags
> if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed',
> dom=self)
> libvirtError: Guest agent is not responding: QEMU guest agent is not connected
IIRC this shouldn't fail anything, other than functionality that
relies on the agent (which should be non-critical).
>
> During the installation phase, qemu-guest-agent on the guest VM is running.
>
> Setting a temporary password (hosted-engine --add-console-password
> --password) and connecting via VNC also failed.
>
> Using "hosted-engine --console" also failed to connect
>
> The engine VM is running on this host
> Connected to HostedEngine domain
> Escaping character: ^]
> error: internal error: character device not found
>
> The network settings are configured using static addressing, without DHCP.
> It seems to me that this is due to the fact that the engine receives an IP
> address that does not match the entry in /etc/hosts, but I do not know how to
> fix it.
"Receives"? Where from? If you choose static, all should be configured
using the values you provided.
Anyway, this should not prevent logging in using the console.
> Any help is welcome, I will provide the necessary logs. Thanks
Do you use qemu-kvm 6.1? If so, please try 6.0 or 6.2. Otherwise,
please check more logs on the host, including:
/var/log/ovirt-hosted-engine*/*
/var/log/libvirt
/var/log/messages
Good luck and best regards,
--
Didi
___
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:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YUIYKXVYXNL6NVF2KHAW3UIRTKXQ6OAX/
[ovirt-users] Wait for the engine to come up on the target vm
When I try to deploy the engine using self-hosted-engine technology, I get an
error at the end of the installation.
[ INFO ] TASK [Wait for the engine to come up on the target VM]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
"cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.181846",
"end": "2022-03-28 15:41:28.853150", "rc": 0, "start": "2022-03-28
15:41:28.671304", "stderr": "", "stderr_lines": [], "stdout": "{\"1\":
{\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon
Mar 28 15:41:20
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
\"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\":
\"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\":
\"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false,
\"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537},
\"global_maintenance\": false}", "stdout_lines": ["{\"1\": {\
"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon
Mar 28 15:41:20
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
\"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\":
\"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\":
\"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false,
\"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537},
\"global_maintenance\": false}"]}
After installation, when checking the condition of the engine, it issues:
Engine status: {"reason": "failed liveliness check", "health": "bad", "vm":
"up", "detail": "Up"}
After looking at the vdsm.logs, I found that qemu-guest-agent for some reason
does not connect to the guest VM
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5400, in
qemuGuestAgentShutdown
self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)
File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f
ret = attr(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
line 130, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in
wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in
shutdownFlags
if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed',
dom=self)
libvirtError: Guest agent is not responding: QEMU guest agent is not connected
During the deployment phase of the engine, qemu-guest-agent was up and running.
When configuring network settings, static addressing is used.
It seems to me that this is due to the fact that the engine receives an IP
address that does not match the entry in /etc/hosts, but I do not know how to
fix it. Any help is welcome, I will provide the necessary logs. Thanks
___
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:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WQSYZONY7TMX6A7QWXV67BMTCFIMLIUR/
[ovirt-users] Wait for the engine to come up on the target vm
I'm trying to deploy oVirt from a self-hosted engine, but at the last step I
get an engine startup error.
[ INFO ] TASK [Wait for the engine to come up on the target VM]
[ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 120, "changed": true,
"cmd": ["hosted-engine", "--vm-status", "--json"], "delta": "0:00:00.181846",
"end": "2022-03-28 15:41:28.853150", "rc": 0, "start": "2022-03-28
15:41:28.671304", "stderr": "", "stderr_lines": [], "stdout": "{\"1\":
{\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon
Mar 28 15:41:20
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
\"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\":
\"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\":
\"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false,
\"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537},
\"global_maintenance\": false}", "stdout_lines": ["{\"1\":
{\"conf_on_shared_storage\": true, \"live-data\": true, \"extra\":
\"metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=5537 (Mon
Mar 28 15:41:20 2022)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=5537 (Mon
Mar 28 15:41:20
2022)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineStarting\\nstopped=False\\n\",
\"hostname\": \"v2.test.ru\", \"host-id\": 1, \"engine-status\": {\"reason\":
\"failed liveliness check\", \"health\": \"bad\", \"vm\": \"up\", \"detail\":
\"Up\"}, \"score\": 3400, \"stopped\": false, \"maintenance\": false,
\"crc32\": \"4d2eeaea\", \"local_conf_timestamp\": 5537, \"host-ts\": 5537},
\"global_maintenance\": false}"]}
Аfter the installation is completed, the condition of the engine is as follows:
Engine status: {"reason": "failed liveliness check", "health": "bad", "vm":
"up", "detail": "Up"}
After reading the vdsm.logs, I found that qemu-guest-agent failed to connect to
the engine for some reason.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5400, in
qemuGuestAgentShutdown
self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)
File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f
ret = attr(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
line 130, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in
wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in
shutdownFlags
if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed',
dom=self)
libvirtError: Guest agent is not responding: QEMU guest agent is not connected
During the installation phase, qemu-guest-agent on the guest VM is running.
Setting a temporary password (hosted-engine --add-console-password --password)
and connecting via VNC also failed.
Using "hosted-engine --console" also failed to connect
The engine VM is running on this host
Connected to HostedEngine domain
Escaping character: ^]
error: internal error: character device not found
The network settings are configured using static addressing, without DHCP.
It seems to me that this is due to the fact that the engine receives an IP
address that does not match the entry in /etc/hosts, but I do not know how to
fix it. Any help is welcome, I will provide the necessary logs. Thanks
___
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:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5X2N6PE2OWTL3MBLZWCSEWAOXWY6Q3IC/
[ovirt-users] Gluster storage and TRIM VDO
Hello everyone. I have a Gluster distributed replication cluster deployed. The cluster - store for ovirt. For bricks - VDO over a raw disk. When discarding via 'fstrim -av' the storage hangs for a few seconds and the connection is lost. Does anyone know the best practices for using TRIM with VDO in the context of ovirt? ovirt - v4.4.10 gluster - v8.6 ___ 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: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UCTN2ZIG3EDVUU5COPXLMOH2T6WHTPBB/
