- Users - oVirt List Archives

"Volume Option cluster.granular-entry-heal=enable could not be set" when using "Optimize for Virt store"
by Jorick Astrego 06 Feb '19

06 Feb '19

Hi again, When using the option "Optimize for Virt store", I get the following error: 2019-02-06 10:25:02,353+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-15727) [051cfc8c-9efc-427c-9e2e-9127e3e0a86d] EVENT_ID: GLUSTER_VOLUME_OPTION_SET_FAILED(4,003), Volume Option cluster.granular-entry-heal=enable could not be set on ssd9 of cluster GlusterFS-storage. This looks like the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1635684 Volume set option 'granular-entry-heal' is not longer set via gluster volume set option. Is this a known issue or should I open a bug for this? Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

2 1

ovirt-node 4.3 hyperconverged - fails on VM deployment - all nodes broken
by feral 06 Feb '19

06 Feb '19

Boring 3 vanilla node deployment. Default options except for gluster volume size. All three nodes on static IP on LAN. All three have each other listed in /etc/hosts as well as dns. Gluster wizard complete successfully, deploy VM. VM deployment fails after copying to the gluster storage. At that point, rebooting any node results in node not coming back to life. No networking, so no other services. Only error I can get is to check the engine.log, which I cannot do as the engine fails to come up. Anyone else seeing this with a vanilla install/deployment? -- _____ Fact: 1. Ninjas are mammals. 2. Ninjas fight ALL the time. 3. The purpose of the ninja is to flip out and kill people.

1 0

ovirt-node 4.2 iso - hyperconverged wizard doesn't write gdeployConfig settings
by feral 06 Feb '19

06 Feb '19

New install of ovirt-node 4.2 (from iso). Setup each node with networking and ssh keys, and use the hyperconverged gluster deployment wizard. None of the user specified settings are ever reflected in the gdeployConfig.conf. Anyone running into this? -- _____ Fact: 1. Ninjas are mammals. 2. Ninjas fight ALL the time. 3. The purpose of the ninja is to flip out and kill people.

7 12

performance issues with Windows 10
by Hetz Ben Hamo 06 Feb '19

06 Feb '19

Hi, I'm doing some very simple disk benchmarks on Windows 10, both with ESXI 6.7 and oVirt 4.3.0. Both Windows 10 Pro guests have all the driver installed. the "Storage" (Datastore in VMWare and storage domains in oVirt) comes from the same ZFS machine, both mounted as NFS *without* any parameters for NFS mount. The ESXI is running on HP DL360 G7 with E5620 CPU, while the oVirt node is running on IBM X3550 M3 with dual Xeon E5620. There are no memory issues as both machines have plenty of free memory and free CPU resources. Screenshots: - Windows 10 in vSphere 6.7 - https://imgur.com/V75ep2n - Windows 10 in oVirt 4.3.0 - https://imgur.com/3JDrWLx As you can see, while oVirt lags a bit in 4K Read, the write performance is really bad. How can this be improved? Thanks

2 1

Re: ovirt 4.2.7 -> 4.3.0 upgrade process
by Douglas Duckworth 06 Feb '19

06 Feb '19

Thanks everyone! We will try the upgrade to 4.2.8 then try 4.3 later. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Wed, Feb 6, 2019 at 11:56 AM Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> wrote: Il giorno mer 6 feb 2019 alle ore 17:28 Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> ha scritto: Hello Can anyone confirm that the steps for upgrading to 4.3 from 4.2 are the same as listed for previous versions? I reviewed 4.1 to 4.2 which looks straight forward: https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_t…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_document…> I am sure nothing will go wrong though we are doing daily backups of the hosted engine VM database. If you are on 4.2.7 I would recommend upgrade the engine to 4.2.8 before upgrading to 4.3. Since in 4.3 we switched from fluentd to rsyslog for the metrics part, with 4.2.7 you may have some issue if you upgrade hosts to 4.3 before the engine gets upgraded. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_site_pri…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_communit…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VC2TVZIHTOTMZ…<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archiv…> -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_&d=DwMF…> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://www.redhat.com/files/brand/email/sig-redhat.png]<https://urldefense.proofpoint.com/v2/url?u=https-3A__red.ht_sig&d=DwMFaQ&c=…>

