April 2021 - Users - Ovirt List Archives

by Matthew.Stier＠fujitsu.com

Ovirt: 4.3.10 Storage: iSCSI Problem: Attempting to place storage domain into 'maintenance' in preparation for detachment and destruction, has left it hung in a 'Preparation for maintenance' state. I have three storage domain I need to put into maintenance, detach and delete. When I placed place the first, and smallest (100GB) into maintenance mode, it switched to 'Preparing for Maintenance', and has stuck there for hours. Early on, I was able to re-activate it, but I do want to remove for use somewhere else, and I want make sure I can remove it, before I try to do the same with two 11TB storage domains.

2 years, 11 months

1
0
0 / 0

Can we remove Export and ISO Domain from KVM ?.

by smuthyala＠helenoftroy.com

I need to migrate both Export and ISO Domains to newer storage. Can i remove them and recreate. Or is there a way to export and import into a newer storage. TIA

2 years, 12 months

1
0
0 / 0

ovsdb-server tlsv1 unknown ca

by ozmen62＠hotmail.com

2 years, 12 months

1
0
1 / 0

Re: Ansible ovirt.ovirt_vm nics

by Martin Perina

Hi Matthew, Could you please share with us your playbook? Which ansible version are you using? Are you using ovirt_vm module from oVirt Ansible Collection which contains newer versions than the ovirt_vm module included in Ansible 2.9? https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_... Thanks, Martin On Thu, Apr 22, 2021 at 9:28 AM Matthew.Stier(a)fujitsu.com < Matthew.Stier(a)fujitsu.com> wrote: > The ‘nics’ section of ovirt_vm is vague and with nearly no examples. > > > > My playbook is based upon > https://blogs.oracle.com/scoter/ansible-with-oracle-linux-virtualization-... > > > > I’ve made several modifications, (more default) and added a few lines, > which I believe is supposed to assign vnic profiles to the primary vnic > (nic1), based upon the definition of ‘vm_nic1_profile’ defined in an > included ‘ini’ file. (the profile defaulting to blank if it is not defined > in the ini file.) > > > > It isn’t doing its job. > > > > nics: > > - name: “nic1” > > profile_name: "{{ hostvars[item]['vm_nic1_profile'] | default('') }}” > > > > > > The playbook runs without complaint. If I run it with option ‘-vvv’ part > of the output lists the variables, but the ‘nics’ variable is an empty list > (nics[]) > > > > Any hints on what I’m doing wrong? I’ve checked the forum, but it tends > to strip leading spaces, which is bad for indent sensitive code. > _______________________________________________ > 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/MEZLXGSSRCR... > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

2 years, 12 months

2
1
0 / 0

n00b Requesting Some Advice

by matthew＠peregrineit.net

Hi All, I need some "best practice" advice. We have a Ceph Storage Cluster (Octopus moving to Pacific) which we'd like to use with our new oVirt Cluster (all on CentOS 8 boxes). What I'd like to know is what is the "best" (ie recommended / best practice) way of doing this - via iSCSI, CFS, 'raw' RBD blocks, some other way I haven't read about yet, etc? I realise 'best' is a subjective term, but what I tend to do is do 'manual' installs so that I both actually understand what is happening (ie how things fit together - I pull apart and rebuild mechanical clocks and watches for the same reason) and also so I can '"Puppet-ise" the results for future use. This means that I am *not* necessarily looking for "quick and dirty" or "quick and easy" (ie, I have no trouble using the CLI and 'vim-ing' conf files as required) but I do want a solid, "best-practice" system when I'm done. So, can some please help? And also, would you mind pointing me towards the relevant documentation for the answer(s) supplied (yes, I *always* RTFM :-) ). Thanks in advance Dulux-Oz

2 years, 12 months

6
6
0 / 0

not able to upload disks, iso - Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser.

by dhanaraj.ramesh＠yahoo.com

Hi We are unning with 4.4.3.12-1.el8 version and so far working fine, but today users complained they are unable to upload new disks and upon checking found "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser" during testing option. please help on this and if there is any temp solution is available share me the steps

2 years, 12 months

4
7
0 / 0

How to update ovirt-sdk

by Miguel Garcia

We integrate jenkins to launch vms dynamically to run smoketest from our builds but now we receive the following problem: "msg": "ovirtsdk4 version 4.3.0 or higher is required for this module" I had installed following packages in CentOs7 ovirt-engine-sdk-java.noarch 3.6.10.0-1.el7 epel ovirt-engine-sdk-java-javadoc.noarch 3.6.10.0-1.el7 epel ovirt-engine-sdk-python.noarch 3.6.9.1-1.el7 epel I tired to use yum upgrade but did not report more recent version from ovirt-sdk. How can I upgrade/install ovirt-sdk to version 4.3?

2 years, 12 months

4
8
0 / 0

[ANN] oVirt 4.4.6 Fifth Release Candidate is now available for testing

by Lev Veyde

oVirt 4.4.6 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Fifth Release Candidate for testing, as of April 22nd, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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.3 or newer * CentOS Linux (or similar) 8.3 or newer * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * 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.6 release highlights: http://www.ovirt.org/release/4.4.6/ * 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.6/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 years, 12 months

1
0
0 / 0

host certification is about to expire

by Bill James

I get this message from ovirt: Message:Host <hostname> certification is about to expire at 2021-05-12. Please renew the host's certification. I tried putting host in maintenance mode and running "enroll certificate". Didn't help. How do I renew the certificate? I'm running* 4.3.9.4-1.el7* *Thanks.* -- This email, its contents and attachments contain information from J2 Global, Inc. and/or its affiliates which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this email in error, please notify the sender by reply email and delete the original message and any copies.

2 years, 12 months

2
4
0 / 0

Ansible ovirt.ovirt_vm nics

by Matthew.Stier＠fujitsu.com

The 'nics' section of ovirt_vm is vague and with nearly no examples. My playbook is based upon https://blogs.oracle.com/scoter/ansible-with-oracle-linux-virtualization-... I've made several modifications, (more default) and added a few lines, which I believe is supposed to assign vnic profiles to the primary vnic (nic1), based upon the definition of 'vm_nic1_profile' defined in an included 'ini' file. (the profile defaulting to blank if it is not defined in the ini file.) It isn't doing its job. nics: - name: "nic1" profile_name: "{{ hostvars[item]['vm_nic1_profile'] | default('') }}" The playbook runs without complaint. If I run it with option '-vvv' part of the output lists the variables, but the 'nics' variable is an empty list (nics[]) Any hints on what I'm doing wrong? I've checked the forum, but it tends to strip leading spaces, which is bad for indent sensitive code.

2 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users April 2021