- Users - oVirt List Archives

Configuring LUNS for self-hosted engine install
by Virden, Gerald 08 Oct '21

08 Oct '21

Hi, I have a host with two 16TB LUNS that I want to deploy a self-hosted engine on. I have so far been unsuccessful; the install either fails or hangs and Oracle is saying it is due to storage. I can see both LUNS with multipath -ll. Does anyone know of step by step instructions on what to do to configure the LUNS so the engine will see them and set up the storage domain? Jerry

1 0

[ANN] oVirt 4.4.9 Second Release Candidate is now available for testing
by Sandro Bonazzola 08 Oct '21

08 Oct '21

oVirt 4.4.9 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.9 Second Release Candidate for testing, as of October 8th, 2021. This update is the ninth in a series of stabilization updates to the 4.4 series. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.9 release highlights: http://www.ovirt.org/release/4.4.9/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.9/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: fresh hyperconverged Gluster setup failed in ovirt 4.4.8
by Eddie Garcia 07 Oct '21

07 Oct '21

I have been having this issue as well with no solution working but I came across something interesting. In selinux-policy 3.14.3-77 they removed the glusterd selinux module. https://centos.pkgs.org/8-stream/centos-baseos-x86_64/selinux-policy-3.14.3… so that policy doesn exist anymore for ansible to apply. I plan on testing installing an older version into an ovirt node box to test which defaults as of 4.4.8 to selinux-policy version 3.14.3-79.el8. A clean install of CentOS 8 using latest iso has version 3.14.3-67.el8_4.2 and I can verify that manually setting policy with command 'semanage fcontext -a -t glusterd_brick_t "/gluster_bricks(/.*)?"' is completed successfully.

2 1

Re: qemu-guest-agent not reporting IP address on boot?
by Tomáš Golembiovský 07 Oct '21

07 Oct '21

On Wed, Oct 06, 2021 at 10:48:51PM +0000, Schreuders, Cliffe wrote: > Following up on this, for the benefit of anyone else who faces the same problem, I'm happy to say we have VMs reporting IP addresses with latest Kali now. > > I've not managed to fix the fact that it is taking Kali a lot longer to report IP address (compared to the last version that shipped with ovirt-guest-agent, which reports IP addresses almost instantly on boot), but I extended the time out to give a lot more time for the VM to get an IP address (it is taking around 5 minutes), Good to hear that it is working now. Which version of oVirt are you using? There were improvements for the delay of initial guest information in oVirt 4.4 and the information should be available as soon as the VM comes up. Tomas > and also needed to add exception handling to the Vagrant oVirt plugin, around accessing the nics_service, which was throwing an oVirt error after a few minutes "Can't send request: Failed sending data to the peer", after allowing those errors to be ignored during the wait for an IP to be reported, it does eventually report the IP address, and other guest information. VMs are now reliably building again (albeit taking a little longer). > > Thanks. > > Cheers, > Cliffe. > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email -- Tomáš Golembiovský <tgolembi(a)redhat.com>

1 0

Self Hosted Engine disk increase
by Paulo Silva 07 Oct '21

07 Oct '21

Hi, Is there any official procedure to increase the disk size of a self-hosted engine? Regards

2 4

Re: qemu-guest-agent not reporting IP address on boot?
by Tomáš Golembiovský 07 Oct '21

07 Oct '21

