- Users - oVirt List Archives

Hello.which environment type I choose?
by 欧文 02 Feb '21

02 Feb '21

Dear: Hello. My name is Owen. First, I appreciate you spend time to check my email. Recently I want to use oVirt to build a project. But after reading the official document, I have some questions to ask. The project is intended to set up a physical server that is used to implement virtualization, Variable quantity of thin clients for users. But I don't know which environment types I should use to deploy. The number two question is why the system environment is different between each version of o-virt？Because centos 7 is the major version. But so many versions of o-virt is not centos 7 or centos 8.can you tell me the reason. Thank you.At last, I have a question.I ever joined the IRC, but there is no response to answer my question. Could you tell me where I can take part in the community with developers who develope o-virt.Thanks

2 1

multipath and VDSM REVISION value mappings
by Gianluca Cecchi 02 Feb '21

02 Feb '21

Hello, considering that the best practice is to keep the multipath.conf file unmodified, is there a table with the mapping between the version of oVirt/RHV and the value of "VDSM REVISION" in /etc/multipath.conf, so that in case of doubts one can crosscheck (eg inherited environment where different admins were managing...)? Does this value depend only on the hypervisor installed sw version or also on the Cluster Compatibility version of the cluster the host belongs to, or on the engine version? In several oVirt/RHV environments with 4.3 / 4.4 I see several numbers for the VDSM REVISION from 2.0, to 1.9 and 1.5... Also what could be the impact of having a wrong (higher or lower) revision inside the file? Thanks, Gianluca

2 2

oVirt + Proxmox Backup Server
by Diggy Mc 02 Feb '21

02 Feb '21

Is anyone using Proxmox Backup Server to backup VMs in an oVirt environment? Is it even possible? I'm looking for a free open-source solution for my backup needs (backup VMs as well as traditional file backups). Any guidance is appreciated.

6 6

move ovirt 4.3.9 to RHEL 8
by Paul Dyer 01 Feb '21

01 Feb '21

Hi, I am laying the groupwork for upgrade ovirt to 4.4. Since the standalone ovirt mgr is now running on RHEL 7, I have installed RHEL 8 to a new VM. Unfortunately, after installing ovirt-release43, I am not able to find documentation for the dnf modules required. All the current documentation point to ovirt-release44 and dnf modules not available for ovirt 4.3/RHEL 8. I have these repos enabled... Repo ID: ansible-2-for-rhel-8-x86_64-rpms Repo ID: rhel-8-for-x86_64-appstream-rpms Repo ID: rhel-8-for-x86_64-baseos-rpms I am looking setup docs for a standalone engine of ovirt 4.3 on RHEL 8. Thanks! -- Paul Dyer, Mercury Consulting Group, RHCE 504-338-8750

4 5

Re: AFFINITY GROUPS
by LS CHENG 01 Feb '21

01 Feb '21

ok thank you Is AFFINITY GROUPS extensively used? Cheers On Sun, Jan 31, 2021 at 10:42 AM Kim Kargaard <Kim.Kargaard(a)noroff.no> wrote: > You can select multiple hosts when selecting which host the VM can run on. > > Kim > ------------------------------ > *From:* LS CHENG <lsc.oraes(a)gmail.com> > *Sent:* Sunday, January 31, 2021 9:51 AM > *To:* Strahil Nikolov <hunter86_bg(a)yahoo.com> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: AFFINITY GROUPS > > Hi > > Yes, that can be trick as well. I am using affinity rules because I am > trying to extend to more combinations. For examples 4 hosts and a vm can > run in 2 hosts only etc. > > Thanks > > On Sun, Jan 31, 2021 at 9:14 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> > wrote: > > Why don't you go to VM settings and define that vm01 can run only on > host_x? > If the host is down, it won't start on host_y. > > Best Regards, > Strahil Nikolov > Sent from Yahoo Mail on Android > <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_And…> > > On Sat, Jan 30, 2021 at 23:09, LS CHENG > <lsc.oraes(a)gmail.com> wrote: > Hi > > I would like to know how AFFINITY GROUPS works. > > I have 2 VM in 2 hosts, each VM runs in a host. Let's call > > HOST_X where vm01 runs > HOST_Y where vm02 runs > > I have set up an affinity group where it says vm01 relates to HOST_X, vm02 > relates to HOST_Y. VM affinity rule is set to negative and HOST affinity > rule set to positive. I need both vm01 and vm02 to run in their respective > physical host. > > I have a problem, when vm01 is stopped and HOST_Y is rebooted vm02 starts > in HOST_X, how can I avoid that? > > Thank you > > Luis Sanchez > > > _______________________________________________ > 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/C74WDKK2SSFA3… > >

1 0

Custom Fence Agent
by Robert Tongue 01 Feb '21

01 Feb '21

