- Users - oVirt List Archives

Re: Ovirt Glusterfs
by Strahil 25 Feb '19

25 Feb '19

I have done some testing and it seems that storhaug + ctdb + nfs-ganesha is showing decent performance in a 3 node hyperconverged setup. Fuse mounts are hitting some kind of limit when mounting gluster -3.12.15 volumes. Best Regards, Strahil Nikolov

3 2

Creating new VM
by Yujin Boby 24 Feb '19

24 Feb '19

I installed oVirt, when i try to create a new VM, it says This host is managed by a virtualization manager, so creation of new VM from this host is not possible. https://imgur.com/a/hpqV6ML Any idea why i am getting this error ? Do i need more than 1 server to create Virtual machines ? Like adding a node ?

2 1

update to 4.2.8 fails
by Vincent Royer 24 Feb '19

24 Feb '19

trying to update from 4.2.6 to 4.2.8 yum update fails with: --> Finished Dependency Resolution Error: Package: vdsm-4.20.46-1.el7.x86_64 (ovirt-4.2) Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.3 Installed: libvirt-daemon-kvm-3.9.0-14.el7_5.8.x86_64 (installed) libvirt-daemon-kvm = 3.9.0-14.el7_5.8 Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 (ovirt-4.2-centos-qemu-ev) Requires: libepoxy.so.0()(64bit) Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 (ovirt-4.2-centos-qemu-ev) Requires: libibumad.so.3()(64bit) Error: Package: 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64 (ovirt-4.2-centos-qemu-ev) Requires: libgbm.so.1()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Uploading Enabled Repositories Report 2019-02-13 16:42:14,190 [INFO] yum:17779:Dummy-18 @connection.py:868 - Connection built: host=subscription.rhsm.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False Loaded plugins: fastestmirror, product-id, subscription-manager 2019-02-13 16:42:14,199 [WARNING] yum:17779:Dummy-18 @logutil.py:141 - logging already initialized 2019-02-13 16:42:14,200 [ERROR] yum:17779:Dummy-18 @identity.py:145 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem' 2019-02-13 16:42:14,200 [INFO] yum:17779:Dummy-18 @connection.py:868 - Connection built: host=subscription.rhsm.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False 2019-02-13 16:42:14,201 [INFO] yum:17779:Dummy-18 @repolib.py:471 - repos updated: Repo updates Total repo updates: 0 Updated <NONE> Added (new) <NONE> Deleted <NONE> This system is not registered with an entitlement server. You can use subscription-manager to register. Cannot upload enabled repos report, is this client registered? [root@brian yum.repos.d]# yum repolist Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade 2019-02-13 16:42:36,489 [ERROR] yum:17809:MainThread @identity.py:145 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem' 2019-02-13 16:42:36,490 [INFO] yum:17809:MainThread @connection.py:868 - Connection built: host=subscription.rhsm.redhat.com port=443 handler=/subscription auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False 2019-02-13 16:42:36,491 [INFO] yum:17809:MainThread @repolib.py:471 - repos updated: Repo updates Total repo updates: 0 Updated <NONE> Added (new) <NONE> Deleted <NONE> This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * ovirt-4.2: mirrors.rit.edu * ovirt-4.2-epel: mirror.sjc02.svwh.net repo id repo name status centos-sclo-rh-release/x86_64 CentOS-7 - SCLo rh 8,113 ovirt-4.2/7 Latest oVirt 4.2 Release 2,558 ovirt-4.2-centos-gluster312/x86_64 CentOS-7 - Gluster 3.12 262 ovirt-4.2-centos-opstools/x86_64 CentOS-7 - OpsTools - release 853 ovirt-4.2-centos-ovirt42/x86_64 CentOS-7 - oVirt 4.2 631 ovirt-4.2-centos-qemu-ev/x86_64 CentOS-7 - QEMU EV 71 ovirt-4.2-epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 *Help!*

6 11

How to recreate Ovirt CA from scratch
by Giorgio Biacchi 24 Feb '19

24 Feb '19

