- Users - oVirt List Archives

VDSM host1/2/3 command GetStorageDeviceListVDS failed: Internal JSON-RPC error: {'reason': 'device is already in tree'}
by Radoslav Milanov 04 Jun '20

04 Jun '20

Hello I have oVirt 4.4 HCI/Gluster, 3 hosts and cluster is working but I'm getting those errors in log: VDSM host1/2/3 command GetStorageDeviceListVDS failed: Internal JSON-RPC error: {'reason': 'device is already in tree'} for all 3 hosts. Thank you.

3 3

[ANN] oVirt 4.4.1 Third Release Candidate is now available for testing
by Lev Veyde 04 Jun '20

04 Jun '20

oVirt 4.4.1 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.1 Third Release Candidate for testing, as of June 4th, 2020. This update is the first in a series of stabilization updates to the 4.4 series. 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. Some of the features included in oVirt 4.4.1 Release Candidate require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer * oVirt Node 4.4 based on CentOS Linux 8.1 (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 Additional Resources: * Read more about the oVirt 4.4.1 release highlights: http://www.ovirt.org/release/4.4.1/ * 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.1/ [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 [image: image.png] <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

VM login info
by fawzi＠kdsplumbing.com 03 Jun '20

03 Jun '20

Hi guys, After a lot of attempts, i was finally able to open a VM (centos8-cld) using virt-viewer on my mac (catalina). but i am faced with a login screen. So, where do i get this information from? or should i be using a different method to log into a vm? This goes for all of the VMs available by default. can someone please help me with this? thanks

2 1

4.4 regression: engine-setup fails if admin password in answerfile contains a "%"
by Stephen Panicho 03 Jun '20

03 Jun '20

I encountered this error when deploying the Hosted Engine via Cockpit: [ INFO ] TASK [ovirt.engine-setup : Run engine-setup with answerfile] [ ERROR ] fatal: [localhost -> engine.ovirt.trashnet.xyz]: FAILED! => {"changed": true, "cmd": ["engine-setup", "--accept-defaults", "--config-append=/root/ovirt-engine-answers"], "delta": "0:00:01.396490", "end": "2020-05-22 18:32:41.965984", "msg": "non-zero return code", "rc": 1, "start": "2020-05-22 18:32:40.569494", "stderr": "", "stderr_lines": [], "stdout": "[ INFO ] Stage: Initializing\n[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'\n[ INFO ] Stage: Clean up\n Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log\n[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'\n[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'\n[ INFO ] Stage: Pre-termination\n[ INFO ] Stage: Termination\n[ ERROR ] Execution of setup failed", "stdout_lines": ["[ INFO ] Stage: Initializing", "[ ERROR ] Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'", "[ INFO ] Stage: Clean up", " Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522183241-c7d1kh.log", "[ ERROR ] Failed to execute stage 'Clean up': 'NoneType' object has no attribute 'cleanup'", "[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522183241-setup.conf'", "[ INFO ] Stage: Pre-termination", "[ INFO ] Stage: Termination", "[ ERROR ] Execution of setup failed"]} The important bit is this: Failed to execute stage 'Initializing': '%' must be followed by '%' or '(', found: '%JUUj'" Hey! Those are the last few characters of the admin password. Note that I don't mean the root password to the VM, but the one for the "admin" user of the web interface. I added some debug lines to the Ansible play to see the answerfile that was being generated. OVESETUP_CONFIG/adminPassword=str:&6&yGfcWf#b%JUUj Apparently engine-setup can no longer handle an answerfile with a "%" character in it. This same password worked in 4.3. Once I changed the admin password, installation progressed normally.

5 14

[ANN] oVirt 4.3.10 is now generally available
by Lev Veyde 03 Jun '20

03 Jun '20

The oVirt Project is pleased to announce the general availability of oVirt 4.3.10 as of June 3rd, 2020. This update is the tenth in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.8 or later (but < 8) * CentOS Linux (or similar) 7.8 or later (but < 8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.8 or later (but < 8) * CentOS Linux (or similar) 7.8 or later (but < 8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance will be available soon - oVirt Node is already available[2] oVirt Node and Appliance have been updated including: - oVirt 4.3.10: http://www.ovirt.org/release/4.3.10/ - Latest CentOS 7.8 updates - latest CentOS Virt, OpsTools and Storage SIG updates Additional Resources: * Read more about the oVirt 4.3.10 release highlights: http://www.ovirt.org/release/4.3.10/ * 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.3.10/ [2] http://resources.ovirt.org/pub/ovirt-4.3/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

Import VM from export domain using oVirt-4.4
by Joop 03 Jun '20

03 Jun '20

Hi All, I'm testing a shiny new oVirt-4.4.02, selfhosted engine HCI gluster, and found a problem when importing my VMs from an export domain. Import is OK but can't start the VM due to the fact that the BIOS is set to Legacy. Manually setting the BIOS type to Cluster Default, through VM properties, will let the VM start. I couldn't find anything about it in the ReleaseNotes As a side note: using gluster still doesn't install gluster-ansible-roles and glusterfs-server and vdsm-gluster or checks for its existance. See also another user who reported problems due to the latter not being installed, had the same experience. Regards, Joop

1 0

Recuring error in the Administration Portal
by Krist van Besien 03 Jun '20

03 Jun '20

When using the Administration Portal after a while I start to get errors like this: 'Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'isEval' of undefined Please have your administrator check the UI logs' 'Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : null is not an object (evaluating 'b.b.b.a') Please have your administrator check the UI logs' These errors appear when I use Brave, but also appear after a while in Firefox, Chrome or Safari. The count listed in the upper right corner continuously increases if I do nothing. I find these errors in the ui.log as well: For example: 2020-06-03 11:10:01,113+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-83) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : null is not an object (evaluating 'b.b.b.a') at org.ovirt.engine.ui.webadmin.section.main.view.tab.gluster.SubTabVolumeGeneralView.$setMainSelectedItem(SubTabVolumeGeneralView.java:143) at org.ovirt.engine.ui.webadmin.section.main.view.tab.gluster.SubTabVolumeGeneralView.setMainSelectedItem(SubTabVolumeGeneralView.java:143) at org.ovirt.engine.ui.common.presenter.AbstractSubTabPresenter.$onDetailModelEntityChange(AbstractSubTabPresenter.java:368) at org.ovirt.engine.ui.common.presenter.AbstractSubTabPresenter.$lambda$6(AbstractSubTabPresenter.java:343) at org.ovirt.engine.ui.common.presenter.AbstractSubTabPresenter$lambda$6$Type.eventRaised(AbstractSubTabPresenter.java:343) at org.ovirt.engine.ui.uicompat.Event.$raise(Event.java:99) at org.ovirt.engine.ui.uicommonweb.models.EntityModel.$setEntity(EntityModel.java:36) at org.ovirt.engine.ui.uicommonweb.models.EntityModel.setEntity(EntityModel.java:36) at org.ovirt.engine.ui.uicommonweb.models.ListWithDetailsModel.$onSelectedItemChanged(ListWithDetailsModel.java:89) at org.ovirt.engine.ui.uicommonweb.models.volumes.VolumeListModel.onSelectedItemChanged(VolumeListModel.java:455) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.$setItems(SearchableListModel.java:714) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.setItems(SearchableListModel.java:714) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel$SetItemsAsyncQuery$1.$onSuccess(SearchableListModel.java:878) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel$SetItemsAsyncQuery$1.onSuccess(SearchableListModel.java:878) at org.ovirt.engine.ui.frontend.Frontend$1.$onSuccess(Frontend.java:227) at org.ovirt.engine.ui.frontend.Frontend$1.onSuccess(Frontend.java:227) at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.$onSuccess(OperationProcessor.java:133) at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.onSuccess(OperationProcessor.java:133) at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.$onSuccess(GWTRPCCommunicationProvider.java:270) at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onSuccess(GWTRPCCommunicationProvider.java:270) at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) at Unknown.anonymous(https://ov.wl.kri.st/ovirt-engine/webadmin/?locale=en_US) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:275) at Unknown.anonymous(https://ov.wl.kri.st/ovirt-engine/webadmin/?locale=en_US) It is always org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService, and the errors run in the hundreds... What is going on? A bug? A misconfiguration? Database corruption? This is an ovirt 4.4 cluster I setup on Centos 8. The cluster uses gluster storage, and was setup only a few days ago.

1 0

Re: VM Networking
by Dominik Holler 02 Jun '20

02 Jun '20

On Tue, Jun 2, 2020 at 3:34 PM Anton Louw via Users <users(a)ovirt.org> wrote: > > > Hi Everybody, > > > > I had a strange incident today.. One of my nodes restarted (Still busy > investigating why), but my VMs powered own and moved to different nodes, > the only issue is, it seemed to have changed the vlan ID on the NICs? > Which VLANs changed during the reboot of the host? Just the VLANs on the hosts NICs, in a way the VMs are still connected to the correct VLANs? > Has anybody seen this before? > It is possible to run a network configuration, which does not persist and is reverted during reboot this way. Please find more details in http://ovirt.github.io/ovirt-engine-api-model/master/#services/host/methods… or the "Save network configuration" checkbox in the "Setup Host Networks" dialog. In recent oVirt versions this checkbox cannot be unselected anymore to avoid unexpected situations. > I am just trying to establish if this was changed on the node networking > side, or inside of the VM. > > > If a virtual NIC is connected to a logical network with a VLAN tag, there is no intended way for the VM to modify this tag. > Thank you > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: image.png] > > > > > > > > <https://www.facebook.com/voxtelecomZA> > > [image: image.png] > > > > > > > > <https://www.twitter.com/voxtelecom> > > [image: image.png] > > > > > > > > <https://www.instagram.com/voxtelecomza/> > > [image: image.png] > > > > > > > > <https://www.linkedin.com/company/voxtelecom> > > [image: image.png] > > > > > > > > <https://www.youtube.com/user/VoxTelecom> > > [image: image.png] > > > > > > > > <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > *Disclaimer* > > The contents of this email are confidential to the sender and the intended > recipient. Unless the contents are clearly and entirely of a personal > nature, they are subject to copyright in favour of the holding company of > the Vox group of companies. Any recipient who receives this email in error > should immediately report the error to the sender and permanently delete > this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been > automatically archived by *Mimecast Ltd*, an innovator in Software as a > Service (SaaS) for business. Providing a *safer* and *more useful* place > for your human generated data. Specializing in; Security, archiving and > compliance. To find out more Click Here > <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > > _______________________________________________ > 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/CP7GZUPSI7MDB… >

1 0

VM Networking
by Anton Louw 02 Jun '20

02 Jun '20

Hi Everybody, I had a strange incident today.. One of my nodes restarted (Still busy investigating why), but my VMs powered own and moved to different nodes, the only issue is, it seemed to have changed the vlan ID on the NICs? Has anybody seen this before? I am just trying to establish if this was changed on the node networking side, or inside of the VM. Thank you Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

1 0

Problem with oVirt 4.4
by minnie.du＠vinchin.com 02 Jun '20

02 Jun '20

Hello, We have met a problem when testing oVirt 4.4. Our VM is on NFS storage. When testing the snapshot function of oVirt 4.4, we created snapshot 1 and then snapshot 2, but after clicking the delete button of snapshot 1, snapshot 1 failed to be deleted and the state of corresponding disk became illegal. Removing the snapshot in this state requires a lot of risky work in the background, leading to the inability to free up snapshot space. Long-term backups will cause the target VM to create a large number of unrecoverable snapshots, thus taking up a large amount of production storage. So we need your help.

2 1