Greetings everyone, I am having another problem that I was hoping to get some assistance with. I have created my own custom fence agent for some tasmota-flashed wifi smart plugs, that can control plug power input to ovirt nodes. This works great; however I am running into a problem getting it added to ovirt as a power manager. I got the custom fence agent added with engine-config -s, and it shows up in the webui to select as a power management agent, then I put in the details for the plug, IP address, login, password, and press the "test" button, which passes, and shows the status as power=on. Once I save the settings, however, it is logged in the engine.log file that fencing will fail, because there is no node available to proxy the operation. When I go back into the power management settings, and press "test" again, then I get the error: "Test failed: Failed to run fence status-check on host 'ovirt1'. No other host was available to serve as proxy for the operation." I have the agent script in /usr/sbin/ on all nodes, execute permissions set, and I can run it manually at the command line just fine, so I am really at a loss here as what to check. What am I missing here? Please help. Thank you for your time. Script: #!/usr/libexec/platform-python -tt from urllib.parse import quote import requests import sys import atexit sys.path.append("/usr/share/fence") from fencing import * def set_power_status(conn, options): if "on" in options["--action"]: response = requests.get(buildUrl(options, "on")) elif "off" in options["--action"]: response = requests.get(buildUrl(options, "off")) return def get_power_status(conn, options): response = requests.get(buildUrl(options, "status")) if "\"Power\":0" in response.text: return "off" elif "\"Power\":1" in response.text: return "on" def buildUrl(options, action): cmnd = { 'on' : 'Power On', 'off' : 'Power Off', 'status' : 'Status' } return "http://" + options["--ip"] + "/cm?user=" + quote(options["--username"]) + "&password=" + quote(options["--password"]) + "&cmnd=" + quote(cmnd.get(action, "Error")) def main(): device_opt = ["ipaddr", "login", "passwd", "web"] atexit.register(atexit_handler) all_opt["power_wait"]["default"] = 5 options = check_input(device_opt, process_input(device_opt)) docs = {} docs["shortdesc"] = "Fence agent for Tasmota-flashed Smarthome Plugs" docs["longdesc"] = "" docs["vendorurl"] = "" show_docs(options, docs) ## ## Fence operations #### result = fence_action(None, options, set_power_status, get_power_status) sys.exit(result) if __name__ == "__main__": main()

1 0

AFFINITY GROUPS
by LS CHENG 31 Jan '21

31 Jan '21

Hi I would like to know how AFFINITY GROUPS works. I have 2 VM in 2 hosts, each VM runs in a host. Let's call HOST_X where vm01 runs HOST_Y where vm02 runs I have set up an affinity group where it says vm01 relates to HOST_X, vm02 relates to HOST_Y. VM affinity rule is set to negative and HOST affinity rule set to positive. I need both vm01 and vm02 to run in their respective physical host. I have a problem, when vm01 is stopped and HOST_Y is rebooted vm02 starts in HOST_X, how can I avoid that? Thank you Luis Sanchez

3 3

recovering gluster volumes when moving hosts to a new datacenter
by Nathanaël Blanchet 30 Jan '21

30 Jan '21

Hi, I moved 3 hosts (for replica 3 volume) from a previous datacenter to a new datacenter. Those hosts had initially been configured in a gluster cluster and managed multiple gluster volume created with ovirt UI. These hosts are now apart of a new gluster cluster and they see each others with cli "gluster peer status" as well as the associated volumes "gluter volumes list". But I can't make gluster volumes visible in the usually "volume" tab, so ovirt doesn't seem to see them. Is there a way to import pre existing gluster volume so as to ovirt be able to manage them ? Thanks. -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 2

Windows 10 on older CPUs
by Chris Adams 29 Jan '21

29 Jan '21

