[Users] Booting oVirt node image 2.3.0, no install option
Hi folks, I'm trying to install oVirt node v2.3.0 on A Dell C2100 server. I can boot up just fine, but the two menu options I see are Start oVirt node, and Troubleshooting. When I choose Start oVirt node, it does just that, and I am soon after given a console login prompt. I've checked the docs, and I don't see what I'm supposed to do next, as in a password etc. Am I missing something? Thanks, -Adam ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Use Filer for NFS storage
On Sun, Apr 15, 2012 at 04:57:15PM +0300, Dan Kenigsberg wrote: On Fri, Apr 13, 2012 at 12:26:39PM -0700, Christian Hernandez wrote: Here is the log from the Host *Thread-1821::DEBUG::2012-04-13 12:18:52,200::BindingXMLRPC::167::vds::(wrapper) [192.168.11.236] Thread-1821::ERROR::2012-04-13 12:18:52,200::BindingXMLRPC::171::vds::(wrapper) Unexpected exception Traceback (most recent call last): File /usr/share/vdsm/BindingXMLRPC.py, line 169, in wrapper return f(*args, **kwargs) File /usr/share/vdsm/BindingXMLRPC.py, line 571, in poolValidateStorageServerConnection return pool.validateStorageServerConnection(domType, conList) File /usr/share/vdsm/API.py, line 897, in validateStorageServerConnection return self._irs.validateStorageServerConnection(domainType, AttributeError: 'NoneType' object has no attribute 'validateStorageServerConnection' Thread-1822::DEBUG::2012-04-13 12:18:52,333::BindingXMLRPC::167::vds::(wrapper) [192.168.11.236] Thread-1822::ERROR::2012-04-13 12:18:52,334::BindingXMLRPC::171::vds::(wrapper) Unexpected exception Traceback (most recent call last): File /usr/share/vdsm/BindingXMLRPC.py, line 169, in wrapper return f(*args, **kwargs) File /usr/share/vdsm/BindingXMLRPC.py, line 491, in poolDisconnectStorageServer return pool.disconnectStorageServer(domType, conList) File /usr/share/vdsm/API.py, line 823, in disconnectStorageServer return self._irs.disconnectStorageServer(domainType, self._UUID, AttributeError: 'NoneType' object has no attribute 'disconnectStorageServer' It seems like the interesting traceback should be further up - I suppose self._irs failed initialization and kept its original None value. Please scroll up and try to find out why this failed on Vdsm startup. We have a FIXME in vdsm so that we report such failures better: vdsm/BindingXMLRPC.py: # XXX: Need another way to check if IRS init was okay Adam, could you take a further look into this? Have a look at http://gerrit.ovirt.org/3571 . This should handle the problem better by reporting a better error when storage was not initialized properly. -- Adam Litke a...@us.ibm.com IBM Linux Technology Center ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt-node trying to use NFS4
On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: Hi Juan, On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote: On 04/13/2012 07:20 PM, Ian Levesque wrote: Hi, I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory). Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term. Mike ___ 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
Re: [Users] ovirt-node trying to use NFS4
On 04/16/2012 06:09 PM, Mike Burns wrote: On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: Hi Juan, On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote: On 04/13/2012 07:20 PM, Ian Levesque wrote: Hi, I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory). Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term. Mike Isn't that what http://www.ovirt.org/wiki/Features/AdvancedNfsOptions all about ? Y. ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt-node trying to use NFS4
On Mon, 2012-04-16 at 18:13 +0300, Yaniv Kaul wrote: On 04/16/2012 06:09 PM, Mike Burns wrote: On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: Hi Juan, On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote: On 04/13/2012 07:20 PM, Ian Levesque wrote: Hi, I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory). Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term. Mike Isn't that what http://www.ovirt.org/wiki/Features/AdvancedNfsOptions all about ? Y. Reading that, looks like it's geared toward I/O timeouts, but could certainly be used for the other options. I wasn't aware of the feature previously. My point was simply that we shouldn't be use edit/persist long term for issues like this. There needs to be either a bug or feature filed so that we solve it long term. Mike ___ 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Use Filer for NFS storage
Excuse my ignorance... But how do I apply the patch? I don't testing the patch on my systems (as I am only testing myself); but I am... 1) Only have a elementary skills at git 2) Don't know how to apply the patch --Christian On Mon, Apr 16, 2012 at 6:50 AM, Adam Litke a...@us.ibm.com wrote: On Sun, Apr 15, 2012 at 04:57:15PM +0300, Dan Kenigsberg wrote: On Fri, Apr 13, 2012 at 12:26:39PM -0700, Christian Hernandez wrote: Here is the log from the Host *Thread-1821::DEBUG::2012-04-13 12:18:52,200::BindingXMLRPC::167::vds::(wrapper) [192.168.11.236] Thread-1821::ERROR::2012-04-13 12:18:52,200::BindingXMLRPC::171::vds::(wrapper) Unexpected exception Traceback (most recent call last): File /usr/share/vdsm/BindingXMLRPC.py, line 169, in wrapper return f(*args, **kwargs) File /usr/share/vdsm/BindingXMLRPC.py, line 571, in poolValidateStorageServerConnection return pool.validateStorageServerConnection(domType, conList) File /usr/share/vdsm/API.py, line 897, in validateStorageServerConnection return self._irs.validateStorageServerConnection(domainType, AttributeError: 'NoneType' object has no attribute 'validateStorageServerConnection' Thread-1822::DEBUG::2012-04-13 12:18:52,333::BindingXMLRPC::167::vds::(wrapper) [192.168.11.236] Thread-1822::ERROR::2012-04-13 12:18:52,334::BindingXMLRPC::171::vds::(wrapper) Unexpected exception Traceback (most recent call last): File /usr/share/vdsm/BindingXMLRPC.py, line 169, in wrapper return f(*args, **kwargs) File /usr/share/vdsm/BindingXMLRPC.py, line 491, in poolDisconnectStorageServer return pool.disconnectStorageServer(domType, conList) File /usr/share/vdsm/API.py, line 823, in disconnectStorageServer return self._irs.disconnectStorageServer(domainType, self._UUID, AttributeError: 'NoneType' object has no attribute 'disconnectStorageServer' It seems like the interesting traceback should be further up - I suppose self._irs failed initialization and kept its original None value. Please scroll up and try to find out why this failed on Vdsm startup. We have a FIXME in vdsm so that we report such failures better: vdsm/BindingXMLRPC.py: # XXX: Need another way to check if IRS init was okay Adam, could you take a further look into this? Have a look at http://gerrit.ovirt.org/3571 . This should handle the problem better by reporting a better error when storage was not initialized properly. -- Adam Litke a...@us.ibm.com IBM Linux Technology Center ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Hey everyone how do we upgrade engine?
On 13/04/12 19:59, Itamar Heim wrote: On 04/13/2012 06:42 PM, Dominic Kaiser wrote: I am running 3.0.0_0001-1.6.fc16 ovirt engine and has been great! I appreciate Red Hat and all the support from the community on this project you all are awesome! I have not thought about it yet but was looking on the wiki and did not see how to upgrade and reninstallengine. What have been your experiences doing this and is it worth it? And how to do it? Sorry if it was posted somewhere else just let me know if there is info on this already. by running the engine-upgrade utility, though i suspect it will have to pass some testing/bug fixes for the second release before can be used (doing a test upgrade at that phase on your environment would help finding issues) We have one issue that we know of and we'll fix soon - https://bugzilla.redhat.com/show_bug.cgi?id=790303 If you are interested you can track engine-de...@ovirt.org list for updates on this in the upcoming week (or keep track of the bug status). Livnat I have had the greatest experience moving from 2 esxiservers to ovirt. You guys and gals rock! thanks - nice to hear. ___ 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
Re: [Users] ovirt-node trying to use NFS4
On 04/16/2012 06:20 PM, Mike Burns wrote: On Mon, 2012-04-16 at 18:13 +0300, Yaniv Kaul wrote: On 04/16/2012 06:09 PM, Mike Burns wrote: On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: Hi Juan, On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote: On 04/13/2012 07:20 PM, Ian Levesque wrote: Hi, I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory). Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term. Mike Isn't that what http://www.ovirt.org/wiki/Features/AdvancedNfsOptions all about ? Y. Reading that, looks like it's geared toward I/O timeouts, but could certainly be used for the other options. I wasn't aware of the feature previously. My point was simply that we shouldn't be use edit/persist long term for issues like this. There needs to be either a bug or feature filed so that we solve it long term. well, for anything fancy, this can be used: http://www.ovirt.org/wiki/Features/PosixFSConnection but if we have an issue with NFS, i agree with need to solve it without using this. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
