- Users - oVirt List Archives

access engine by http
by du_hongyu＠yeah.net 16 Feb '19

16 Feb '19

I want to access engine by http， after engine-setup success， I fix /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf ENGINE_FQDN=localhost.localdomain ENGINE_PROXY_ENABLED=false ENGINE_PROXY_HTTP_PORT=None ENGINE_PROXY_HTTPS_PORT=None ENGINE_AJP_ENABLED=false ENGINE_AJP_PORT=None ENGINE_HTTP_ENABLED=true ENGINE_HTTPS_ENABLED=false ENGINE_HTTP_PORT=8080 ENGINE_HTTPS_PORT=443 but I access http://ip:8080/ovirt-engine , still browser is redirect to https, I should how to disable redirect? Regards Hongyu Du

3 11

ovirt-4.3 hyperconverged deployment - no option for "disc count" for JBOD
by feral 16 Feb '19

16 Feb '19

Vanilla install of ovirt-node-4.3 (iso). During hyperconverged wizard, there is no option for disc count for JBOD. This results in error during deployment. Disc Count option is available for all other raid levels. -- _____ Fact: 1. Ninjas are mammals. 2. Ninjas fight ALL the time. 3. The purpose of the ninja is to flip out and kill people.

5 12

Upgrade from 4.2.7 to 4.3.0 troubles
by mariani.alberto＠libero.it 15 Feb '19

15 Feb '19

Hello All, I'm trying to upgrade a Self Hosted Engine installation from 4.2.7 to 4.3.0. I was able to update the Engine itself, but when I try the general update for both the Engine VM and the Self Hosted Nodes the update fails because the openvswitch-ovn-* packages want a long series of libraries as dependencies, all with the name librte_* Unfortunately, I don't think these exist in CentOs 7, so I'm having no luck in finding them. Am I doing something wrong? Best Regards, Alberto M.

3 4

Error packages update after upgrade to ovirt 4.3
by Нон локалес 15 Feb '19

15 Feb '19

Hello. Anyone please help, cannot upgrade host, yum update going in error. https://pastebin.com/MWnsxVAa What i have done and didnt work: yum install dpdk yum clean all package-cleanup --cleandupes Its clean centos 7 with installed host role throught ovirt engine/

3 2

Vnic-Port mirroring
by ada per 15 Feb '19

15 Feb '19

Hello everyone, I am trying to allow port mirroring through the Vnic profile but no matter what i do it stays grayed out. How can i enable this option? When i am creating a new VNIC profile the options ,port mirroring and passthrough are disabled. the version i am using is 4.2.8. Thanks!:)

4 11

Re: Ovirt Cluster completely unstable
by Ryan Bullock 15 Feb '19

15 Feb '19

Just to add, after we updated to 4.3 our gluster just went south. Thankfully gluster is only secondary storage for us, and our primary storage is an ISCSI SAN. We migrated everything over to the SAN that we could, but a few VM's got corrupted by gluster (data was gone). Right now we just have gluster off and set to maintenance because the connectivity issues were causing our main cluster to continuously migrate VMs. Looking at the gluster hosts themselves I noticed that heal info would often report one brick down, even if ovirt didn't. Checking the status of glusterd would also show health checks failed. Feb 6 15:36:37 vmc3h1 glusterfs-virtstore[17036]: [2019-02-06 23:36:37.937041] M [MSGID: 113075] [posix-helpers.c:1957:posix_health_check_thread_proc] 0-VirstStore-posix: health-check failed, going down Feb 6 15:36:37 vmc3h1 glusterfs-virtstore[17036]: [2019-02-06 23:36:37.937561] M [MSGID: 113075] [posix-helpers.c:1975:posix_health_check_thread_proc] 0-VirstStore-posix: still alive! -> SIGTERM I think the health-check is failing (maybe erroneously) which is then killing the brick. When this happens it just causing a continuous cycle of brick up-down and healing, and in turn connectivity issues. This is our second time running into issues with gluster, so I think we are going to sideline it for awhile. -Ryan On Thu, Feb 14, 2019 at 12:47 PM Darryl Scott <dscott(a)umbctraining.com> wrote: > I do believe something went wrong after fully updating everything last > Friday. I updated all the ovirt compute nodes on Friday and gluster/engine > on Saturday. I have been experiencing these issues every since. I have > pour over engine.log and seems to be connection to storage issue. > > > ------------------------------ > *From:* Jayme <jaymef(a)gmail.com> > *Sent:* Thursday, February 14, 2019 1:52:59 AM > *To:* Darryl Scott > *Cc:* users > *Subject:* Re: [ovirt-users] Ovirt Cluster completely unstable > > I have a three node HCI gluster which was previously running 4.2 with zero > problems. I just upgraded it yesterday. I ran in to a few bugs right away > with the upgrade process, but aside from that I also discovered other users > with severe GlusterFS problems since the upgrade to new GlusterFS version. > It is less than 24 hours since I upgrade my cluster and I just got a notice > that one of my GlusterFS bricks is offline. There does appear to be a very > real and serious issue here with the latest updates. > > > On Wed, Feb 13, 2019 at 7:26 PM <dscott(a)umbctraining.com> wrote: > > I'm abandoning my production ovirt cluster due to instability. I have a > 7 host cluster running about 300 vms and have been for over a year. It has > become unstable over the past three days. I have random hosts both, > compute and storage disconnecting. AND many vms disconnecting and becoming > unusable. > > 7 host are 4 compute hosts running Ovirt 4.2.8 and three glusterfs hosts > running 3.12.5. I submitted a bugzilla bug and they immediately assigned > it to the storage people but have not responded with any meaningful > information. I have submitted several logs. > > I have found some discussion on problems with instability with gluster > 3.12.5. I would be willing to upgrade my gluster to a more stable version > if that's the culprit. I installed gluster using the ovirt gui and this is > the version the ovirt gui installed. > > Is there an ovirt health monitor available? Where should I be looking to > get a resolution the problems I'm facing. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/BL4M3JQA3IEXC… > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/IMUKFFANNJXLK… >