On Mon, Oct 04, 2021 at 01:03:10PM +0000, Schreuders, Cliffe wrote: > Thank you. It does look like that bug could be related. Is the problem just with the IP addresses? Do you see other guest information or are those missing too? Tomas > > I had an earlier version of the VM template which continued to work correctly, and an updated version (via apt-get dist-upgrade) that did not report IP addresses correctly. > > I suspected that it might be related to the new ovirt/qemu user agent, so I hold/pinned "ovirt-guest-agent" on the older template before re-running the software updates. > > This worked to create an updated Kali VM that reports it's IP address (albeit more-or-less stuck with whatever dependencies the last ovirt-guest-agent has) so it seems this is indeed an issue with qemu-guest-agent vs ovirt-guest-agent. > > Cheers, > Cliffe. > ________________________________ > From: Arik Hadas <ahadas(a)redhat.com> > Sent: 03 October 2021 12:04 > To: Schreuders, Cliffe <C.Schreuders(a)leedsbeckett.ac.uk> > Cc: users <users(a)ovirt.org>; Tomas Golembiovsky <tgolembi(a)redhat.com> > Subject: Re: [ovirt-users] qemu-guest-agent not reporting IP address on boot? > > > Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. > > > On Fri, Oct 1, 2021 at 5:51 PM <c.schreuders(a)leedsbeckett.ac.uk<mailto:c.schreuders@leedsbeckett.ac.uk>> wrote: > Hi folks, > > Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and instead package qemu-guest-agent. However, since this upgrade VMs based on Kali no longer report their IP address to oVirt (and therefore timeout during provisioning). If I interact with the VM console, the VM does have an IP address, and the agent is running, yet oVirt reports N/A IP address. I've tried restarting the agent, but that does not help. If I load the console and use the VM it seems to increase the chances the IP address will eventually makes it's way to oVirt, although I can't seem to reproduce an update, or get it to provide the IP address on boot so that provisioning works reliably. > > Any suggestions would be really appreciated. > > Might be the same as/related to https://bugzilla.redhat.com/show_bug.cgi?id=1981946<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.…> which is still being investigated > > > Thank you. > > Cheers, > Cliffe. > _______________________________________________ > Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> > To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> > Privacy Statement: https://www.ovirt.org/privacy-policy.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFINLLXPBRKYH…<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email -- Tomáš Golembiovský <tgolembi(a)redhat.com>

2 2

adding new node to host engine is getting failed - engine version latest 4.4.8
by dhanaraj.ramesh＠yahoo.com 06 Oct '21

06 Oct '21