1 0

sun.security.validator
by suporte＠logicworks.pt 06 Feb '19

06 Feb '19

Hi, I'm running Version 4.2.3.8-1.el7, and after reboot the engine machine no longer could login into administration portal with this error: sun.security.validator.ValidatorException: PKIX path validation faile java.security.cert.CertPathValidatorException: validity check failed I'm using a self signed cert. Any idea? Thanks -- Jose Ferradeira http://www.logicworks.pt

5 5

ovirt 4.2.7 -> 4.3.0 upgrade process
by Douglas Duckworth 06 Feb '19

06 Feb '19

Hello Can anyone confirm that the steps for upgrading to 4.3 from 4.2 are the same as listed for previous versions? I reviewed 4.1 to 4.2 which looks straight forward: https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_from_4.1_t… I am sure nothing will go wrong though we are doing daily backups of the hosted engine VM database. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690

5 5

Strange behavior when changing memory and virtual cpu for VM
by matthias.barmeier＠sourcepark.de 06 Feb '19

06 Feb '19

Hi, after creating a VM from a template everything works fine. After a while I would like to increase memory and cpus. I changed the memory and virtual cpu settings in the "System" settings. I restarted the VM. From this moment on the VM hangs on boot with this messages filling the console: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' Connection to 169.254.169.254 timed out. This goes on for ever. What can I do to make the VM work again ? I tried to restore the settings to the values it has before but this does not help. The VM contains debian 9 (stretch) with cloud init. Ovirt version: 4.2.7.5-1.el7 Ciao Matze

4 4

But in the web interface?
by Hetz Ben Hamo 06 Feb '19

06 Feb '19

Hi, I upgraded to 4.3 and on the hosted engine web interface, I see the "dashboard" button twice, one below the other. How can I fix it or is it a known bug? Thanks Hetz

7 14

Re: Changing CPU type from Opteron G3 to Epyc with hosted engine in 4.3
by Simone Tiraboschi 06 Feb '19

06 Feb '19

On Wed, Feb 6, 2019 at 11:02 AM Juhani Rautiainen < juhani.rautiainen(a)gmail.com> wrote: > On Wed, Feb 6, 2019 at 11:27 AM Juhani Rautiainen > <juhani.rautiainen(a)gmail.com> wrote: > > > > On Wed, Feb 6, 2019 at 10:31 AM Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > > > > > > The only case that could prevent that is that you are in hosted-engine > mode and so you cannot set the latest host into maintenance mode without > loosing the engine itself. > > > > > > If this is your case, > > > what you can do is: > > > - set HE global maintenance mode > > > - set one of the hosted-engine hosts into maintenance mode > > > - move it to a different cluster > > > - shutdown the engine VM > > > - manually restart the engine VM on the host on the custom cluster > directly executing on that host: hosted-engine --vm-start > > > - connect again to the engine > > > - set all the hosts of the initial cluster into maintenance mode > > > - upgrade the cluster > > > - shut down again the engine VM > > > - manually restart the engine VM on one of the hosts of the initial > cluster > > > - move back the host that got into a temporary cluster to its initial > cluster > > > > I might try this one. > > I tried this one and it worked. There was problem with couple of VM's > (they were made from OVA from Virtualbox). It couldn't upgrade old > cluster until they were moved to temporary cluster too (complaining > about wrong cluster level). It might have been the real reason why the > normal upgrade failed? Maybe the error message was wrong? > Thanks for the report, honestly I have to double check it because it looks a bit suspicious. I also think that an addition to https://github.com/oVirt/ovirt-ansible-cluster-upgrade to handle also the upgrade of the hosted-engine cluster making it smoother could make a lot of sense. > > Thanks a lot, > Juhani >

1 0