I have an oVirt cluster running 4.3.10 on older hardware with a cluster CPU type of Intel Nehalem. I needed to install a Windows 10 (latest release) VM, which oVirt rejected because of the CPU model. I remember there being issues with certain versions of Windows and this CPU model under oVirt (I don't do Windows very often and had forgotten). I instead told oVirt I was installing Windows 8 (which it accepted), and then installed - it installed and appears to be working just fine. I don't know if Microsoft changed whatever used to break or what... I remember the problem before not even getting through install, so it seems to be okay. Any issues I should be worried about? -- Chris Adams <cma(a)cmadams.net>

1 0

ovirt node ng 4.4 crash in anaconda when setting ntp
by Gianluca Cecchi 29 Jan '21

29 Jan '21

Hello, when installing ovirt node ng 4.4 on a Dell M620 I remember I had a crash in anaconda if I try to set up ntp. Using ovirt-node-ng-installer-4.4.4-2020122111.el8.iso As soon as I select it and try to type the hostname to use, all stops and then anaconda aborts. Just today I had the same with the latest RHVH 4.4 iso: RHVH-4.4-20201210.0-RHVH-x86_64-dvd1.iso on an R630. Quite disappointing because I also have to fight with iDRAC8 to install the OS: it is slow to die. In practice I waste about one hour.... Is anyone aware of it or able to reproduce on another platform so that eventually I'm going to open a bug/case for it? My config is default one in anaconda accepting default and creating a bonded connection (LACP). Then as the last step I go into the set time/date and click on the ntp button and I get the problem as soon as I try to type inside the text box. Thanks, Gianluca

1 1

LVM Filesystem not mount VMStore
by marcel＠deheureu.se 29 Jan '21

29 Jan '21

Hi, We got the following error message from our 3 Server Setup this morning. Two of the servers where switched off by a "User". Simply power off. One of the server startup well and the other one provide the following message. What should we do first, we can't mount the vmstore manual. The system takes a lot of minutes. Did anyone have an idea? Br Marcel

5 5

[ANN] oVirt 4.4.5 Third Release Candidate is now available for testing
by Sandro Bonazzola 29 Jan '21

29 Jan '21

oVirt 4.4.5 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Third Release Candidate for testing, as of January 29th, 2021. This update is the fifth 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.5 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.5 (redeploy in case of already being on 4.4.5). 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 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 * oVirt Node 4.4 based on CentOS Linux 8.3 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * 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.5/ [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

How to reset network on all cluster members (controller and host) to defaults for cleans start?
by David Johnson 29 Jan '21

29 Jan '21

I have a new Ovirt 4.4.5 cluster consisting of a controller and a single host, both running on centos 8. I believe I have messed up my network configurations by using a mix of oVirt and nmcli functions to try to resolve problems. Is there an easy way to reset everything on the controller and host machines to get a clean start? Or do I need to start from scratch and re-install centos. Thank you in advance. David Johnson

2 1

Gluster volume slower then raid1 zpool speed
by Harry O 28 Jan '21

28 Jan '21

Hi, Can anyone help me with the performance on my 3 node gluster on zfs (it is setup with one arbiter) The performance on the single vm I have on it (with engine) is 50% worse then a single bare metal disk, on the writes. I have enabled "Optimize for virt store" I run 1Gbps 1500MTU network, could this be the write performance killer? Is this to be expected from a 2xHDD zfs raid one on each node, with 3xNode arbiter setup? Maybe I should move to raid 5 or 6? Maybe I should add SSD cache to raid1 zfs zpools? What are your thoughts? What to do for optimize this setup? I would like to run zfs with gluster and I can deal with a little performance loss, but not that much.

5 13

vGPU on ovirt 4.3
by kim.kargaard＠noroff.no 28 Jan '21

28 Jan '21

Hi, We are looking at getting some GPU's for our servers and to use vGPU passthrough so that our students can do some video renders on the VM's. Does anyone have good experience with the Nvidia Quadro RTX6000 or RTX8000 and ovirt 4.3? Thanks. Kim

7 12

centos 7.9
by suporte＠logicworks.pt 28 Jan '21

28 Jan '21

Hello, Can I run ovirt 4.3.10.4-1.el7 over Centos 7.9 ? Thanks -- Jose Ferradeira http://www.logicworks.pt

5 4

Re: VM templates
by Strahil Nikolov 28 Jan '21

28 Jan '21

If you system will have only Gluster -> you can blacklist everything in multipath.But imagine you have gluster and also SAN or iSCSI -> then you need to blacklist only local disks that Gluster uses, but not the SAN. Best Regards,Strahil Nikolov Sent from Yahoo Mail on Android On Wed, Jan 27, 2021 at 16:28, Robert Tongue<phunyguy(a)neverserio.us> wrote: #yiv8013230980 P {margin-top:0;margin-bottom:0;}Ahh, OK, I didn't realize that. I appreciate it, and was hoping to get good feedback like this when I posted what I did. Will make the changes. What is meant by "gluster only machine" here? From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Wednesday, January 27, 2021 7:11 AM To: Robert Tongue <phunyguy(a)neverserio.us>; users <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: VM templates You should create a file like mine, cause vdsm manages /etc/multipathd.conf # cat /etc/multipath/conf.d/blacklist.confblacklist { devnode "*" wwid nvme.1cc1-324a31313230303131343036-414441544120535838323030504e50-00000001 wwid TOSHIBA-TR200_Z7KB600SK46S wwid ST500NM0011_Z1M00LM7 wwid WDC_WD5003ABYX-01WERA0_WD-WMAYP2303189 wwid WDC_WD15EADS-00P8B0_WD-WMAVU0885453 wwid WDC_WD5003ABYZ-011FA0_WD-WMAYP0F35PJ4} Keep in mind 'devnode *' is OK only for gluster-only machine. Best Regards,Strahil Nikolov Sent from Yahoo Mail on Android On Wed, Jan 27, 2021 at 6:02, Robert Tongue<phunyguy(a)neverserio.us> wrote:_______________________________________________ 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/YD7ROMATPWFWO…

1 0

New setup - Failing to Activate storage domain on NFS shared storage
by Matt Snow 28 Jan '21

28 Jan '21

I installed ovirt node 4.4.4 as well as 4.4.5-pre and experience the same problem with both versions. The issue occurs in both cockpit UI and tmux'd CLI of ovirt-hosted-engine-setup. I get passed the point where the VM is created and running. I tried to do some debugging on my own before reaching out to this list. Any help is much appreciated! ovirt node hardware: NUC format Jetway w/ Intel N3160 (Braswell 4 cores/4threads), 8GB RAM, 64GB SSD. I understand this is underspec'd, but I believe it meets the minimum requirements. NFS server: * Ubuntu 19.10 w/ ZFS share w/ 17TB available space. * NFS share settings are just 'rw=(a)172.16.1.0/24' but have also tried 'rw,sec=sys,anon=0' and '@172.16.1.0/24,insecure' * The target directory is always empty and chown'd 36:36 with 0755 permissions. * I have tried using both IP and DNS names. forward and reverse DNS works from ovirt host and other systems on the network. * The NFS share always gets mounted successfully on the ovirt node system. * I have tried auto and v3 NFS versions in other various combinations. * I have also tried setting up an NFS server on a non-ZFS backed storage system that is open to any host and get the same errors as shown below. * I ran nfs-check.py script without issue against both NFS servers and followed other verification steps listed on https://www.ovirt.org/develop/troubleshooting-nfs-storage-issues.html ***Snip from ovirt-hosted-engine-setup*** Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs Please specify the nfs version you would like to use (auto, v3, v4, v4_0, v4_1, v4_2)[auto]: Please specify the full shared storage connection path to use (example: host:/path): stumpy.mydomain.com:/tanker/ovirt/host_storage If needed, specify additional mount options for the connection to the hosted-engine storagedomain (example: rsize=32768,wsize=32768) []: rw [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the storage interface to be up] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add NFS storage domain] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add glusterfs storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add iSCSI storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add Fibre Channel storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get storage domain details] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the appliance OVF] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Parse OVF] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get required size] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Remove unsuitable storage domain] [ INFO ] skipping: [localhost] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check storage domain free space] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Activate storage domain] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400."} Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: ***End snippet** The relevant section from /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-create_storage_domain-20210116195220-bnfg1w.log: **Snip*** 2021-01-16 19:53:56,010-0700 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f11a04c8320> kwargs 2021-01-16 19:53:57,219-0700 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engine_setup : Activate storage domain'} 2021-01-16 19:53:57,220-0700 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Activate storage domain kwargs is_conditional:False 2021-01-16 19:53:57,221-0700 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : Activate storage domain kwargs 2021-01-16 19:54:00,346-0700 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2021-01-16 19:54:00,347-0700 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2021-01-16 19:54:00,348-0700 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2021-01-16 19:54:00,349-0700 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_storage_domain_payload_f38n25ab/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py\", line 783, in main\n File \"/tmp/ansible_ovirt_storage_domain_payload_f38n25ab/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py\", line 638, in post_create_check\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py\", line 3647, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 232, in _internal_add\n return future.wait() if wait else future\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 55, in wait\n return self._code(response)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 229, in callback\n self._check_fault(respon se)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 132, in _check_fault\n self._raise_error(response, body)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 118, in _raise_error\n raise error\novirtsdk4.Error: Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400.\n", "invocation": { "module_args": { "backup": null, "comment": null, "critical_space_action_blocker": null, "data_center": "Default", "description": null, "destroy": null, "discard_after_delete": null, "domain_function": "data", "fcp": null, "fetch_nested": false, "format": null, "glusterfs": null, "host": "brick.mydomain.com", "id": null, "iscsi": null, "localfs": null, "managed_block_storage": null, "name": "hosted_storage", "nested_attributes": [], "nfs": null, "poll_interval": 3, "posixfs": null, "state": "present", "timeout": 180, "wait": true, "warning_low_space": null, "wipe_after_delete": null } }, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400." }, "ansible_task": "Activate storage domain", "ansible_type": "task", "status": "FAILED", "task_duration": 4 } 2021-01-16 19:54:00,350-0700 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f11a05f2d30> kwargs ignore_errors:None 2021-01-16 19:54:00,358-0700 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "01:35 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 23, 'failures': 1, 'unreachable': 0, 'changed': 0, 'skipped': 7, 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" } 2021-01-16 19:54:00,359-0700 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:05 ] Force facts gathering [ 00:03 ] Check local VM dir stat [ 00:04 ] Obtain SSO token using username/password credentials [ 00:04 ] Fetch host facts [ 00:02 ] Fetch cluster ID [ 00:04 ] Fetch cluster facts [ 00:04 ] Fetch Datacenter facts [ 00:02 ] Fetch Datacenter ID [ 00:02 ] Fetch Datacenter name [ 00:04 ] Add NFS storage domain [ 00:04 ] Get storage domain details [ 00:03 ] Find the appliance OVF [ 00:03 ] Parse OVF [ 00:02 ] Get required size [ FAILED ] Activate storage domain 2021-01-16 19:54:00,359-0700 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7f11a2e3b8d0> kwargs **End snip** The relevantsection from /var/log/vdsm/vdsm.log: ***begin snip*** 2021-01-16 19:53:58,439-0700 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=b8b21668-189e-4b68-a7f0-c2d2ebf14546 (api:48) 2021-01-16 19:53:58,439-0700 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=b8b21668-189e-4b68-a7f0-c2d2ebf14546 (api:54) 2021-01-16 19:53:58,440-0700 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:726) 2021-01-16 19:53:58,885-0700 INFO (jsonrpc/3) [vdsm.api] START connectStorageServer(domType=1, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'protocol_version': 'auto', 'port': '', 'iqn': '', 'connection': 'stumpy:/tanker/ovirt/host_storage', 'ipv6_enabled': 'false', 'id': '3ffd1e3b-168e-4248-a2af-b28fbdf49eef', 'user': '', 'tpgt': '1'}], options=None) from=::ffff:192.168.222.53,41192, flow_id=592e278f, task_id=5bd52fa3-f790-4ed3-826d-c1f51e5f2291 (api:48) 2021-01-16 19:53:58,892-0700 INFO (jsonrpc/3) [storage.StorageDomainCache] Invalidating storage domain cache (sdc:74) 2021-01-16 19:53:58,892-0700 INFO (jsonrpc/3) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'id': '3ffd1e3b-168e-4248-a2af-b28fbdf49eef', 'status': 0}]} from=::ffff:192.168.222.53,41192, flow_id=592e278f, task_id=5bd52fa3-f790-4ed3-826d-c1f51e5f2291 (api:54) 2021-01-16 19:53:58,914-0700 INFO (jsonrpc/6) [vdsm.api] START getStorageDomainInfo(sdUUID='54532dd4-3e5b-4885-b88e-599c81efb146', options=None) from=::ffff:192.168.222.53,41192, flow_id=592e278f, task_id=4d5a352d-6096-45b7-a4ee-b6e08ac02f7b (api:48) 2021-01-16 19:53:58,914-0700 INFO (jsonrpc/6) [storage.StorageDomain] sdUUID=54532dd4-3e5b-4885-b88e-599c81efb146 (fileSD:535) 2021-01-16 19:53:58,918-0700 INFO (jsonrpc/6) [vdsm.api] FINISH getStorageDomainInfo error=Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) from=::ffff:192.168.222.53,41192, flow_id=592e278f, task_id=4d5a352d-6096-45b7-a4ee-b6e08ac02f7b (api:52) 2021-01-16 19:53:58,918-0700 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='4d5a352d-6096-45b7-a4ee-b6e08ac02f7b') Unexpected error (task:880) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 887, in _run return fn(*args, **kargs) File "<decorator-gen-131>", line 2, in getStorageDomainInfo File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2796, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 312, in validateSdUUID sdDom.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 538, in validate raise se.StorageDomainAccessError(self.sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) 2021-01-16 19:53:58,918-0700 INFO (jsonrpc/6) [storage.TaskManager.Task] (Task='4d5a352d-6096-45b7-a4ee-b6e08ac02f7b') aborting: Task is aborted: "value=Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) abortedcode=379" (task:1190) 2021-01-16 19:53:58,918-0700 ERROR (jsonrpc/6) [storage.Dispatcher] FINISH getStorageDomainInfo error=Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) (dispatcher:83) 2021-01-16 19:53:58,919-0700 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call StorageDomain.getInfo failed (error 379) in 0.00 seconds (__init__:312) 2021-01-16 19:53:58,956-0700 INFO (jsonrpc/1) [vdsm.api] START createStoragePool(poolType=None, spUUID='91fb3f22-5795-11eb-ad9f-00163e3f4683', poolName='Default', masterDom='54532dd4-3e5b-4885-b88e-599c81efb146', domList=['54532dd4-3e5b-4885-b88e-599c81efb146'], masterVersion=7, lockPolicy=None, lockRenewalIntervalSec=5, leaseTimeSec=60, ioOpTimeoutSec=10, leaseRetries=3, options=None) from=::ffff:192.168.222.53,41192, flow_id=592e278f, task_id=a946357f-537a-4c9c-9040-e70a98ee5643 (api:48) 2021-01-16 19:53:58,958-0700 INFO (jsonrpc/1) [storage.StoragePool] updating pool 91fb3f22-5795-11eb-ad9f-00163e3f4683 backend from type NoneType instance 0x7f86e45f89d0 to type StoragePoolDiskBackend instance 0x7f8680738408 (sp:157) 2021-01-16 19:53:58,958-0700 INFO (jsonrpc/1) [storage.StoragePool] spUUID=91fb3f22-5795-11eb-ad9f-00163e3f4683 poolName=Default master_sd=54532dd4-3e5b-4885-b88e-599c81efb146 domList=['54532dd4-3e5b-4885-b88e-599c81efb146'] masterVersion=7 {'LEASERETRIES': 3, 'LEASETIMESEC': 60, 'LOCKRENEWALINTERVALSEC': 5, 'IOOPTIMEOUTSEC': 10} (sp:602) 2021-01-16 19:53:58,958-0700 INFO (jsonrpc/1) [storage.StorageDomain] sdUUID=54532dd4-3e5b-4885-b88e-599c81efb146 (fileSD:535) 2021-01-16 19:53:58,963-0700 ERROR (jsonrpc/1) [storage.StoragePool] Unexpected error (sp:618) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 613, in create domain.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 538, in validate raise se.StorageDomainAccessError(self.sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) 2021-01-16 19:53:58,963-0700 INFO (jsonrpc/1) [vdsm.api] FINISH createStoragePool error=Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) from=::ffff:192.168.222.53,41192, flow_id=592e278f, task_id=a946357f-537a-4c9c-9040-e70a98ee5643 (api:52) 2021-01-16 19:53:58,963-0700 ERROR (jsonrpc/1) [storage.TaskManager.Task] (Task='a946357f-537a-4c9c-9040-e70a98ee5643') Unexpected error (task:880) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 613, in create domain.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 538, in validate raise se.StorageDomainAccessError(self.sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 887, in _run return fn(*args, **kargs) File "<decorator-gen-31>", line 2, in createStoragePool File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 1027, in createStoragePool leaseParams) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 619, in create raise se.StorageDomainAccessError(sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) 2021-01-16 19:53:58,964-0700 INFO (jsonrpc/1) [storage.TaskManager.Task] (Task='a946357f-537a-4c9c-9040-e70a98ee5643') aborting: Task is aborted: "value=Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) abortedcode=379" (task:1190) 2021-01-16 19:53:58,964-0700 ERROR (jsonrpc/1) [storage.Dispatcher] FINISH createStoragePool error=Domain is either partially accessible or entirely inaccessible: ('54532dd4-3e5b-4885-b88e-599c81efb146',) (dispatcher:83) 2021-01-16 19:53:58,965-0700 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call StoragePool.create failed (error 379) in 0.01 seconds (__init__:312) 2021-01-16 19:54:01,923-0700 INFO (jsonrpc/5) [api.host] START getStats() from=::ffff:192.168.222.53,41192 (api:48) 2021-01-16 19:54:01,964-0700 INFO (jsonrpc/7) [api.host] START getAllVmStats() from=::ffff:192.168.222.53,41192 (api:48) 2021-01-16 19:54:01,966-0700 INFO (jsonrpc/7) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::ffff:192.168.222.53,41192 (api:54) 2021-01-16 19:54:01,977-0700 INFO (jsonrpc/5) [vdsm.api] START repoStats(domains=()) from=::ffff:192.168.222.53,41192, task_id=7a6c8536-3f1e-41b3-9ab7-bb58a5e75fac (api:48) 2021-01-16 19:54:01,978-0700 INFO (jsonrpc/5) [vdsm.api] FINISH repoStats return={} from=::ffff:192.168.222.53,41192, task_id=7a6c8536-3f1e-41b3-9ab7-bb58a5e75fac (api:54) 2021-01-16 19:54:01,980-0700 INFO (jsonrpc/5) [vdsm.api] START multipath_health() from=::ffff:192.168.222.53,41192, task_id=b8af45b5-6488-4940-b7d0-1d11b5f76db4 (api:48) 2021-01-16 19:54:01,981-0700 INFO (jsonrpc/5) [vdsm.api] FINISH multipath_health return={} from=::ffff:192.168.222.53,41192, task_id=b8af45b5-6488-4940-b7d0-1d11b5f76db4 (api:54) 2021-01-16 19:54:01,996-0700 INFO (jsonrpc/5) [api.host] FINISH getStats return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} from=::ffff:192.168.222.53,41192 (api:54) ***end snip***

