- Users - oVirt List Archives

deployment fails - debug: var=server_cpu_dict
by lejeczek 06 Jun '21

06 Jun '21

Hi guys, my: -> $ ovirt-hosted-engine-setup fails every time with: ... [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Convert CPU model name] [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute ''\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 69, column 15, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook ... An expert would care to comment? many thanks, L

3 7

Hosted-engine fail and host reboot
by Dominique D 05 Jun '21

05 Jun '21

I tried with a 1 baremetal host, 3 baremetals or virtual hosts and I still have the same problem for installing the hosted-engine. Hyperconverge installs well. I have tried with multiple version of ovirt ISO file 4.4.1 and 4.4.4 and 4.4.6. when I run hosted-engine --deploy or with the cockpit, it creates a temporary VM in the 192.168.222.x subnet and I am able to connect in ssh on this temporary ip. When the script displays "TASK [ovirt.ovirt.hoted_engine_setup]: Wait for the host to be up" the server reboots and I have nothing left. problem when creation of the ovirtmgmt? here all my log https://drive.google.com/drive/folders/1kFFSlIqbjVwSN8t88aQZZR45DYEHPUvt?us… 021-05-26 10:15:09,135-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 TASK [ovirt.ovirt.hosted_engine_setup : Always revoke the SSO token] 2021-05-26 10:15:10,439-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:105 {'msg': "You must specify either 'url' or 'hostname'.", 'invocation': {'module_args': {'state': 'absent', 'ovirt_auth': {'changed': False, 'ansible_facts': {'ovirt_auth': {'token': 'Mz2onwB7qWX2x8HnJVgetQIQ9U4eVziRt8TEabfoizI2B98d0PDp-yxTU92a9lbun2vcr_i5yOXRsJKJKhqkVw', 'url': 'https://oe.telecom.lan/ovirt-engine/api', 'ca_file': None, 'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None}}, 'failed': False, 'attempts': 1}, 'timeout': 0, 'compress': True, 'kerberos': False, 'url': None, 'hostname': None, 'username': None, 'password': None, 'ca_file': None, 'insecure': None, 'headers': None, 'token': None}}, '_ansible_no_log': False, 'changed': False} 2021-05-26 10:15:10,540-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:105 ignored: [localhost]: FAILED! => {"changed": false, "msg": "You must specify either 'url' or 'hostname'."} 2021-05-26 10:15:11,643-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] 2021-05-26 10:15:12,647-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 ok: [localhost] 2021-05-26 10:15:13,851-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] 2021-05-26 10:15:15,261-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 ok: [localhost] 2021-05-26 10:15:17,275-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:111 TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] 2021-05-26 10:22:54,758-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': SIG1 2021-05-26 10:22:54,762-0400 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2021-05-26 10:22:54,763-0400 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2021-05-26 10:22:54,763-0400 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'RuntimeError'>, RuntimeError('SIG1',), <traceback object at 0x7fa8fc1ca1c8>)]' thank you

6 12

Adding a Ubuntu Host's NFS share to oVirt
by David White 04 Jun '21

04 Jun '21

Hello, Is it possible to use Ubuntu to share an NFS export with oVirt?I'm trying to setup a Backup Domain for my environment. I got to the point of actually adding the new Storage Domain. When I click OK, I see the storage domain appear momentarily before disappearing, at which point I get a message about oVirt not being able to obtain a lock. It appears I'm running into the issue described in this thread: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/BNVXUH5B26FBFC… ... Although the actual export is ext4, not xfs. From what I'm reading on that thread and elsewhere, it sounds like this problem is a result of SELinux not being present, is that correct? Is my only option here to install an OS that supports SELinux? Sent with ProtonMail Secure Email.

3 4

Re: [oVirt 4.4.6] Offline deployment of hosted engine
by Strahil Nikolov 04 Jun '21

04 Jun '21

I think you can download and install the ovirt-engine-appliance rpm (the big one) from https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/x86_64/ in advance. Best Regards,Strahil Nikolov On Fri, Jun 4, 2021 at 9:40, sharma.ishan(a)fujitsu.com<sharma.ishan(a)fujitsu.com> wrote:  Hello, I am trying to test oVirt node 4.4.6 inside my company’s network which needs proxy setting for internet access. Is there any possibility to deploy host engine without any internet access? i.e. Is offline deployment of hosted engine possible? I have added the following line at the end of the file /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml environment: https_proxy: "http://<proxy_host>:<proxy_port>" http_proxy: "http://<proxy_host>:<proxy_port>" But it gives error in the process of “hosted-engine --deploy”. I am not sure if this a typical issue in my company’s network but, it would be great if there is any offline installation method (without accessing internet repository). I have also tried to use “hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true” but, it is not helping me at all. With regards ********************************************** Ishan Nath Sharma Technical Computing Solutions Unit Fujitsu Limited E-mail:sharma.ishan@jp.fujitsu.com http://www.fujitsu.com ********************************************** _______________________________________________ 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/Z2Q3JFI5ARXV7…

2 1

Can't remove snapshot
by David Johnson 04 Jun '21

04 Jun '21

Hi all, I patched one of my Windows VM's yesterday. I started by snapshotting the VM, then applied the Windows update. Now that the patch has been tested, I want to remove the snapshot. I get this message: Error while executing action: win-sql-2019: - Cannot remove Snapshot. The following attached disks are in ILLEGAL status: win-2019-tmpl_Disk1 - please remove them and try again. Does anyone have any thoughts how to recover from this? I really don't want to keep this snapshot hanging around. Thanks in advance, *David Johnson*

3 6

oVirt 2021 online conference
by Sandro Bonazzola 04 Jun '21

04 Jun '21

It is our pleasure to invite you to the oVirt 2021 online conference. The conference, organized by the oVirt community, will take place online on Monday, September 6th 2021! oVirt 2021 is a free conference for oVirt community project users and contributors coming to a web browser near you! There is no admission or ticket charge for this event. However, you are required to complete a free registration. Watch https://blogs.ovirt.org/ovirt-2021-online-conference/ for updates about registration. Talks, presentations and workshops will all be in English. We encourage students and new graduates as well as professionals to submit proposals to oVirt conferences. The theme of oVirt 2021 online conference will be about making it easy to contribute to the oVirt project and celebrating 10 years of oVirt. We will be looking for talks and discussions across virtualization, and how oVirt 4.4 can effectively solve user issues around: - Developing for oVirt - Integrating with oVirt - New features - User stories The deadline to submit abstracts is July 25th 2021. To submit your abstract, please click on the following link: submission form <https://forms.gle/CeCbGmNpvPs6fC2M8> More information are available at https://blogs.ovirt.org/ovirt-2021-online-conference/ Thanks, -- 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

[ANN] oVirt 4.4.7 Second Release Candidate is now available for testing
by Sandro Bonazzola 04 Jun '21

04 Jun '21

oVirt 4.4.7 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 Second Release Candidate for testing, as of June 4th, 2021. This update is the seventh 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. If you are upgrading from 4.4.1 please check previous versions release notes about Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> 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.7 release highlights: http://www.ovirt.org/release/4.4.7/ * 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.7/ [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

[oVirt 4.4.6] Offline deployment of hosted engine
by sharma.ishan＠fujitsu.com 04 Jun '21

04 Jun '21

Hello, I am trying to test oVirt node 4.4.6 inside my company’s network which needs proxy setting for internet access. Is there any possibility to deploy host engine without any internet access? i.e. Is offline deployment of hosted engine possible? I have added the following line at the end of the file /usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml environment: https_proxy: "http://<proxy_host>:<proxy_port>" http_proxy: "http://<proxy_host>:<proxy_port>" But it gives error in the process of “hosted-engine --deploy”. I am not sure if this a typical issue in my company’s network but, it would be great if there is any offline installation method (without accessing internet repository). I have also tried to use “hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true” but, it is not helping me at all. With regards ********************************************** Ishan Nath Sharma Technical Computing Solutions Unit Fujitsu Limited E-mail: sharma.ishan(a)jp.fujitsu.com<mailto:sharma.ishan@jp.fujitsu.com> http://www.fujitsu.com **********************************************

1 0

Fwd: Can't remove snapshot
by Roman Bednar 03 Jun '21

03 Jun '21

Ok, sounds good. Forgot to include the mailing list, doing it now. ---------- Forwarded message --------- From: David Johnson <djohnson(a)maxistechnology.com> Date: Thu, Jun 3, 2021 at 11:17 AM Subject: Re: [ovirt-users] Can't remove snapshot To: Roman Bednar <rbednar(a)redhat.com> Thanks, I'll check it out. Since my business is replatforming and transforming databases, digging around the DB is something I will be very comfortable with. I won't be able to do anything until Friday. I'll let you know how it goes. David Johnson On Thu, Jun 3, 2021, 2:40 AM Roman Bednar <rbednar(a)redhat.com> wrote: > Digging a bit further I found this is a known issue. A discrepancy can > occur between vdsm and engine db when removing a snapshot. > > It's been already discussed [1] and a bug is filed [2]. In the discussion > you can find a workaround which is manual removal of the snapshot. > > Don't forget to backup the engine database by running 'engine-backup' tool > on the engine node before doing any changes. > Restore requires a bit more options and can be done like this: > > # engine-backup > --file=/var/lib/ovirt-engine-backup/ovirt-engine-backup-20210602055605.backup > --mode=restore --provision-all-databases > > To check if the discrepancy occurred you can check the db and compare that > to what vdsm sees (which is a source of truth). > > The example below shows a consistent setup from my env with one snapshot, > if there is anything extra in your env in the > db it should be removed and the parent id changed accordingly [3]. > > image_group_id (db) == image (vdsm) > image_guid (db) == logical volume on host (vdsm) > > Engine node: > > # su - postgres > # psql > postgres=# \c engine > engine=# select image_guid, image_group_id, parentid from images where > image_group_id = 'e75318bf-c563-4d66-99e4-63645736a418'; > image_guid | image_group_id > | parentid > > --------------------------------------+--------------------------------------+-------------------------------------- > 1955f6de-658a-43c3-969b-79db9b4bf14c | > e75318bf-c563-4d66-99e4-63645736a418 | 00000000-0000-0000-0000-000000000000 > d6662661-eb87-4c01-a204-477919e65221 | > e75318bf-c563-4d66-99e4-63645736a418 | 1955f6de-658a-43c3-969b-79db9b4bf14c > > > Host node: > > # vdsm-tool dump-volume-chains <STORAGE_DOMAIN_ID> > > Images volume chains (base volume first) > > image: e75318bf-c563-4d66-99e4-63645736a418 > > - 1955f6de-658a-43c3-969b-79db9b4bf14c > status: OK, voltype: INTERNAL, format: RAW, legality: > LEGAL, type: PREALLOCATED, capacity: 5368709120, truesize: 5368709120 > > - d6662661-eb87-4c01-a204-477919e65221 > status: OK, voltype: LEAF, format: COW, legality: LEGAL, > type: SPARSE, capacity: 5368709120, truesize: 3221225472 > ... > > > I hope this helps a bit and if you need further assistance let us know, > it's not very convenient to change the db > manually like this but a fix should be on the way :) > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1948599 > [2] > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/7ZU7NWHBW3B2NB… > [3] > https://lists.ovirt.org/archives/list/users@ovirt.org/message/D2HKS2RFMNKGP… > > On Tue, Jun 1, 2021 at 8:19 PM David Johnson <djohnson(a)maxistechnology.com> > wrote: > >> Yes, I have the same error on the second try. >> >> You can see it happening in the engine log starting at 2021-05-31 07:49. >> >> >> *David Johnson* >> *Director of Development, Maxis Technology* >> 844.696.2947 ext 702 (o) | 479.531.3590 (c) >> <https://www.linkedin.com/in/pojoguy/> >> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson.v…> >> <https://maxistechnology.com/> >> >> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/> >> >> >> On Tue, Jun 1, 2021 at 7:48 AM Roman Bednar <rbednar(a)redhat.com> wrote: >> >>> Hi David, >>> >>> awesome, thanks for the reply. Looking at the logs there does not seem >>> anything suspicious on vdsm side and as you said the snapshots are really >>> gone when looking from vdsm. I tried to reproduce without much success but >>> it looks like a problem on the engine side. >>> >>> Did you get the same error saying that the disks are illegal on the >>> second try? There should be more in the engine log so try checking it as >>> well to see if this is really on the engine side. >>> >>> It would be great to have a reproducer for this and file the bug so we >>> can track this and provide a fix. >>> >>> >>> -Roman >>> >>> >>> >>> On Mon, May 31, 2021 at 3:20 PM David Johnson < >>> djohnson(a)maxistechnology.com> wrote: >>> >>>> Hi Roman, >>>> >>>> Thank you for your assistance. >>>> >>>> I found another snapshot that needed collapsing, and deleted that. >>>> These logs include that execution. >>>> >>>> Prior to the execution, the vdsm-dump listed snapshot volumes. >>>> Post-execution, the snapshot volumes were absent. That suggests to me that >>>> the snapshot was actually removed, but Ovirt is confused. >>>> >>>> >>>> >>>> >>>> >>>> *David Johnson* >>>> *Director of Development, Maxis Technology* >>>> 844.696.2947 ext 702 (o) | 479.531.3590 (c) >>>> <https://www.linkedin.com/in/pojoguy/> >>>> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson.v…> >>>> <https://maxistechnology.com/> >>>> >>>> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/> >>>> >>>> >>>> On Mon, May 31, 2021 at 5:54 AM Roman Bednar <rbednar(a)redhat.com> >>>> wrote: >>>> >>>>> Hello David, >>>>> >>>>> there's quite a few reasons a volume could be marked as illegal, e.g. >>>>> failed operation that left the volume in this state. This is done in vdsm >>>>> so please provide a vdsm log on the host running the VM so we can check >>>>> exactly what went wrong. Also the state of the storage domain could be >>>>> helpful to see what volumes are present and marked illegal, you can get the >>>>> information by running: >>>>> >>>>> # vdsm-client StorageDomain dump sd_id=<SD_ID> >>>>> >>>>> >>>>> >>>>> -Roman >>>>> >>>>> On Fri, May 28, 2021 at 6:10 PM David Johnson < >>>>> djohnson(a)maxistechnology.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I patched one of my Windows VM's yesterday. I started by >>>>>> snapshotting the VM, then applied the Windows update. Now that the patch >>>>>> has been tested, I want to remove the snapshot. I get this message: >>>>>> >>>>>> Error while executing action: >>>>>> >>>>>> win-sql-2019: >>>>>> >>>>>> - Cannot remove Snapshot. The following attached disks are in >>>>>> ILLEGAL status: win-2019-tmpl_Disk1 - please remove them and try again. >>>>>> >>>>>> >>>>>> Does anyone have any thoughts how to recover from this? I really >>>>>> don't want to keep this snapshot hanging around. >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> *David Johnson* >>>>>> >>>>>> _______________________________________________ >>>>>> 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/PJODGOB2MI6EQ… >>>>>> >>>>>

1 0

how to start fedora coreos
by matthias.waldrey＠mail.de 03 Jun '21

03 Jun '21

Hello, i try to use fedora coreos 34 from glance-repo. i import template, choose as type redhat coreos and start with only user + key ingnition. errormessage: Failed to run VM fcos34 (User: admin@internal-authz). with other templates (centos8) i have no problems. is there anything more todo before starting vm?

1 0

Re: Creating Snapshots failed
by Strahil Nikolov 02 Jun '21

02 Jun '21

I thought that I sent it to all, but I was wrong What is the output of ls -l /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/images/ad23c0db-1838-4f1f-811b-2b213d3a11cd/15259a3b-1065-4fb7-bc3c-04c5f4e14479 ? Best Regards,Strahil Nikolov On Tue, Jun 1, 2021 at 9:49, Liran Rotenberg<lrotenbe(a)redhat.com> wrote: On Mon, May 31, 2021 at 7:08 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > This stale file handle can happen when there is a gfid mismatch between bricks causing a some kind of splitbrain. > > > ls -l /rhev/data-center/mnt/glusterSD/onode1.example.org:_vmstore/3cf83851-1cc8-4f97-8960-08a60b9e25db/images/ad23c0db-1838-4f1f-811b-2b213d3a11cd/15259a3b-1065-4fb7-bc3c-04c5f4e14479 could show the file status. Hi Strahil, Can you respond to the thread? Luckily for me, I don't deal with glusterFS so much :) > > Best Regards, > Strahil Nikolov > > On Mon, May 31, 2021 at 10:46, Liran Rotenberg > <lrotenbe(a)redhat.com> 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/4UV524PGGZEEF…

3 7

Cannot add new host to Ovirt
by pablo＠miami.edu 02 Jun '21

02 Jun '21

I have an Ovirt installation with a hosted engine and three hosts. Using Gluster as the storage for the VMs. Ovirt: 4.4.6.7 Hosts: CentOS Stream release 8 (updated to latest) So far so good. I am trying to add a new host to the cluster with the same OS and hardware as the others and I cannot get it to install, it gives me all kind of errors and it will not install. I reinstalled the OS and I am getting the same results. DNS is configured properly and working ok for all hosts. I can see this error in this log file ansible-runner-service.log: 2021-05-30 15:46:38,319 - runner_service.services.hosts - ERROR - SSH - NOAUTH:SSH auth error - passwordless ssh not configured for 'ovirt4' (sshd is configured exactly the same as all other hosts and I can login to this host without a password from the ovirt hosted engine) I see these errors in the log engine.log: 2021-05-30 16:22:35,166Z ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 2021-05-30 16:22:35,175Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt4.net.miami.edu command Get Host Capabilities failed: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 2021-05-30 16:22:35,175Z ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target 2021-05-30 16:22:35,597Z ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-23) [] Error while refreshing server data for cluster 'Default' from database: null I tried reinstalling, rebooting, put it in maintenance, enroll the certificate, check for Upgrades, rebooted multiple times both the hosts and the ovirt engine: nothing works. What am I doing wrong? Thank you in advance for your help.

