[ovirt-users] not exist gluster volume mounted on a node
Hi! I have a little problem with my 3.5. I have a not-exist gluster volume that is mounted on a node. Some weeks ago it's really existed, but it has been deleted. After node restart or a single service restart it's always shown as mounted on one node. How can I refresh the good configuration for vdsm on this node? Thanks, Tibor ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] noVNC problems after upgrading to 3.5.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.11.2014 23:27, Darrell Budic wrote: That’s what I thought too, but... Firefox tells me “This certificate is already installed as a certificate authority.” though. It looks like the cert for :6100 is the proper one, too. Maybe a firefox change with their new signing rules (i’ve disabled security.use_mozillapkix_verification due to problems with other internal certs)? I tried removing all the old web site certs and still had to add the https://engine:6100 cert to get the noVNC console to connect. also I'm wondering why the certificate should get exchanged during upgrade? is this the normal upgrade path? Does upgrade renew/change any previously installed certificates? I guess this should not happen? thanks for any answers in advance Sven -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQGcBAEBAgAGBQJUZ7GHAAoJEAq0kGAWDrqlt8QMAMSy5pw3LE+mYC/kux8DIiQh nbD9xnJj2jZpbg21/wp+aHDGXp99NJl6GGN0ClMnZkPAH1WmCYmxq7zEcqSGnAV7 Nu5+LsmFvyktK+u2INXNi/5Z3NNYCUbGLHOL2d4CprmBOAy/5G+5G4ucBNRmBTIH 8MzLop2sJEtHQ6ZK2VbzpD/5k7K87VwhLSGIXx9R72AEmeuH9p0Q4GNDxhLU99lO 5fMyF63ExECoMGdb/JwSUQ/juZ79K6UnRY63qTdFlMXW7eddf+zetmZrS8eE4lHe HEe+IuMSqqsHovpHn7lCnM27AsQzG6UITqCz9atlO34zlqd2jvaoWhsbYBO0wrUS MKUsMB/abdp/N1Vhs1WigsYkCvv4OoSzabBkrQ+pU9ivzK+zagwi65lqx1nsgfCH UigwWWnb6SWUeGpPu40UYOCAqYWCGCcH3H0kuuGtVsql55Vr++OSHoG9Q9kRYpj3 0d6GfSW9V+6hvhc/jv9C6BAzTY0clNSwiBKBZZyi2w== =VavE -END PGP SIGNATURE- ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Mail in spam folder ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.11.2014 22:35, Gianluca Cecchi wrote: Strange that for about 3 months I didn't get any e-mail about the list in spam and now about 20 a day... Ok, I didn't know this option about spam in gmail filters. I have set it. Let's see how it goes. Here is a bugzilla regarding this topic for rhel6: https://bugzilla.redhat.com/show_bug.cgi?id=1095359 and here is something for centos (which of course just follows upstream), because the centos users list is haunted by the same problem: https://bugs.centos.org/view.php?id=7149 this applies not just to gmail, but also to yahoo and some other mail providers. if you got a rhel subscription you could open a case with support to emphasize the impact of this old mailman software. regards Sven -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQGcBAEBAgAGBQJUZ7KyAAoJEAq0kGAWDrqlb7AL/2jQUA9t2eDY6+i16/CZ+ERr KTNmkswGuhBtAqGSO39TKv2m1W0653HAYeNfOaYI5lSNqWwCsn1Iu/x10h53W9sT iwSgWtP8mQR09EUXUSJu5+yi2xrzfjrz+kJ4G+qlcQA+Dp8aKKM5QcS63ywb0rjW lVvpG9cPglZs97TNRYc/Xluif3Ntm+m1cfVBJFCwFvYtrRsSKHc01s2XSnEIZ/UM hn0xubJHrGbrf1eyuhh10mc0nGVc2DczY/CV0N//lq352ZplvPhm5Ia/sC009rxd h6yWfkCnASlE+QUY9z+v9dujc1mVYXdk6DRr0cPzm37+slaSgyK9BBuMZr2YGADR r/KpYzkLz6JYOhZRhIVNBdtQn9DgS/eFvOyJ7EPV6UZll2mMu2OIBDyB5MJVTVhL OS2jYsXhOJmJMU83wz6NtJsg1PgVLVb2wYrai7EeDqawnXWNcqVVslFsAR3TPn2N MbK2zG2rHkgFFprJDw4wweKUf1t0SFPuoiNGY1+Fqg== =8wlO -END PGP SIGNATURE- ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] ovirt-websocket-proxy uses the wrong IP
Hello, One of my nodes has two IP addresses, 10.42.0.101 and 10.42.0.103. Ovirt is configured to use 10.42.0.101, yet the ovirt-websocket-proxy service tries to connect to 10.42.0.103, where no VNC server is listening. Is there any way I can configure it to use the correct address? [root@engine ~]# /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --debug start ovirt-websocket-proxy[1838] DEBUG _daemon:403 daemon entry pid=1838 ovirt-websocket-proxy[1838] DEBUG _daemon:404 background=False ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.conf' ovirt-websocket-proxy[1838] DEBUG loadFile:70 loading config '/etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf' ovirt-websocket-proxy[1838] DEBUG _daemon:440 I am a daemon 1838 ovirt-websocket-proxy[1838] DEBUG _setLimits:377 Setting rlimits WebSocket server settings: - Listen on *:6100 - Flash security policy server - SSL/TLS support - Deny non-SSL/TLS connections - proxying from *:6100 to targets in /dummy 1: 10.42.0.1: new handler Process 1: 10.42.0.1: SSL/TLS (wss://) WebSocket connection 1: 10.42.0.1: Version hybi-13, base64: 'True' 1: 10.42.0.1: Path: '/eyJ2YWxpZFRvIjoiMjAxNDExMTUyMTI1MDgiLCJkYXRhIjoiJTdCJTIyaG9zdCUyMjolMjIxMC40Mi4wLjEwMyUyMiwlMjJwb3J0JTIyOiUyMjU5MDElMjIsJTIyc3NsX3RhcmdldCUyMjpmYWxzZSU3RCIsInZhbGlkRnJvbSI6IjIwMTQxMTE1MjEyMzA4Iiwic2lnbmVkRmllbGRzIjoidmFsaWRUbyxkYXRhLHZhbGlkRnJvbSxzYWx0Iiwic2lnbmF0dXJlIjoiajRQUmxwYjBvT0dOZUNPaHZKK01wUTVrVGRMYVA0Sm8zRDIzTGlXRlZYRm4xNU9KN0NZVmw5OTBpNTBUNzlVZkpqUzRlRmZ1SHJhT1c4TlFNbXIwanZXSUpTWCtnL3RYSnc4MWRFS2wrcFVPVHo3MWlmY2dTbXdITmptOUkwTTl6Q0NNR2dvbE1BRzZwMndFbDFySDdSZkhMWnIvOGo4bnpnVGZ0NlhaOTdBcHgyejhkMlo0UjRmdklXemtXMjErMDdsNWw4dXpNVytEM1FmaWdDS1Q3V3VKdlFHNi9SSC9zZWRBWHJXcnFUNXYzTHNuNVl0MWtYb2lGV3ZYOHNUdE5PdGdvQWk3eGN5WUhGaEM1ei9SMjZXNEkrSlJNcDZlVDNxbWVlZnM0eWRSN0NpZWwzZWZvZDB5TU9meGJwMG9EMGlscXVWUWVjK1JxeGxqd21ZVG5BPT0iLCJzYWx0IjoiWGhVQ1dYL2hQU1U9In0=' 1: connecting to: 10.42.0.103:5901 1: handler exception: [Errno 111] Connection refused 1: Traceback (most recent call last): File /usr/lib/python2.6/site-packages/websockify/websocket.py, line 711, in top_new_client self.new_client() File /usr/lib/python2.6/site-packages/websockify/websocketproxy.py, line 183, in new_client connect=True, use_ssl=self.ssl_target, unix_socket=self.unix_target) File /usr/lib/python2.6/site-packages/websockify/websocket.py, line 188, in socket sock.connect(addrs[0][4]) File string, line 1, in connect error: [Errno 111] Connection refused Regards, mots signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Fake power management?
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: mots m...@nepu.moe, users@ovirt.org Sent: Friday, November 14, 2014 5:15:25 PM Subject: Re: [ovirt-users] Fake power management? Il 14/11/2014 15:54, mots ha scritto: Hello, I'm building a small demonstration system for our sales team to take to a customer so that they can show them our solutions. Hardware: Two Intel NUC's, a 4 port switch and a laptop. Engine: Runs as a VM on one of the NUCs, which one it runs on is determined by pacemaker. Storage: Also managed by pacemaker, it's drbd backed and accessed with iscsi. oVirt version: 3.5 OS: CentOS 6.6 Just for curiosity, any reason for using pacemaker instead on oVirt Hosted Engine solution? The idea is to have our sales representative (or the potential customer himself) randomly pull the plug on one of the NUCs to show that the system stays operational when part of the hardware fails. My problem is that I don't have any way to implement power management, so the Engine can't fence nodes and won't restart guests that were running on the node which lost power. In pacemaker I can just configure fencing over SSH or even disable the requirement to do so completely. Is there something similar for oVirt, so that the Engine will consider a node which it can't connect to to be powered down? Well, we are thinking of adding such ability (Fake power management) mainly for testing purpose... Meanwhile, I think I have a work-around that may help you. When we have a connectivity issue with a node, we first try (after a grace period) to restart its VDSM via SSH this is always done before the hard-fencing (restart via the PM card) and can be done no matter if the host has PM configured or not. So basically when a connectivity issue is found, you can custom the SSH command that restarts VDSM to do whatever you want, even a script or a power-down command look at the result of psql -U engine -c select * from vdc_options where option_name ilike 'SshSoftFencingCommand' engine option_id | option_name | option_value | version ---+---+--+- 558 | SshSoftFencingCommand | service vdsmd restart| 3.0 559 | SshSoftFencingCommand | service vdsmd restart| 3.1 560 | SshSoftFencingCommand | service vdsmd restart| 3.2 561 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.3 562 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.4 563 | SshSoftFencingCommand | /usr/bin/vdsm-tool service-restart vdsmd | 3.5 Please note: 1) change only the value that match your cluster version 2) restart engine so change can take place 3) restore to default value again after you are done Does this may be useful for you ? Regards, mots ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