Hi Team when I try to add a new node to the cluster, the installation getting failed with below error Host beclovkvma04.bec.lab installation failed. Task Run PKI enroll request for vdsm and QEMU failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20211006191147-beclovkvma04.bec.lab-e9351609-1bf4-4a8e-adcc-af459f8b25a0.log. log shows as below oR4K1dI9NIaH1jSEtBnIC0Qycxz1i9", "/knKXJLDKeuRsY2holB/BYbMECe4dpseRO+SJPnoqLbK0S6lEf/F6rIcowcg4KbS", "TYjL8g8P6/mM", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "...............+++++", "........................................+++++", "writing new private key to '/tmp/ansible.wjc0hdouvdsm'", "-----" ], "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.wjc0hdouvdsm", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "vdsm", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "vdsm", "pending_file" : "keys/vdsmkey.pending.pem", "req_dir" : "requests" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item" } }, { "diff" : [ ], "dest" : "/etc/pki/ovirt-engine/requests-qemu/beclovkvma04.bec.lab.req", "src" : "/var/lib/ovirt-engine/.ansible/tmp/ansible-tmp-1633527734.1252306-38395-243978746272048/source", "md5sum" : "76137d8fb7063ee3ecce0a1637e991e9", "checksum" : "37c73f4ac229f1837a9b5f4a84162426547de18e", "changed" : true, "cmd" : [ "/usr/share/ovirt-engine/bin/pki-enroll-request.sh", "--name=beclovkvma04.bec.lab", "--subject=/O=bec.lab /CN=beclovkvma04.bec.lab", "--san=DNS:beclovkvma04.bec.lab", "--days=398", "--timeout=30", "--ca-file=ca", "--cert-dir=certs" , "--req-dir=requests" ], "stdout" : "", "stderr" : "Using configuration from openssl.conf\nunable to load number from serial.txt\nerror while loading serial number\n139654062544704:error: 0D066096:asn1 encoding routines:a2i_ASN1_INTEGER:short line:crypto/asn1/f_int.c:140:\nCannot sign certificate", "rc" : 1, "start" : "2021-10-06 19:12:14.648053", "end" : "2021-10-06 19:12:14.673708", "delta" : "0:00:00.025655", "changed" : true, "failed" : true, "invocation" : { "module_args" : { "_raw_params" : "\"/usr/share/ovirt-engine/bin/pki-enroll-request.sh\"\n\"--name=beclovkvma04.bec.lab\"\n\"--subject=/O=bec.bsn lab.broadcom.net/CN=beclovkvma04.bec.lab\"\n\"--san=DNS:beclovkvma04.bec.bsnlab.broadcom.net\"\n\"--days=398\"\n\"--timeout=30\"\n\"--ca-file =ca\"\n\"--cert-dir=certs\"\n\"--req-dir=requests\"\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } },

1 0

adding new node to host engine is getting failed - engine version latest 4.4.8
by dhanaraj.ramesh＠yahoo.com 06 Oct '21

06 Oct '21

Hi Team when I try to add a new node to the cluster, the installation getting failed with below error Host beclovkvma04.bec.lab installation failed. Task Run PKI enroll request for vdsm and QEMU failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20211006191147-beclovkvma04.bec.lab-e9351609-1bf4-4a8e-adcc-af459f8b25a0.log. log shows as below oR4K1dI9NIaH1jSEtBnIC0Qycxz1i9", "/knKXJLDKeuRsY2holB/BYbMECe4dpseRO+SJPnoqLbK0S6lEf/F6rIcowcg4KbS", "TYjL8g8P6/mM", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "...............+++++", "........................................+++++", "writing new private key to '/tmp/ansible.wjc0hdouvdsm'", "-----" ], "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.wjc0hdouvdsm", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "vdsm", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "vdsm", "pending_file" : "keys/vdsmkey.pending.pem", "req_dir" : "requests" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item" } }, { "diff" : [ ], "dest" : "/etc/pki/ovirt-engine/requests-qemu/beclovkvma04.bec.lab.req", "src" : "/var/lib/ovirt-engine/.ansible/tmp/ansible-tmp-1633527734.1252306-38395-243978746272048/source", "md5sum" : "76137d8fb7063ee3ecce0a1637e991e9", "checksum" : "37c73f4ac229f1837a9b5f4a84162426547de18e", "changed" : true, "cmd" : [ "/usr/share/ovirt-engine/bin/pki-enroll-request.sh", "--name=beclovkvma04.bec.lab", "--subject=/O=bec.lab /CN=beclovkvma04.bec.lab", "--san=DNS:beclovkvma04.bec.lab", "--days=398", "--timeout=30", "--ca-file=ca", "--cert-dir=certs" , "--req-dir=requests" ], "stdout" : "", "stderr" : "Using configuration from openssl.conf\nunable to load number from serial.txt\nerror while loading serial number\n139654062544704:error: 0D066096:asn1 encoding routines:a2i_ASN1_INTEGER:short line:crypto/asn1/f_int.c:140:\nCannot sign certificate", "rc" : 1, "start" : "2021-10-06 19:12:14.648053", "end" : "2021-10-06 19:12:14.673708", "delta" : "0:00:00.025655", "changed" : true, "failed" : true, "invocation" : { "module_args" : { "_raw_params" : "\"/usr/share/ovirt-engine/bin/pki-enroll-request.sh\"\n\"--name=beclovkvma04.bec.lab\"\n\"--subject=/O=bec.bsn lab.broadcom.net/CN=beclovkvma04.bec.lab\"\n\"--san=DNS:beclovkvma04.bec.bsnlab.broadcom.net\"\n\"--days=398\"\n\"--timeout=30\"\n\"--ca-file =ca\"\n\"--cert-dir=certs\"\n\"--req-dir=requests\"\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } },

1 0

Import ISCSI target as data domain, cannot see old data
by joyzhao93＠gmail.com 06 Oct '21

06 Oct '21

Hi Team, Hope you are doing well. I had a standalone Ovirt Engine with 2 hosts, one 2TB ISCSI data domain (dell equallogic). Today the Ovirt Engine machine crashed so we have to bring up a new one, setup is good and when I try to import ISCSI data domain I can see volumes/Luns, but after import, Ovirt shows the volume is empty - 2TB free (so all old data on the ISCSI volume is not presenting). However when I login to the ISCSI target machine, it shows the old data (around 400GB) is in use. Seems like the new Ovirt Engine cannot detect the old ISCSI data domain disk content. Thank you, Sincerely, SYZhao

2 1

Deploying ovirt+gluster hyperconverged with standalone engine
by J W 06 Oct '21

06 Oct '21

I'm looking for the proper steps to deploy ovirt+gluster hyperconverged with standalone engine as the scenario doesn't seem to be covered here: https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_H… I have attempted to: 1) Deploy standalone engine 2) deploy 3 nodes and ran gluster deployment, stopping before the engine deploy 3) Added hosts to standalone engine I then attempt to add the gluster volumes to the standalone engine by specifying host1:/volume as glusterfs but the volume does not successfully add. Is there another perferred method for this type of deployment?

1 0