2 2

(no subject)
by david 02 Jun '21

02 Jun '21

hi i have a 4.4 ovirt cluster with a sigle server in it the emulated chipset in this cluster is q35 i need to change emulated chipset from q35 to i440fx to add a new host that don't support the q35 chipset type how it will affect on vm's that are running on ovirt 4.4 cluster ? what does this change process look like, how can i do it correctly?

1 0

The self-hosted engine upgraded to 4.4.6 was not Stream 8.
by mail＠chattytak.com 01 Jun '21

01 Jun '21

I upgraded. The upgrade seems to have been successful. However, the distribution OS of the self-hosted engine did not change. # cat /etc/system-release CentOS Linux release 8.3.2011 Do I need to manually change my self-hosted engine distribution to Stream 8? I saw this URL for the version upgrade procedure. https://www.ovirt.org/documentation/upgrade_guide/index.html#Updates_betwee…

3 5

can't login
by raymond.schilperoort＠ziggo.nl 01 Jun '21

01 Jun '21

Hello everyone, I installed ovirt yesterday, everything went well. Now I want to log in to :9090 I use the same as my login details because it says Log in with your server user account. However, no matter what I do, all I get is the message can't log in. Is there a way via ssh to change a password?

2 2

OSError: [Errno 24] Too many open files
by lejeczek 31 May '21