Hi list, during our datacenter lifetime many things changed. We moved the engine twice on different hosts with, of course, different FQDNs, and many other changes. Now we are stuck with an error when we try to upload an image to a data domain. The error is somehow bound to a failure to validate the ovirt-imageio-proxy certificate and, since the current root CA certificate is still signed with sha1WithRSAEncryption we'd like to regenerate the whole CA. That's the steps we've done.. without success... 1) Make a tar.gz of the /etc/pki/ovirt-engine as backup 2) Create a new CA cert using the same private key: openssl req -key /etc/pki/ovirt-engine/private/ca.pem -new -x509 -days 3650 -sha256 -extensions v3_ca -out newca.cert.pem 3) Put the new CA cert in place mv ca.pem ca.pem.orig.20190219;mv newca.cert.pem ca.pem 4) Resign all the other certs names="engine apache websocket-proxy jboss imageio-proxy" for name in $names; do subject="$( openssl \ x509 \ -in /etc/pki/ovirt-engine/certs/"${name}".cer \ -noout \ -subject \ | sed \ 's;subject= $.*$;\1;' \ )" /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh \ --name="${name}" \ --password=mypass \ --subject="${subject}" \ --keep-key done 5) Restart all the services systemctl restart httpd systemctl restart ovirt-engine systemctl restart ovirt-websocket-proxy systemctl restart ovirt-imageio-proxy The following step was to take the backup at 1) and fall back to the initial state because nothing worked as expected. There's any documented procedure about how to recreate Ovirt CA from scratch?? Thanks in advance -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

2 3

Re: Info about AD integration and Root CA
by Strahil 23 Feb '19

23 Feb '19

You can get the root CA from any windows machine in the domain . Best Regards, Strahil Nikolov

1 0

Installing oVirt on Physical machine (Solved)
by emmanualvnebu1＠gmail.com 23 Feb '19

23 Feb '19

Issue: Unable to install oVirt on physical machine with USB. Once selected the option to install oVirt 4.3 it give a screen "dracut-initqueue time out And then get into emergency mode & gives dracut cmd line. Fix:I think I fixed it. The issue was with the bootable usb. Tried with multiple software to create & one worked. https://www.balena.io/etcher/ Thanks for everyone’s help.. Appreciate it.

1 0

Installing oVirt on Physical machine V4.3
by emmanualvnebu1＠gmail.com 23 Feb '19

23 Feb '19

Hi Guys, I am trying to install oVirt node on a physical machine. Once selected the option to install oVirt 4.3 it give a screen "dracut-initqueue time out And then get into emergency mode & gives dracut cmd line. if I exit the command line, it continue boot into the installation window. However it gives a message "Kickstart file /run/install/ks.config is missing" (Pane is dead). Tried the same on vmware, it boot fine & am able to install it. Can someone tell me how could I fix this?

3 11

Re: Installing oVirt on Physical machine V4.3
by Emmanual Vnebu 23 Feb '19

23 Feb '19

I think I fixed it. The issue was with the bootable usb. Tried with multiple software to create & one worked. https://www.balena.io/etcher/ Thanks for everyone’s help.. Appreciate it.. 😊 Sent from Mail for Windows 10

1 0

Design question: one big NFS share or several smaller ones?
by Markus Schaufler 22 Feb '19

22 Feb '19

Hi all, I've got a design question: Are there any best practices regarding NFS datastores especially datastore sizing? Should I use one big NFS datastore and expand it on demand or should the size not exceed a certain limit and start with a new NFS datastore? Are there any other configuration considerations (NFS v3 or v4(.1) and mounting options)?

3 2

Fencing : SSL or not?
by Nicolas Ecarnot 22 Feb '19

22 Feb '19

Hello, As fence_idrac has never worked for us, and as fence_ipmilan has worked nicely since years, we are using fence_ipmilan with the lanplus=1 option and we're happy with it. We upgraded to 4.3.0.4 and we're witnessing that we cannot fence our hosts anymore : 2019-02-18 09:42:08,678+01 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-11) [2f78ed99-6703-4d92-b7cb-948c2d24b623] Can not run fence action on host 'xxxxx', no suitable proxy host was found. and on the SPM : fence_ipmilan: Failed: Unable to obtain correct plug status or plug is not available I found the suggested workaround here : https://access.redhat.com/solutions/3349841 but no combination of - lanplus={0,1} - -z - ssl=={0,1} lead to no solution. The package version is the same as what's described in the KB : fence-agents-rhevm-4.2.1-11.el7_6.7.x86_64 What should I test now? Thank you. -- Nicolas ECARNOT

2 7