1 0

Using the web-ui VM portal through a proxy failing
by Callum Smith 15 Feb '19

15 Feb '19

Dear oVirt Gurus, Using the oVirt user VM portal seems to not work through the squid proxy setup (configured as per the guide). The page loads and login works fine through the proxy, but the asynchronous requests just hang. I've attached a screenshot, but you can see the "api" endpoint just hanging in a web inspector: "https://proxyfqdn/ovirt-engine/api/" [cid:CA42E493-3AD9-45F8-B4C3-C914F059390C@well.ox.ac.uk] This works fine when not going through the proxy. Is there a way to force noVNC HTML as the console mode through the web-ui, or at least have it as an option if not default? The console seems not to work when logged in with a base 'user role'. Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

2 14

Create Snapshots on Windows 7 Pro x64 VM's causes Bootload errors
by robertodg＠prismatelecomtesting.com 15 Feb '19

15 Feb '19

Hello everyone, on Ovirt 4.2.6.4-1.el7, when we try to create a snapshot on Windows 7 Pro x64 (regardless of whether the VM is powered off or not) after several reboots it causes bootload errors (below you'll find a link with screenshoot error). https://ibb.co/tKx6SKw We haven't tried other Windows versions yet, do you have any idea about what the cause might be? Thanks in advance.

2 1

Ovirt self-hosted engine won't come up
by joshuaosko＠gmail.com 14 Feb '19

14 Feb '19

The self-hosted engine had an issue whereby it'd /var partition was full. A few days later the engine was rebooted; however, it did not come back up gracefully. I presently have three CentOS 7 hosts which can spin up a new hosted engine vm; however every attempt to do so results in: Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} The VM is not "up" as it does not even respond to ping, let alone having any ability to ssh or console into it to see what's wrong. All of the VMs that have been built using this engine appear to be fully operational. Is there any guidance anyone can give me? At this point I'm wondering what the consequences are to deploying a new hosted engine within that same cluster. If anyone could shed light on this matter it would be tremendously appreciated! Thanks.

3 10

please help with console issues on vGPU enabled VMs.
by Edward Berger 14 Feb '19

14 Feb '19

We are attempting to get vGPU-enabled guests working with our oVirt 4.3.0 configuration, but have run into problems. We are running: NVidia License Server version 2018.09 NVidia License Client Manager 2018.10.0.25098346 and that license info is correctly retrieved by the clients. With a Centos 7.6 guest, we can ssh into the guest and see that the X server is running and a gdm process is also running, but when we open a remote console viewer, all we get is a black screen. The X server reports the correct vGPU profile. The only error we see in the Xorg.0.log file is: [ 5.176] (EE) NVIDIA(GPU-0): Failed to update the GLS device with FRL configuration but that is not fatal. With a Windows 10 guest, we do get a login screen to appear, but the mouse and keyboard do not seem to be functional. Host configuration: host is running oVirt-node 4.3.0 NVidia driver NVIDIA-vGPU-rhel-7.6-410.91.x86_64.rpm installed CentOS 7.6 guest configuration: NVidia driver NVIDIA-Linux-x86_64-410.92-grid.run installed added an explicit BusID in the guest's xorg.conf file disabled SELinux Windows 10 guest configuration: NVidia driver 412.16_grid_win10_server2016_64bit_international.exe installed Remote viewer: remote-viewer 5.0-11.el7 running on CentOS 7.3 Both host and guest NVidia drivers come from the NVIDIA-GRID-RHEL-7.6-410.92-410.91-412.16.zip package. We have tried with both V100 and P4 GPUs (with ECC disabled), and encounter similar problems. Any ideas on what to try, or how to better diagnose the cause of these problems? Thanks.

1 0