31 May '21

Hi guys I'm trying to install HE on a KVM host and installer cannot get pass this: [ ERROR ] OSError: [Errno 24] Too many open files [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this. Please add this host's fingerprint to your known_hosts file to manage this host."} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up KVM itself should be satisfying in terms of requirements, as a setup of a HE version from 'master' repo worked previously on it. Any ideas & thoughts shared, on what is that cryptic error message saying and how to troubleshoot I'll very much appreciate. many thanks, L.

2 5

Error while deploying Hyperconverged oVirt 4.3.3(el7) + GlusterFS
by techbreak＠icloud.com 31 May '21

31 May '21

As title, we want to use 3 hosts with hyperconverged solution of oVirt. We installed oVirt and Gluster as reported in the guide https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_H… When we try to deploy, we get some errors which we cannot figure out. ============================================================== gdeploy creates as configuration rules: hc_nodes: hosts: virtnodetest-0-0: gluster_infra_volume_groups: - vgname: gluster_vg_sdb pvname: /dev/sdb gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_sdb - path: /gluster_bricks/isostorage lvname: gluster_lv_isostorage vgname: gluster_vg_sdb - path: /gluster_bricks/vmstorage lvname: gluster_lv_vmstorage vgname: gluster_vg_sdb gluster_infra_thick_lvs: - vgname: gluster_vg_sdb lvname: gluster_lv_engine size: 150G gluster_infra_thinpools: - vgname: gluster_vg_sdb thinpoolname: gluster_thinpool_gluster_vg_sdb poolmetadatasize: 16G gluster_infra_lv_logicalvols: - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_isostorage lvsize: 250G - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_vmstorage lvsize: 3500G virtnodetest-0-1: gluster_infra_volume_groups: - vgname: gluster_vg_sdb pvname: /dev/sdb gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_sdb - path: /gluster_bricks/isostorage lvname: gluster_lv_isostorage vgname: gluster_vg_sdb - path: /gluster_bricks/vmstorage lvname: gluster_lv_vmstorage vgname: gluster_vg_sdb gluster_infra_thick_lvs: - vgname: gluster_vg_sdb lvname: gluster_lv_engine size: 150G gluster_infra_thinpools: - vgname: gluster_vg_sdb thinpoolname: gluster_thinpool_gluster_vg_sdb poolmetadatasize: 16G gluster_infra_lv_logicalvols: - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_isostorage lvsize: 250G - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_vmstorage lvsize: 3500G virtnodetest-0-2: gluster_infra_volume_groups: - vgname: gluster_vg_sdb pvname: /dev/sdb gluster_infra_mount_devices: - path: /gluster_bricks/engine lvname: gluster_lv_engine vgname: gluster_vg_sdb - path: /gluster_bricks/isostorage lvname: gluster_lv_isostorage vgname: gluster_vg_sdb - path: /gluster_bricks/vmstorage lvname: gluster_lv_vmstorage vgname: gluster_vg_sdb gluster_infra_thick_lvs: - vgname: gluster_vg_sdb lvname: gluster_lv_engine size: 150G gluster_infra_thinpools: - vgname: gluster_vg_sdb thinpoolname: gluster_thinpool_gluster_vg_sdb poolmetadatasize: 16G gluster_infra_lv_logicalvols: - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_isostorage lvsize: 250G - vgname: gluster_vg_sdb thinpool: gluster_thinpool_gluster_vg_sdb lvname: gluster_lv_vmstorage lvsize: 3500G vars: gluster_infra_disktype: JBOD gluster_set_selinux_labels: true gluster_infra_fw_ports: - 2049/tcp - 54321/tcp - 5900/tcp - 5900-6923/tcp - 5666/tcp - 16514/tcp gluster_infra_fw_permanent: true gluster_infra_fw_state: enabled gluster_infra_fw_zone: public gluster_infra_fw_services: - glusterfs gluster_features_force_varlogsizecheck: false cluster_nodes: - virtnodetest-0-0 - virtnodetest-0-1 - virtnodetest-0-2 gluster_features_hci_cluster: '{{ cluster_nodes }}' gluster_features_hci_volumes: - volname: engine brick: /gluster_bricks/engine/engine arbiter: 0 - volname: isostorage brick: /gluster_bricks/isostorage/isostorage arbiter: 0 - volname: vmstorage brick: /gluster_bricks/vmstorage/vmstorage arbiter: 0 ========================================================================= The system returns this error: PLAY [Setup backend] *********************************************************** TASK [Gathering Facts] ********************************************************* ok: [virtnodetest-0-2] ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] TASK [Check if valid hostnames are provided] *********************************** changed: [virtnodetest-0-1] => (item=virtnodetest-0-1) changed: [virtnodetest-0-1] => (item=virtnodetest-0-0) changed: [virtnodetest-0-1] => (item=virtnodetest-0-2) TASK [Check if provided hostnames are valid] *********************************** ok: [virtnodetest-0-1] => { "changed": false, "msg": "All assertions passed" } ok: [virtnodetest-0-0] => { "changed": false, "msg": "All assertions passed" } ok: [virtnodetest-0-2] => { "changed": false, "msg": "All assertions passed" } TASK [Check if /var/log has enough disk space] ********************************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [Check if the /var is greater than 15G] *********************************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [Check if disks have logical block size of 512B] ************************** skipping: [virtnodetest-0-1] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-0] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-2] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) TASK [Check if logical block size is 512 bytes] ******************************** skipping: [virtnodetest-0-1] => (item=Logical Block Size) skipping: [virtnodetest-0-0] => (item=Logical Block Size) skipping: [virtnodetest-0-2] => (item=Logical Block Size) TASK [Get logical block size of VDO devices] *********************************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [Check if logical block size is 512 bytes for VDO devices] **************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/firewall_config : Start firewalld if not already started] *** ok: [virtnodetest-0-2] ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] TASK [gluster.infra/roles/firewall_config : check if required variables are set] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/firewall_config : Open/Close firewalld ports] ******** ok: [virtnodetest-0-2] => (item=2049/tcp) ok: [virtnodetest-0-1] => (item=2049/tcp) ok: [virtnodetest-0-0] => (item=2049/tcp) ok: [virtnodetest-0-2] => (item=54321/tcp) ok: [virtnodetest-0-0] => (item=54321/tcp) ok: [virtnodetest-0-1] => (item=54321/tcp) ok: [virtnodetest-0-2] => (item=5900/tcp) ok: [virtnodetest-0-1] => (item=5900/tcp) ok: [virtnodetest-0-0] => (item=5900/tcp) ok: [virtnodetest-0-2] => (item=5900-6923/tcp) ok: [virtnodetest-0-0] => (item=5900-6923/tcp) ok: [virtnodetest-0-1] => (item=5900-6923/tcp) ok: [virtnodetest-0-2] => (item=5666/tcp) ok: [virtnodetest-0-1] => (item=5666/tcp) ok: [virtnodetest-0-0] => (item=5666/tcp) ok: [virtnodetest-0-2] => (item=16514/tcp) ok: [virtnodetest-0-1] => (item=16514/tcp) ok: [virtnodetest-0-0] => (item=16514/tcp) TASK [gluster.infra/roles/firewall_config : Add/Delete services to firewalld rules] *** ok: [virtnodetest-0-1] => (item=glusterfs) ok: [virtnodetest-0-0] => (item=glusterfs) ok: [virtnodetest-0-2] => (item=glusterfs) TASK [gluster.infra/roles/backend_setup : Check if vdsm-python package is installed or not] *** changed: [virtnodetest-0-2] changed: [virtnodetest-0-1] changed: [virtnodetest-0-0] TASK [gluster.infra/roles/backend_setup : Remove the existing LVM filter] ****** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check that the multipath.conf exists] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Ensure that multipathd services is enabled if not] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Ensure that multipathd services is running] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create /etc/multipath/conf.d if doesn't exists] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Get the UUID of the devices] ********* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check that the blacklist.conf exists] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create blacklist template content] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Add wwid to blacklist in blacklist.conf file] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Reload multipathd] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Gather facts to determine the OS distribution] *** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for debian systems.] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for RHEL systems.] *** ok: [virtnodetest-0-2] ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] TASK [gluster.infra/roles/backend_setup : Install python-yaml package for Debian systems] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Initialize vdo_devs array] *********** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Record VDO devices (if any)] ********* skipping: [virtnodetest-0-1] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-0] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) skipping: [virtnodetest-0-2] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) TASK [gluster.infra/roles/backend_setup : Configure lvm thinpool extend threshold] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Configure lvm thinpool extend percentage] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if vdo block device exists] **** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Record for missing devices for phase 2] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : set fact if it will at least install 1 vdo device] *** TASK [gluster.infra/roles/backend_setup : Install VDO dependencies] ************ skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : set fact about vdo installed deps] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Enable and start vdo service] ******** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create VDO with specified size] ****** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set VDO maxDiscardSize as 16M] ******* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Stop VDO volumes] ******************** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Start VDO volumes] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if valid disktype is provided] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for JBOD] ****** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for RAID] ****** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Set VG physical extent size for RAID] *** skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : include_tasks] *********************** included: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/get_vg_groupings.yml for virtnodetest-0-1, virtnodetest-0-0, virtnodetest-0-2 TASK [gluster.infra/roles/backend_setup : Group devices by volume group name, including existing devices] *** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if vg block device exists] ***** changed: [virtnodetest-0-0] => (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) changed: [virtnodetest-0-1] => (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) changed: [virtnodetest-0-2] => (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) TASK [gluster.infra/roles/backend_setup : Filter none-existing devices] ******** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Record for missing devices for phase 2] *** ok: [virtnodetest-0-1] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:18:33.575598', u'stderr': u'', u'stdout': u'0', u'changed': True, u'failed': False, u'delta': u'0:00:00.009901', u'cmd': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'item': {u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}], u'key': u'gluster_vg_sdb'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'0'], u'start': u'2021-05-13 12:18:33.565697'}) ok: [virtnodetest-0-0] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 10:52:56.886693', u'stderr': u'', u'stdout': u'0', u'changed': True, u'failed': False, u'delta': u'0:00:00.008123', u'cmd': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'item': {u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}], u'key': u'gluster_vg_sdb'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'0'], u'start': u'2021-05-13 10:52:56.878570'}) ok: [virtnodetest-0-2] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:25:24.420710', u'stderr': u'', u'stdout': u'0', u'changed': True, u'failed': False, u'delta': u'0:00:00.007307', u'cmd': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'item': {u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}], u'key': u'gluster_vg_sdb'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' test -b /dev/sdb && echo "1" || echo "0"; \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'0'], u'start': u'2021-05-13 12:25:24.413403'}) TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** skipping: [virtnodetest-0-1] => (item={u'key': u'gluster_vg_sdb', u'value': []}) skipping: [virtnodetest-0-0] => (item={u'key': u'gluster_vg_sdb', u'value': []}) skipping: [virtnodetest-0-2] => (item={u'key': u'gluster_vg_sdb', u'value': []}) TASK [gluster.infra/roles/backend_setup : update LVM fact's] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if thick-lv block devices exists] *** changed: [virtnodetest-0-0] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) changed: [virtnodetest-0-1] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) changed: [virtnodetest-0-2] => (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) TASK [gluster.infra/roles/backend_setup : Record for missing devices for phase 2] *** skipping: [virtnodetest-0-1] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:18:37.528159', u'stderr': u'', u'stdout': u'1', u'changed': True, u'failed': False, u'delta': u'0:00:00.010032', u'cmd': u' echo "1" \n', u'item': {u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' echo "1" \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'1'], u'start': u'2021-05-13 12:18:37.518127'}) skipping: [virtnodetest-0-0] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 10:53:00.863436', u'stderr': u'', u'stdout': u'1', u'changed': True, u'failed': False, u'delta': u'0:00:00.007459', u'cmd': u' echo "1" \n', u'item': {u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' echo "1" \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'1'], u'start': u'2021-05-13 10:53:00.855977'}) skipping: [virtnodetest-0-2] => (item={u'stderr_lines': [], u'ansible_loop_var': u'item', u'end': u'2021-05-13 12:25:28.261106', u'stderr': u'', u'stdout': u'1', u'changed': True, u'failed': False, u'delta': u'0:00:00.007818', u'cmd': u' echo "1" \n', u'item': {u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}, u'rc': 0, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'strip_empty_ends': True, u'_raw_params': u' echo "1" \n', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin_add_newline': True, u'stdin': None}}, u'stdout_lines': [u'1'], u'start': u'2021-05-13 12:25:28.253288'}) TASK [gluster.infra/roles/backend_setup : include_tasks] *********************** included: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/get_vg_groupings.yml for virtnodetest-0-1, virtnodetest-0-0, virtnodetest-0-2 TASK [gluster.infra/roles/backend_setup : Group devices by volume group name, including existing devices] *** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Check if vg block device exists] ***** TASK [gluster.infra/roles/backend_setup : Filter none-existing devices] ******** ok: [virtnodetest-0-1] ok: [virtnodetest-0-0] ok: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Make sure thick pvs exists in volume group] *** TASK [gluster.infra/roles/backend_setup : update LVM fact's] ******************* skipping: [virtnodetest-0-1] skipping: [virtnodetest-0-0] skipping: [virtnodetest-0-2] TASK [gluster.infra/roles/backend_setup : Create thick logical volume] ********* failed: [virtnodetest-0-1] (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " WARNING: Device for PV gx6iUE-369Z-3FDP-aRUQ-Wur0-1Xhf-v4g79j not found or rejected by a filter.\n Volume group \"gluster_vg_sdb\" not found\n Cannot process volume group gluster_vg_sdb\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "150G", "vgname": "gluster_vg_sdb"}, "msg": "Volume group gluster_vg_sdb does not exist.", "rc": 5} failed: [virtnodetest-0-0] (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_sdb\" not found\n Cannot process volume group gluster_vg_sdb\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "150G", "vgname": "gluster_vg_sdb"}, "msg": "Volume group gluster_vg_sdb does not exist.", "rc": 5} failed: [virtnodetest-0-2] (item={u'lvname': u'gluster_lv_engine', u'vgname': u'gluster_vg_sdb', u'size': u'150G'}) => {"ansible_index_var": "index", "ansible_loop_var": "item", "changed": false, "err": " Volume group \"gluster_vg_sdb\" not found\n Cannot process volume group gluster_vg_sdb\n", "index": 0, "item": {"lvname": "gluster_lv_engine", "size": "150G", "vgname": "gluster_vg_sdb"}, "msg": "Volume group gluster_vg_sdb does not exist.", "rc": 5} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* virtnodetest-0-0 : ok=19 changed=3 unreachable=0 failed=1 skipped=41 rescued=0 ignored=0 virtnodetest-0-1 : ok=20 changed=4 unreachable=0 failed=1 skipped=41 rescued=0 ignored=0 virtnodetest-0-2 : ok=19 changed=3 unreachable=0 failed=1 skipped=41 rescued=0 ignored=0 Please check /var/log/cockpit/ovirt-dashboard/gluster-deployment.log for more informations. ====================================================================== How can we resolve this issue?

4 7

Creating Snapshots failed
by jb 31 May '21

31 May '21

Hello Community, since I upgrade our cluster to ovirt 4.4.6.8-1.el8 I'm not able anymore to create snapshots on certain VMs. For example I have two debian 10 VMs, from one I can make a snapshot, and from other one not. Both are up to date and uses the same qemu-guest-agent versions. I tried to create snapshots over API and on web gui, both gives the same result. In the attachment you found a snipped from the engine.log. Any help would be wonderful! Regards, Jonathan

2 3

oVirt 2021 Spring survey responses are now available
by Sandro Bonazzola 31 May '21

31 May '21

Thanks to the 133 participants in the oVirt 2021 Spring survey! The survey is now over and results are publicly available at [1]. [1] https://docs.google.com/forms/d/1RcSzRQ2YmB2U3MNlWk0YqTVFdGYIdguk46K2A-DZEv… -- 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 1

Where to get the vm config file ?
by tommy 28 May '21

28 May '21

Thanks.

3 2

After upgrade only 1/3 hosts is running Node 4.4.6
by Jayme 28 May '21

28 May '21

I updated my three server HCI cluster from 4.4.5 to 4.4.6. All hosts updated successfully and rebooted and are active. I notice that only one host out of the three is actually running oVirt node 4.4.6 and the other two are running 4.4.5. If I check for upgrade in admin it shows no upgrades available. Why are two hosts still running 4.4.5 after being successfully upgraded/rebooted and how can I get them on 4.4.6 if no upgrades are being found?

2 6

[ANN] oVirt 4.4.7 First Release Candidate is now available for testing
by Lev Veyde 28 May '21

28 May '21

oVirt 4.4.7 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 First Release Candidate for testing, as of May 27th, 2021. This update is the seventh 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.7 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.7 (redeploy in case of already being on 4.4.7). 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.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.7 release highlights: http://www.ovirt.org/release/4.4.7/ * 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.7/ [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>

1 0

unable to login cockpit using root after upgrading to 4.4.6
by dhanaraj.ramesh＠yahoo.com 28 May '21

28 May '21

Hi Team, after upgrading ovirt node from 4.4.5 to 4.4.6, unale to login to the cockpit using root, but could able to login via ssh. please check whether this is considered as bug

13 21

CPU usage question
by David Johnson 28 May '21

28 May '21

Hi everyone, I am slowly working the performance bottlenecks out of my rack, and ran into this puzzling scenario. Ovirt shows CPU usage at over 50%. Windows shows CPU usage between 5 and 15 % The backing store is TrueNAS NFS on a 10 GBit lan. I am seeing just under 1 GBit throughput on the storage network for this operation (create database). Am I reading this correctly that my system is bottlenecking on the CPU used to handle the Windows disk IO over TCP/IP ? Thanks *David Johnson* Screenshot of pertinent metrics: [image: image.png] <https://www.linkedin.com/in/pojoguy/> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson.v…> <https://maxistechnology.com/> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>

2 1

Unable to migrate VMs
by Jayme 27 May '21

27 May '21

I have a three node oVirt 4.4.5 cluster running oVirt node hosts. Storage is mix of GlusterFS and NFS. Everything has been running smoothly, but the other day I noticed many VMs had invalid snapshots. I run a script to export OVA for VMs for backup purposes, exports seemed to have been fine but snapshots failed to delete at the end. I was able to manually delete the snapshots through oVirt admin GUI without any errors/warnings and the VMs have been running fine and can restart them without problems. I thought this problem may be due to snapshot bug which is supposedly fixed in oVirt 4.4.6. I decided to start upgrading cluster to 4.4.6 and am now having a problem with VMs not being able to migrate. When I migrate any VM (doesn't seem to matter which host to and from) the process starts but stops at 0-1%. Eventually after 15-30 minutes or more the tasks are all completed by the VM is not migrated. I am unable to migrate any VMs and as such I cannot place any host in maintenance mode. I've attaching some VDSM logs from source and destination hosts, these were after initiating a migration of a single VM I'm seeing some errors in the logs regarding the migration stalling, but not able to determine why its stalling. 2021-05-27 17:10:22,167+0000 INFO (jsonrpc/4) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme1n1/bce04425-1d25-4489-bdab-2834a1a57db8/images/38b27cce-c744-4a12-85a3-3af07d386da2/93c1e793-f8cb-42c9-86a6-0e9ce4a6023a', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '2b87204f-f695-474a-9f08-47b85fcac366': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/f2e0c9f3-ab0d-441a-85a6-07a42e78b5a8/848f353e-6787-4e20-ab7b-0541ebd852c6', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '26332421-54a3-4afc-90e7-551a7e314c80': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/b7a785f9-307b-42af-9bbe-23cac884fe97/ed1d027e-a36a-4e6b-9207-119915044e06', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/535fcb2e-ece9-4d50-86fe-bf6264d11ae1/6c01a036-8a14-46ba-a4b4-fe4f66a586a3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/1f467fb5-5ea7-42ba-bace-f175c86791b2/cbe8327f-9b7f-442f-a650-6888bb11a674', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdd', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/c93956d5-c88d-41f9-8c38-9f5f62cc90dd/3920b46c-5fab-4b63-b47f-2fa5c6714c36', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, 'beeefe06-78a0-4e14-a932-cc8d734d542d': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/310d8b3e-d578-418d-9802-dc0ebcea06d6/aa758c51-8478-4273-aeef-d4b374b8d6b4', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/4072fda1-ec82-45c9-b353-91fceb13bf08/891f5982-dead-48b4-8907-caa1e309fa82', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '7e5156de-649d-4904-9092-21a699242a37': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/ca0c1208-a7aa-4ef6-a450-4a40bd4455f3/a2335199-ddd4-429b-b55d-f4d527081fd3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}}} from=::1,35012 (api:54) 2021-05-27 17:10:31,118+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:10:31,118+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 190.035 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814) 2021-05-27 17:10:33,827+0000 INFO (jsonrpc/5) [throttled] Current getAllVmStats: {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': 'Up', '2b87204f-f695-474a-9f08-47b85fcac366': 'Up', '26332421-54a3-4afc-90e7-551a7e314c80': 'Up', '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': 'Up', 'beeefe06-78a0-4e14-a932-cc8d734d542d': 'Up', '7e5156de-649d-4904-9092-21a699242a37': 'Migration Source'} (throttledlog:104) 2021-05-27 17:10:37,186+0000 INFO (jsonrpc/5) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme1n1/bce04425-1d25-4489-bdab-2834a1a57db8/images/38b27cce-c744-4a12-85a3-3af07d386da2/93c1e793-f8cb-42c9-86a6-0e9ce4a6023a', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '2b87204f-f695-474a-9f08-47b85fcac366': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/f2e0c9f3-ab0d-441a-85a6-07a42e78b5a8/848f353e-6787-4e20-ab7b-0541ebd852c6', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '26332421-54a3-4afc-90e7-551a7e314c80': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/b7a785f9-307b-42af-9bbe-23cac884fe97/ed1d027e-a36a-4e6b-9207-119915044e06', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/535fcb2e-ece9-4d50-86fe-bf6264d11ae1/6c01a036-8a14-46ba-a4b4-fe4f66a586a3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/1f467fb5-5ea7-42ba-bace-f175c86791b2/cbe8327f-9b7f-442f-a650-6888bb11a674', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdd', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/c93956d5-c88d-41f9-8c38-9f5f62cc90dd/3920b46c-5fab-4b63-b47f-2fa5c6714c36', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, 'beeefe06-78a0-4e14-a932-cc8d734d542d': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/310d8b3e-d578-418d-9802-dc0ebcea06d6/aa758c51-8478-4273-aeef-d4b374b8d6b4', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/4072fda1-ec82-45c9-b353-91fceb13bf08/891f5982-dead-48b4-8907-caa1e309fa82', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '7e5156de-649d-4904-9092-21a699242a37': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/ca0c1208-a7aa-4ef6-a450-4a40bd4455f3/a2335199-ddd4-429b-b55d-f4d527081fd3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}}} from=::1,35012 (api:54) 2021-05-27 17:10:41,120+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:10:41,120+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 200.037 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814) 2021-05-27 17:10:51,121+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:10:51,121+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 210.039 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814) 2021-05-27 17:10:52,211+0000 INFO (jsonrpc/1) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'f8f4e4a1-b565-4663-8962-c8804dbb86fb': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme1n1/bce04425-1d25-4489-bdab-2834a1a57db8/images/38b27cce-c744-4a12-85a3-3af07d386da2/93c1e793-f8cb-42c9-86a6-0e9ce4a6023a', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '2b87204f-f695-474a-9f08-47b85fcac366': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/f2e0c9f3-ab0d-441a-85a6-07a42e78b5a8/848f353e-6787-4e20-ab7b-0541ebd852c6', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '26332421-54a3-4afc-90e7-551a7e314c80': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/b7a785f9-307b-42af-9bbe-23cac884fe97/ed1d027e-a36a-4e6b-9207-119915044e06', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '60edbd80-dad7-4bf8-8fd1-e138413cf9f6': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/535fcb2e-ece9-4d50-86fe-bf6264d11ae1/6c01a036-8a14-46ba-a4b4-fe4f66a586a3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/1f467fb5-5ea7-42ba-bace-f175c86791b2/cbe8327f-9b7f-442f-a650-6888bb11a674', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdd', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme2n1/a7efa448-201b-4453-9bc9-900559b891ca/images/c93956d5-c88d-41f9-8c38-9f5f62cc90dd/3920b46c-5fab-4b63-b47f-2fa5c6714c36', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, 'beeefe06-78a0-4e14-a932-cc8d734d542d': {'policy': [], 'current_values': [{'name': 'sda', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/310d8b3e-d578-418d-9802-dc0ebcea06d6/aa758c51-8478-4273-aeef-d4b374b8d6b4', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}, {'name': 'sdb', 'path': '/rhev/data-center/mnt/glusterSD/gluster0.grove.silverorange.com:_data__sdb/30fd0a2f-ab42-4a8a-8f0b-67242dc2d15d/images/4072fda1-ec82-45c9-b353-91fceb13bf08/891f5982-dead-48b4-8907-caa1e309fa82', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}, '7e5156de-649d-4904-9092-21a699242a37': {'policy': [], 'current_values': [{'name': 'vda', 'path': '/rhev/data-center/mnt/10.11.0.9:_vmstorage_nvme0n1/a99cd663-f6d5-42d8-bd7a-ee0b5d068608/images/ca0c1208-a7aa-4ef6-a450-4a40bd4455f3/a2335199-ddd4-429b-b55d-f4d527081fd3', 'ioTune': {'total_bytes_sec': 0, 'read_bytes_sec': 0, 'write_bytes_sec': 0, 'total_iops_sec': 0, 'write_iops_sec': 0, 'read_iops_sec': 0}}]}}} from=::1,35012 (api:54) 2021-05-27 17:11:01,123+0000 WARN (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration stalling: remaining (32863MiB) > lowmark (32863MiB). (migration:801) 2021-05-27 17:11:01,123+0000 INFO (migmon/7e5156de) [virt.vm] (vmId='7e5156de-649d-4904-9092-21a699242a37') Migration Progress: 220.041 seconds elapsed, 1% of data processed, total data: 32864MB, processed data: 0MB, remaining data: 32863MB, transfer speed 0Mbps, zero pages: 160MB, compressed: 0MB, dirty rate: 0, memory iteration: 1 (migration:814)ats return={'86245648-abd8-46e3-9c10-432e8788a074': {'code': 0, 'lastCheck': '1.6', 'delay': '0.00353497', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=::1,35010, task_id=c4e65f55-1367-41d3-9bf6-f357a382df4a (api:54) 2021-05-27 17:09:33,156+0000 INFO (jsonrpc/2) [api.host] START getStats() from=::ffff:10.11.0.219,54952 (api:48)

1 2