5 26

New failure Gluster deploy: Set granual-entry-heal on --> Bricks down
by Charles Lam 27 Jan '21

27 Jan '21

Dear friends, Thanks to Donald and Strahil, my earlier Gluster deploy issue was resolved by disabling multipath on the nvme drives. The Gluster deployment is now failing on the three node hyperconverged oVirt v4.3.3 deployment at: TASK [gluster.features/roles/gluster_hci : Set granual-entry-heal on] ********** task path: /etc/ansible/roles/gluster.features/roles/gluster_hci/tasks/hci_volumes.yml:67 with: "stdout": "One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals\nVolume heal failed." Specifically: TASK [gluster.features/roles/gluster_hci : Set granual-entry-heal on] ********** task path: /etc/ansible/roles/gluster.features/roles/gluster_hci/tasks/hci_volumes.yml:67 failed: [fmov1n1.sn.dtcorp.com] (item={'volname': 'engine', 'brick': '/gluster_bricks/engine/engine', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["gluster", "volume", "heal", "engine", "granular-entry-heal", "enable"], "delta": "0:00:10.112451", "end": "2020-12-18 19:50:22.818741", "item": {"arbiter": 0, "brick": "/gluster_bricks/engine/engine", "volname": "engine"}, "msg": "non-zero return code", "rc": 107, "start": "2020-12-18 19:50:12.706290", "stderr": "", "stderr_lines": [], "stdout": "One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals\nVolume heal failed.", "stdout_lines": ["One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals", "Volume heal failed."]} failed: [fmov1n1.sn.dtcorp.com] (item={'volname': 'data', 'brick': '/gluster_bricks/data/data', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["gluster", "volume", "heal", "data", "granular-entry-heal", "enable"], "delta": "0:00:10.110165", "end": "2020-12-18 19:50:38.260277", "item": {"arbiter": 0, "brick": "/gluster_bricks/data/data", "volname": "data"}, "msg": "non-zero return code", "rc": 107, "start": "2020-12-18 19:50:28.150112", "stderr": "", "stderr_lines": [], "stdout": "One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals\nVolume heal failed.", "stdout_lines": ["One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals", "Volume heal failed."]} failed: [fmov1n1.sn.dtcorp.com] (item={'volname': 'vmstore', 'brick': '/gluster_bricks/vmstore/vmstore', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["gluster", "volume", "heal", "vmstore", "granular-entry-heal", "enable"], "delta": "0:00:10.113203", "end": "2020-12-18 19:50:53.767864", "item": {"arbiter": 0, "brick": "/gluster_bricks/vmstore/vmstore", "volname": "vmstore"}, "msg": "non-zero return code", "rc": 107, "start": "2020-12-18 19:50:43.654661", "stderr": "", "stderr_lines": [], "stdout": "One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals\nVolume heal failed.", "stdout_lines": ["One or more bricks could be down. Please execute the command again after bringing all bricks online and finishing any pending heals", "Volume heal failed."]} Any suggestions regarding troubleshooting, insight or recommendations for reading are greatly appreciated. I apologize for all the email and am only creating this as a separate thread as it is a new, presumably unrelated issue. I welcome any recommendations if I can improve my forum etiquette. Respectfully, Charles

4 19

Re: VM templates
by Strahil Nikolov 27 Jan '21

27 Jan '21

You should create a file like mine, cause vdsm manages /etc/multipathd.conf # cat /etc/multipath/conf.d/blacklist.confblacklist { devnode "*" wwid nvme.1cc1-324a31313230303131343036-414441544120535838323030504e50-00000001 wwid TOSHIBA-TR200_Z7KB600SK46S wwid ST500NM0011_Z1M00LM7 wwid WDC_WD5003ABYX-01WERA0_WD-WMAYP2303189 wwid WDC_WD15EADS-00P8B0_WD-WMAVU0885453 wwid WDC_WD5003ABYZ-011FA0_WD-WMAYP0F35PJ4} Keep in mind 'devnode *' is OK only for gluster-only machine. Best Regards,Strahil Nikolov Sent from Yahoo Mail on Android On Wed, Jan 27, 2021 at 6:02, Robert Tongue<phunyguy(a)neverserio.us> wrote: _______________________________________________ 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/YD7ROMATPWFWO…

2 1

Ovirt reporting dashboard not working
by suporte＠logicworks.pt 27 Jan '21

27 Jan '21

Hello, Had a problem with the engine server, the clock changed to 2026 and now I don't have any report on the dashboard. The version is 4.2.3.8-1.el7 Any idea? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 8

Re: VM templates
by Robert Tongue 27 Jan '21

27 Jan '21

Correction, the issue came back, but I fixed it again, the actual issue was multipathd. I had to set up device filters in /etc/multipath.conf blacklist { protocol "(scsi:adt|scsi:sbp)" devnode "^hd[a-z]" devnode "^sd[a-z]$" devnode "^sd[a-z]" devnode "^nvme0n1" devnode "^nvme0n1p$"blacklist { } Probably overkill, but it works. ________________________________ From: Robert Tongue <phunyguy(a)neverserio.us> Sent: Tuesday, January 26, 2021 2:24 PM To: users <users(a)ovirt.org> Subject: Re: VM templates I fixed my own issue, and for everyone else that may run into this, the issue was the fact that I created the first oVirt node VM inside VMware, and got it fully configured with all the software/disks/partitioning/settings, then cloned it to two more VMs. Then I ran the hosted-engine deployment and set up the cluster. I think it was because I used clones for each cluster node, and that confused things due to device/system identifiers. I rebuilt all 3 node VMs from scratch, and everything works perfectly now. Thanks for listening. ________________________________ From: Robert Tongue Sent: Monday, January 25, 2021 10:03 AM To: users <users(a)ovirt.org> Subject: VM templates Hello, Another weird issue over here. I have the latest oVirt running inside VMware Vcenter, as a proof of concept/testing platform. Things are working well finally, for the most part, however I am noticing strange behavior with templates, and deployed VMs from that template. Let me explain: I created a basic Ubuntu Server VM, captured that VM as a template, then deployed 4 VMs from that template. The deployment went fine; however I can only start 3 of the 4 VMs. If I shut one down one of the 3 that I started, I can then start the other one that refused to start, then the one I JUST shut down will then refuse to start. The error is: VM test3 is down with error. Exit message: Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'file', 'specParams': {}, 'alias': 'ua-2dc7fbff-da30-485d-891f-03a0ed60fd0a', 'address': {'bus': '0', 'controller': '0', 'unit': '0', 'type': 'drive', 'target': '0'}, 'domainID': '804c6a0c-b246-4ccc-b3ab-dd4ceb819cea', 'imageID': '2dc7fbff-da30-485d-891f-03a0ed60fd0a', 'poolID': '3208bbce-5e04-11eb-9313-00163e281c6d', 'volumeID': 'f514ab22-07ae-40e4-9146-1041d78553fd', 'path': '/rhev/data-center/3208bbce-5e04-11eb-9313-00163e281c6d/804c6a0c-b246-4ccc-b3ab-dd4ceb819cea/images/2dc7fbff-da30-485d-891f-03a0ed60fd0a/f514ab22-07ae-40e4-9146-1041d78553fd', 'discard': True, 'format': 'cow', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'scsi', 'name': 'sda', 'bootOrder': '1', 'serial': '2dc7fbff-da30-485d-891f-03a0ed60fd0a', 'index': 0, 'reqsize': '0', 'truesize': '2882392576', 'apparentsize': '3435134976'}. The underlying storage is GlusterFS, self-managed outside of oVirt. I can provide any logs needed, please let me know which. Thanks in advance.

1 0

OVN and change of mgmt network
by Gianluca Cecchi 26 Jan '21

26 Jan '21

Hello, I previously had OVN running on engine (as OVN provider with northd and northbound and southbound DBs) and hosts (with OVN controller). After changing mgmt ip of hosts (engine has retained instead the same ip), I executed again on them the command: vdsm-tool ovn-config <ip_of_engine> <nel_local_ip_of_host> Now I think I have to clean up some things, eg: 1) On engine where I get these lines below systemctl status ovn-northd.service -l . . . Sep 29 14:41:42 ovmgr1 ovsdb-server[940]: ovs|00005|reconnect|ERR|tcp: 10.4.167.40:37272: no response to inactivity probe after 5 seconds, disconnecting Oct 03 11:52:00 ovmgr1 ovsdb-server[940]: ovs|00006|reconnect|ERR|tcp: 10.4.167.41:52078: no response to inactivity probe after 5 seconds, disconnecting The two IPs are the old ones of two hosts It seems that a restart of the services has fixed... Can anyone confirm if I have to do anything else? 2) On hosts (there are 3 hosts with OVN on ip 10.4.192.32/33/34) where I currently have this output [root@ov301 ~]# ovs-vsctl show 3a38c5bb-0abf-493d-a2e6-345af8aedfe3 Bridge br-int fail_mode: secure Port "ovn-1dce5b-0" Interface "ovn-1dce5b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.32"} Port "ovn-ddecf0-0" Interface "ovn-ddecf0-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.33"} Port "ovn-fd413b-0" Interface "ovn-fd413b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.168.74"} Port br-int Interface br-int type: internal ovs_version: "2.7.2" [root@ov301 ~]# The IPs of kind 10.4.192.x are ok. But there is a left-over of an old host I initially used for tests, corresponding to 10.4.168.74, that now doesn't exist anymore How can I clean records for 1) and 2)? Thanks, Gianluca

3 4

Re: VM templates
by Robert Tongue 26 Jan '21

26 Jan '21

I fixed my own issue, and for everyone else that may run into this, the issue was the fact that I created the first oVirt node VM inside VMware, and got it fully configured with all the software/disks/partitioning/settings, then cloned it to two more VMs. Then I ran the hosted-engine deployment and set up the cluster. I think it was because I used clones for each cluster node, and that confused things due to device/system identifiers. I rebuilt all 3 node VMs from scratch, and everything works perfectly now. Thanks for listening. ________________________________ From: Robert Tongue Sent: Monday, January 25, 2021 10:03 AM To: users <users(a)ovirt.org> Subject: VM templates Hello, Another weird issue over here. I have the latest oVirt running inside VMware Vcenter, as a proof of concept/testing platform. Things are working well finally, for the most part, however I am noticing strange behavior with templates, and deployed VMs from that template. Let me explain: I created a basic Ubuntu Server VM, captured that VM as a template, then deployed 4 VMs from that template. The deployment went fine; however I can only start 3 of the 4 VMs. If I shut one down one of the 3 that I started, I can then start the other one that refused to start, then the one I JUST shut down will then refuse to start. The error is: VM test3 is down with error. Exit message: Bad volume specification {'device': 'disk', 'type': 'disk', 'diskType': 'file', 'specParams': {}, 'alias': 'ua-2dc7fbff-da30-485d-891f-03a0ed60fd0a', 'address': {'bus': '0', 'controller': '0', 'unit': '0', 'type': 'drive', 'target': '0'}, 'domainID': '804c6a0c-b246-4ccc-b3ab-dd4ceb819cea', 'imageID': '2dc7fbff-da30-485d-891f-03a0ed60fd0a', 'poolID': '3208bbce-5e04-11eb-9313-00163e281c6d', 'volumeID': 'f514ab22-07ae-40e4-9146-1041d78553fd', 'path': '/rhev/data-center/3208bbce-5e04-11eb-9313-00163e281c6d/804c6a0c-b246-4ccc-b3ab-dd4ceb819cea/images/2dc7fbff-da30-485d-891f-03a0ed60fd0a/f514ab22-07ae-40e4-9146-1041d78553fd', 'discard': True, 'format': 'cow', 'propagateErrors': 'off', 'cache': 'none', 'iface': 'scsi', 'name': 'sda', 'bootOrder': '1', 'serial': '2dc7fbff-da30-485d-891f-03a0ed60fd0a', 'index': 0, 'reqsize': '0', 'truesize': '2882392576', 'apparentsize': '3435134976'}. The underlying storage is GlusterFS, self-managed outside of oVirt. I can provide any logs needed, please let me know which. Thanks in advance.

1 0

Replaced host but ovn complains of duplicate port
by Kevin Doyle 26 Jan '21

26 Jan '21

I had to rebuild a host. I first removed it from Ovirt then reinstalled the OS. I then used the same 192.xxx.xxx.207 IP as the old host. I then added it to Ovirt which seem to go OK. However I am seeing lots of ovn errors complaining that there was an existing port for the same IP Port ovn-47cc88-0 new port is ovn-af7f78-0 ovs-vsctl show 34c43e58-46f5-4217-8f2e-5801e1f2b9de Bridge br-int fail_mode: secure Port "ovn-24b972-0" Interface "ovn-24b972-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.204"} Port "ovn-ec1bbd-0" Interface "ovn-ec1bbd-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.201"} Port "ovn-47cc88-0" Interface "ovn-47cc88-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.207"} Port "ovn-d1e09d-0" Interface "ovn-d1e09d-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.203"} Port "ovn-f5ded7-0" Interface "ovn-f5ded7-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.202"} Port "ovn-1cb1b0-0" Interface "ovn-1cb1b0-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.206"} Port br-int Interface br-int type: internal Port "ovn-af7f78-0" Interface "ovn-af7f78-0" type: geneve options: {csum="true", key=flow, remote_ip="192.xxx.xxx.207"} error: "could not add network device ovn-af7f78-0 to ofproto (File exists)" ovs_version: "2.10.1" / var/log/ovs-vswitchd.log tunnel|WARN|ovn-af7f78-0: attempting to add tunnel port with same config as port 'ovn-47cc88-0' (::->192.xxx.xxx.207, key=flow, legacy_l2, dp port=2) 2021-01-26T18:03:38.128Z|69740|ofproto|WARN|br-int: could not add port ovn-af7f78-0 (File exists) 2021-01-26T18:03:38.128Z|69741|bridge|WARN|could not add network device ovn-af7f78-0 to ofproto (File exists) /var/log/messages Jan 26 18:03:37 xxxx05 kernel: device genev_sys_6081 entered promiscuous mode Jan 26 18:03:37 xxxx05 kernel: i40e 0000:3d:00.0 eno3: UDP port 6081 was not found, not deleting Jan 26 18:03:37 xxxx05 kernel: i40e 0000:3d:00.1 eno4: UDP port 6081 was not found, not deleting Jan 26 18:03:37 xxxx05 kernel: i40e 0000:3d:00.2 eno5: UDP port 6081 was not found, not deleting Jan 26 18:03:37 xxxx05 kernel: i40e 0000:3d:00.3 eno6: UDP port 6081 was not found, not deleting I can bring the host 192.xxx.xxx.107 down and the errors stop on the other hosts but ovn still has a port defined for 192.xxx.xxx.207 The question I have is how do I delete the old port definition ? Regards Kevin

1 0