Re: [Users] Ovirt 3.1 : node installation fails with no reason
On 08/14/2012 01:18 PM, Vincent Miszczak wrote: Hello guys, I have upgraded both my engine and node from Fedora 16 to Fedora 17. I have added the 3.1 release repo to both servers. My engine is working as expected. Now I want to add my node to it, but it fails everytime I try (the GUI says “Install Failed”), despite the installation log on the node show that everything is OK. I’ve looked to everything I’ve think about, cannot find why this fails :/ [root@ovirt-engine ovirt-engine]# rpm -qa ovirt* ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch ovirt-engine-tools-common-3.1.0-2.fc17.noarch ovirt-release-fedora-4-2.noarch ovirt-engine-userportal-3.1.0-2.fc17.noarch ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch ovirt-engine-dbscripts-3.1.0-2.fc17.noarch ovirt-engine-3.1.0-2.fc17.noarch ovirt-engine-sdk-3.1.0.4-1.fc17.noarch ovirt-engine-config-3.1.0-2.fc17.noarch ovirt-engine-webadmin-portal-3.1.0-2.fc17.noarch ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch ovirt-engine-genericapi-3.1.0-2.fc17.noarch ovirt-engine-restapi-3.1.0-2.fc17.noarch ovirt-engine-notification-service-3.1.0-2.fc17.noarch ovirt-engine-setup-3.1.0-2.fc17.noarch ovirt-engine-backend-3.1.0-2.fc17.noarch [root@ovirt-engine ovirt-engine]# rpm -qa vds* vdsm-cli-4.10.0-6.fc17.noarch vdsm-python-4.10.0-6.fc17.x86_64 vdsm-bootstrap-4.10.0-6.fc17.noarch vdsm-reg-4.10.0-6.fc17.noarch vdsm-hook-vhostmd-4.9.3.2-0.fc17.noarch vdsm-4.10.0-6.fc17.x86_64 vdsm-debuginfo-4.10.0-6.fc17.x86_64 vdsm-debug-plugin-4.10.0-6.fc17.noarch vdsm-gluster-4.10.0-6.fc17.noarch vdsm-xmlrpc-4.10.0-6.fc17.noarch vdsm-rest-4.10.0-6.fc17.noarch vdsm-tests-4.10.0-6.fc17.noarch vdsm-hook-faqemu-4.10.0-6.fc17.noarch [root@ovirt-node-01]# rpm -qa vds* vdsm-cli-4.10.0-6.fc17.noarch vdsm-hook-vhostmd-4.9.3.2-0.fc17.noarch vdsm-4.10.0-6.fc17.x86_64 vdsm-debuginfo-4.10.0-6.fc17.x86_64 vdsm-xmlrpc-4.10.0-6.fc17.noarch vdsm-rest-4.10.0-6.fc17.noarch vdsm-bootstrap-4.10.0-6.fc17.noarch vdsm-reg-4.10.0-6.fc17.noarch vdsm-python-4.10.0-6.fc17.x86_64 vdsm-tests-4.10.0-6.fc17.noarch vdsm-debug-plugin-4.10.0-6.fc17.noarch vdsm-hook-faqemu-4.10.0-6.fc17.noarch vdsm-gluster-4.10.0-6.fc17.noarch On the node : Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject = '192.168.3.24', random_num = 'c8008897-9996-43a0-a712-dbb99d72ed71', rev_num = 'None', installVirtualizationService = 'True', installGlusterService = 'False') Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with RHN/Satellite. Tue, 14 Aug 2012 12:00:58 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGAvailable VDSM matches requirements Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGvirtExplorer testing Tue, 14 Aug 2012 12:00:59 DEBUGCPU vendor is GenuineIntel Tue, 14 Aug 2012 12:00:59 DEBUGvirt support in cpu: True, in bios: True Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'elevator=deadline'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'processor.max_cstate=1'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGCheck required packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'SDL.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGSDL-1.2.14-16.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'bridge-utils.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGbridge-utils-1.5-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'mesa-libGLU.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGmesa-libGLU-8.0.3-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'openssl.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGopenssl-1.0.0j-2.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'm2crypto.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGm2crypto-0.21.1-8.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'rsync.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGrsync-3.0.9-2.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGCheck VDS packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'qemu-kvm'] Tue, 14 Aug 2012 12:00:59 DEBUGqemu-kvm-1.0.1-1.
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Hi again, I have removed then added the node again : same result. The engine does not log anything (but it seems its log level is INFO, how can I activate DEBUG ?). VDSM does not log anything neither (and vdsm-reg folder is empty on both node and engine). -Message d'origine- De : Itamar Heim [mailto:ih...@redhat.com] Envoyé : mardi 14 août 2012 16:28 À : Vincent Miszczak Cc : users@ovirt.org Objet : Re: [Users] Ovirt 3.1 : node installation fails with no reason On 08/14/2012 01:18 PM, Vincent Miszczak wrote: > Hello guys, > > I have upgraded both my engine and node from Fedora 16 to Fedora 17. > > I have added the 3.1 release repo to both servers. > > My engine is working as expected. Now I want to add my node to it, but > it fails everytime I try (the GUI says "Install Failed"), despite the > installation log on the node show that everything is OK. > > I've looked to everything I've think about, cannot find why this fails > :/ > > [root@ovirt-engine ovirt-engine]# rpm -qa ovirt* > > ovirt-log-collector-3.1.0-0.git10d719.fc17.noarch > > ovirt-engine-tools-common-3.1.0-2.fc17.noarch > > ovirt-release-fedora-4-2.noarch > > ovirt-engine-userportal-3.1.0-2.fc17.noarch > > ovirt-image-uploader-3.1.0-0.git9c42c8.fc17.noarch > > ovirt-engine-dbscripts-3.1.0-2.fc17.noarch > > ovirt-engine-3.1.0-2.fc17.noarch > > ovirt-engine-sdk-3.1.0.4-1.fc17.noarch > > ovirt-engine-config-3.1.0-2.fc17.noarch > > ovirt-engine-webadmin-portal-3.1.0-2.fc17.noarch > > ovirt-iso-uploader-3.1.0-0.git1841d9.fc17.noarch > > ovirt-engine-genericapi-3.1.0-2.fc17.noarch > > ovirt-engine-restapi-3.1.0-2.fc17.noarch > > ovirt-engine-notification-service-3.1.0-2.fc17.noarch > > ovirt-engine-setup-3.1.0-2.fc17.noarch > > ovirt-engine-backend-3.1.0-2.fc17.noarch > > [root@ovirt-engine ovirt-engine]# rpm -qa vds* > > vdsm-cli-4.10.0-6.fc17.noarch > > vdsm-python-4.10.0-6.fc17.x86_64 > > vdsm-bootstrap-4.10.0-6.fc17.noarch > > vdsm-reg-4.10.0-6.fc17.noarch > > vdsm-hook-vhostmd-4.9.3.2-0.fc17.noarch > > vdsm-4.10.0-6.fc17.x86_64 > > vdsm-debuginfo-4.10.0-6.fc17.x86_64 > > vdsm-debug-plugin-4.10.0-6.fc17.noarch > > vdsm-gluster-4.10.0-6.fc17.noarch > > vdsm-xmlrpc-4.10.0-6.fc17.noarch > > vdsm-rest-4.10.0-6.fc17.noarch > > vdsm-tests-4.10.0-6.fc17.noarch > > vdsm-hook-faqemu-4.10.0-6.fc17.noarch > > [root@ovirt-node-01]# rpm -qa vds* > > vdsm-cli-4.10.0-6.fc17.noarch > > vdsm-hook-vhostmd-4.9.3.2-0.fc17.noarch > > vdsm-4.10.0-6.fc17.x86_64 > > vdsm-debuginfo-4.10.0-6.fc17.x86_64 > > vdsm-xmlrpc-4.10.0-6.fc17.noarch > > vdsm-rest-4.10.0-6.fc17.noarch > > vdsm-bootstrap-4.10.0-6.fc17.noarch > > vdsm-reg-4.10.0-6.fc17.noarch > > vdsm-python-4.10.0-6.fc17.x86_64 > > vdsm-tests-4.10.0-6.fc17.noarch > > vdsm-debug-plugin-4.10.0-6.fc17.noarch > > vdsm-hook-faqemu-4.10.0-6.fc17.noarch > > vdsm-gluster-4.10.0-6.fc17.noarch > > On the node : > > Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation > > Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject = > '192.168.3.24', random_num = 'c8008897-9996-43a0-a712-dbb99d72ed71', > rev_num = 'None', > > installVirtualizationService = 'True', installGlusterService = > 'False') > > Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks > > Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with > RHN/Satellite. > > Tue, 14 Aug 2012 12:00:58 DEBUG status='OK' message='Host properly registered with RHN/Satellite.'/> > > Tue, 14 Aug 2012 12:00:59 DEBUGAvailable VDSM matches requirements > > Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' message='Available VDSM matches requirements'/> > > Tue, 14 Aug 2012 12:00:59 DEBUGvirtExplorer testing > > Tue, 14 Aug 2012 12:00:59 DEBUGCPU vendor is GenuineIntel > > Tue, 14 Aug 2012 12:00:59 DEBUGvirt support in cpu: True, in bios: True > > Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' processor='Intel' message='Server supports > virtualization'/> > > Tue, 14 Aug 2012 12:00:59 DEBUG type='FEDORA' message='Supported platform version'/> > > Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' version='3.5.1-1.fc17.x86_64' message='Supported kernel > version: [~3.5.1~, ~1.f > > c17.x86_64~]'/> > > Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', > 'DEFAULT', '--args', 'elevator=deadline'] > > Tue, 14
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Hi, Manually uninstall libjpeg and install it. Then try to add it using the GUI. -Sharad Quoting Douglas Landgraf : Hi Vicent, On 08/14/2012 06:18 AM, Vincent Miszczak wrote: Hello guys, I have upgraded both my engine and node from Fedora 16 to Fedora 17. I have added the 3.1 release repo to both servers. My engine is working as expected. Now I want to add my node to it, but it fails everytime I try (the GUI says "Install Failed"), despite the installation log on the node show that everything is OK. I've looked to everything I've think about, cannot find why this fails :/ The below logs are all that you have in /tmp/vds_* in the Node side? Could you please attach the log from engine? I am wondering what might happened. On the node : Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject = '192.168.3.24', random_num = 'c8008897-9996-43a0-a712-dbb99d72ed71', rev_num = 'None', installVirtualizationService = 'True', installGlusterService = 'False') Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with RHN/Satellite. Tue, 14 Aug 2012 12:00:58 DEBUG component='RHN_REGISTRATION' status='OK' message='Host properly registered with RHN/Satellite.'/> Tue, 14 Aug 2012 12:00:59 DEBUGAvailable VDSM matches requirements Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' message='Available VDSM matches requirements'/> Tue, 14 Aug 2012 12:00:59 DEBUGvirtExplorer testing Tue, 14 Aug 2012 12:00:59 DEBUGCPU vendor is GenuineIntel Tue, 14 Aug 2012 12:00:59 DEBUGvirt support in cpu: True, in bios: True Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' processor='Intel' message='Server supports virtualization'/> Tue, 14 Aug 2012 12:00:59 DEBUG type='FEDORA' message='Supported platform version'/> Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' version='3.5.1-1.fc17.x86_64' message='Supported kernel version: [~3.5.1~, ~1.f c17.x86_64~]'/> Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'elevator=deadline'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'processor.max_cstate=1'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGCheck required packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'SDL.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGSDL-1.2.14-16.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='SDL.x86_64' message='SDL-1.2.14-16.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'bridge-utils.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGbridge-utils-1.5-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='bridge-utils.x86_64' message='bridge-utils-1.5-3.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'mesa-libGLU.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGmesa-libGLU-8.0.3-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='mesa-libGLU.x86_64' message='mesa-libGLU-8.0.3-3.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'openssl.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGopenssl-1.0.0j-2.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='openssl.x86_64' message='openssl-1.0.0j-2.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'm2crypto.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGm2crypto-0.21.1-8.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='m2crypto.x86_64' message='m2crypto-0.21.1-8.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'rsync.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGrsync-3.0.9-2.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='rsync.x86_64' message='rsync-3.0.9-2.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUGCheck VDS packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'qemu-kvm'] Tue, 14 Aug 2012 12:00:59 DEBUGqemu-kvm-1.0.1-1.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='qemu-kvm' message='qemu-kvm-1.0.1-1.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'qemu-kvm-tools'] Tue, 14 Aug 2012 12:00:59 DEBUGqemu-kvm-tools-1.0.1-1.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='qemu-kvm-tools' message='qemu-kvm-tools-1.0.1-1.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'vdsm'] Tue, 14 Aug 2012 12:00:59 DEBUGvdsm-4.10.0-6.fc
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Quoting Douglas Landgraf : Hi Sharad, On 08/14/2012 03:16 PM, snmis...@linux.vnet.ibm.com wrote: Hi, Manually uninstall libjpeg and install it. Then try to add it using the GUI. Did you get any bug around this? In my case, I had done some manual deletes and thought that this error was due to something I did. Lets wait and see if this solves Vincent's issue. If it does, then I will open a defect. -Sharad Thanks! -Sharad Quoting Douglas Landgraf : Hi Vicent, On 08/14/2012 06:18 AM, Vincent Miszczak wrote: Hello guys, I have upgraded both my engine and node from Fedora 16 to Fedora 17. I have added the 3.1 release repo to both servers. My engine is working as expected. Now I want to add my node to it, but it fails everytime I try (the GUI says "Install Failed"), despite the installation log on the node show that everything is OK. I've looked to everything I've think about, cannot find why this fails :/ The below logs are all that you have in /tmp/vds_* in the Node side? Could you please attach the log from engine? I am wondering what might happened. On the node : Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject = '192.168.3.24', random_num = 'c8008897-9996-43a0-a712-dbb99d72ed71', rev_num = 'None', installVirtualizationService = 'True', installGlusterService = 'False') Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with RHN/Satellite. Tue, 14 Aug 2012 12:00:58 DEBUG component='RHN_REGISTRATION' status='OK' message='Host properly registered with RHN/Satellite.'/> Tue, 14 Aug 2012 12:00:59 DEBUGAvailable VDSM matches requirements Tue, 14 Aug 2012 12:00:59 DEBUG component='VDSM_MAJOR_VER' status='OK' message='Available VDSM matches requirements'/> Tue, 14 Aug 2012 12:00:59 DEBUGvirtExplorer testing Tue, 14 Aug 2012 12:00:59 DEBUGCPU vendor is GenuineIntel Tue, 14 Aug 2012 12:00:59 DEBUGvirt support in cpu: True, in bios: True Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' processor='Intel' message='Server supports virtualization'/> Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' type='FEDORA' message='Supported platform version'/> Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' version='3.5.1-1.fc17.x86_64' message='Supported kernel version: [~3.5.1~, ~1.f c17.x86_64~]'/> Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'elevator=deadline'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'processor.max_cstate=1'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGCheck required packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'SDL.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGSDL-1.2.14-16.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='SDL.x86_64' message='SDL-1.2.14-16.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'bridge-utils.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGbridge-utils-1.5-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='bridge-utils.x86_64' message='bridge-utils-1.5-3.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'mesa-libGLU.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGmesa-libGLU-8.0.3-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='mesa-libGLU.x86_64' message='mesa-libGLU-8.0.3-3.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'openssl.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGopenssl-1.0.0j-2.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='openssl.x86_64' message='openssl-1.0.0j-2.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'm2crypto.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGm2crypto-0.21.1-8.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='m2crypto.x86_64' message='m2crypto-0.21.1-8.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'rsync.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGrsync-3.0.9-2.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='rsync.x86_64' message='rsync-3.0.9-2.fc17.x86_64 '/> Tue, 14 Aug 2012 12:00:59 DEBUGCheck VDS packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'qemu-kvm'] Tue, 14 Aug 2012 12:00:59 DEBUGqemu-kvm-1.0.1-1.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG status='OK' result='qemu-kvm' message='qemu-kvm-1.0.1-1.fc17.x86_64 '/> Tue, 14 Aug 2012
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Hi guys, I'm finally running my node, but cannot say what was the real problem. To solve it I just flushed everything on node and engine (vdsm*, libvirt*, ovirt*), installed again, run engine-cleanup and engine-setup. Sorry I cannot be more precise, but the engine or node did really log nothing about "Install Failed". The engine should really log about that. I'm still having an issue on my node : Vdsmd does not start at startup. [root@ovirt-node-01 ~]# service vdsmd status Redirecting to /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/vdsmd.service [root@ovirt-node-01 ~]# cat /var/log/boot.log|grep -i vdsm [root@ovirt-node-01 ~]# [root@ovirt-node-01 ~]# journalctl |grep -i vdsm [root@ovirt-node-01 ~] Vdsm log shows nothing. It seems it is really not started. Starting it manually works fine. -Message d'origine- De : users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] De la part de snmis...@linux.vnet.ibm.com Envoyé : mardi 14 août 2012 22:20 À : Douglas Landgraf Cc : users@ovirt.org Objet : Re: [Users] Ovirt 3.1 : node installation fails with no reason Quoting Douglas Landgraf : > Hi Sharad, > > On 08/14/2012 03:16 PM, snmis...@linux.vnet.ibm.com wrote: >> Hi, >> >>Manually uninstall libjpeg and install it. Then try to add it >> using the GUI. >> > Did you get any bug around this? In my case, I had done some manual deletes and thought that this error was due to something I did. Lets wait and see if this solves Vincent's issue. If it does, then I will open a defect. -Sharad > > Thanks! > >> -Sharad >> >> Quoting Douglas Landgraf : >> >>> Hi Vicent, >>> >>> On 08/14/2012 06:18 AM, Vincent Miszczak wrote: >>>> >>>> Hello guys, >>>> >>>> I have upgraded both my engine and node from Fedora 16 to Fedora 17. >>>> >>>> I have added the 3.1 release repo to both servers. >>>> >>>> My engine is working as expected. Now I want to add my node to it, >>>> but it fails everytime I try (the GUI says "Install Failed"), >>>> despite the installation log on the node show that everything is >>>> OK. >>>> >>>> I've looked to everything I've think about, cannot find why this >>>> fails :/ >>>> >>> >>> The below logs are all that you have in /tmp/vds_* in the Node side? >>> Could you please attach the log from engine? >>> I am wondering what might happened. >>> >>> >>>> On the node : >>>> >>>> Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation >>>> >>>> Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject >>>> = '192.168.3.24', random_num = >>>> 'c8008897-9996-43a0-a712-dbb99d72ed71', rev_num = 'None', >>>> >>>> installVirtualizationService = 'True', installGlusterService = >>>> 'False') >>>> >>>> Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks >>>> >>>> Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with >>>> RHN/Satellite. >>>> >>>> Tue, 14 Aug 2012 12:00:58 DEBUG >>> component='RHN_REGISTRATION' status='OK' message='Host properly >>>> registered with RHN/Satellite.'/> >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUGAvailable VDSM matches requirements >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUG >>> status='OK' message='Available VDSM matches requirements'/> >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUGvirtExplorer testing >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUGCPU vendor is GenuineIntel >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUGvirt support in cpu: True, in >>>> bios: True >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUG >>> status='OK' processor='Intel' message='Server supports >>>> virtualization'/> >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUG >>> status='OK' type='FEDORA' message='Supported platform version'/> >>>> >>>> Tue, 14 Aug 2012 12:00:59 DEBUG >>> status='OK' version='3.5.1-1.fc17.x86_64' message='Supported kernel
Re: [Users] Ovirt 3.1 : node installation fails with no reason
On 08/24/2012 07:11 PM, Vincent Miszczak wrote: Hi guys, I'm finally running my node, but cannot say what was the real problem. To solve it I just flushed everything on node and engine (vdsm*, libvirt*, ovirt*), installed again, run engine-cleanup and engine-setup. Sorry I cannot be more precise, but the engine or node did really log nothing about "Install Failed". The engine should really log about that. I'm still having an issue on my node : Vdsmd does not start at startup. [root@ovirt-node-01 ~]# service vdsmd status Redirecting to /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/vdsmd.service [root@ovirt-node-01 ~]# cat /var/log/boot.log|grep -i vdsm [root@ovirt-node-01 ~]# [root@ovirt-node-01 ~]# journalctl |grep -i vdsm [root@ovirt-node-01 ~] Vdsm log shows nothing. It seems it is really not started. Starting it manually works fine. Sounds like the user:group on the vdsm log file are root:root, if yes - it's probably due to first start manually and not by the scripts. -Message d'origine- De : users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] De la part de snmis...@linux.vnet.ibm.com Envoyé : mardi 14 août 2012 22:20 À : Douglas Landgraf Cc : users@ovirt.org Objet : Re: [Users] Ovirt 3.1 : node installation fails with no reason Quoting Douglas Landgraf: Hi Sharad, On 08/14/2012 03:16 PM, snmis...@linux.vnet.ibm.com wrote: Hi, Manually uninstall libjpeg and install it. Then try to add it using the GUI. Did you get any bug around this? In my case, I had done some manual deletes and thought that this error was due to something I did. Lets wait and see if this solves Vincent's issue. If it does, then I will open a defect. -Sharad Thanks! -Sharad Quoting Douglas Landgraf: Hi Vicent, On 08/14/2012 06:18 AM, Vincent Miszczak wrote: Hello guys, I have upgraded both my engine and node from Fedora 16 to Fedora 17. I have added the 3.1 release repo to both servers. My engine is working as expected. Now I want to add my node to it, but it fails everytime I try (the GUI says "Install Failed"), despite the installation log on the node show that everything is OK. I've looked to everything I've think about, cannot find why this fails :/ The below logs are all that you have in /tmp/vds_* in the Node side? Could you please attach the log from engine? I am wondering what might happened. On the node : Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject = '192.168.3.24', random_num = 'c8008897-9996-43a0-a712-dbb99d72ed71', rev_num = 'None', installVirtualizationService = 'True', installGlusterService = 'False') Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with RHN/Satellite. Tue, 14 Aug 2012 12:00:58 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGAvailable VDSM matches requirements Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGvirtExplorer testing Tue, 14 Aug 2012 12:00:59 DEBUGCPU vendor is GenuineIntel Tue, 14 Aug 2012 12:00:59 DEBUGvirt support in cpu: True, in bios: True Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'elevator=deadline'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/sbin/grubby', '--update-kernel', 'DEFAULT', '--args', 'processor.max_cstate=1'] Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUGCheck required packages ... Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'SDL.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGSDL-1.2.14-16.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'bridge-utils.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGbridge-utils-1.5-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'mesa-libGLU.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGmesa-libGLU-8.0.3-3.fc17.x86_64 Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG Tue, 14 Aug 2012 12:00:59 DEBUG['/usr/bin/rpm', '-q', 'openssl.x86_64'] Tue, 14 Aug 2012 12:00:59 DEBUGopenssl-1.0.0j-2.fc17.x86_64 Tue, 1
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Hello Vincent, On 08/24/2012 12:11 PM, Vincent Miszczak wrote: Hi guys, I'm finally running my node, but cannot say what was the real problem. To solve it I just flushed everything on node and engine (vdsm*, libvirt*, ovirt*), installed again, run engine-cleanup and engine-setup. Sorry I cannot be more precise, but the engine or node did really log nothing about "Install Failed". The engine should really log about that. Can you please share the logs with us? I'm still having an issue on my node : Vdsmd does not start at startup. [root@ovirt-node-01 ~]# service vdsmd status Redirecting to /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/vdsmd.service [root@ovirt-node-01 ~]# cat /var/log/boot.log|grep -i vdsm [root@ovirt-node-01 ~]# [root@ovirt-node-01 ~]# journalctl |grep -i vdsm [root@ovirt-node-01 ~] Vdsm log shows nothing. It seems it is really not started. Can you please check: /var/log/vdsm-reg/vdsm-reg.log in the node side as well? Thanks! -- Cheers Douglas ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Hi, I've checked the log file permissions, it looks ok : [root@ovirt-node-01 vdsm]# ls -al /var/log/vdsm/vdsm.log -rw-r--r--. 1 vdsm kvm 5965261 Aug 24 18:01 /var/log/vdsm/vdsm.log -Message d'origine- De : Rami Vaknin [mailto:rvak...@redhat.com] Envoyé : vendredi 24 août 2012 21:09 À : Vincent Miszczak Cc : snmis...@linux.vnet.ibm.com; Douglas Landgraf; users@ovirt.org Objet : Re: [Users] Ovirt 3.1 : node installation fails with no reason On 08/24/2012 07:11 PM, Vincent Miszczak wrote: > Hi guys, > > I'm finally running my node, but cannot say what was the real problem. > To solve it I just flushed everything on node and engine (vdsm*, libvirt*, > ovirt*), installed again, run engine-cleanup and engine-setup. > > Sorry I cannot be more precise, but the engine or node did really log nothing > about "Install Failed". The engine should really log about that. > > I'm still having an issue on my node : > Vdsmd does not start at startup. > > [root@ovirt-node-01 ~]# service vdsmd status Redirecting to > /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop > Server Manager >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) >Active: inactive (dead) >CGroup: name=systemd:/system/vdsmd.service > > [root@ovirt-node-01 ~]# cat /var/log/boot.log|grep -i vdsm > [root@ovirt-node-01 ~]# > > [root@ovirt-node-01 ~]# journalctl |grep -i vdsm > [root@ovirt-node-01 ~] > > Vdsm log shows nothing. It seems it is really not started. > > Starting it manually works fine. Sounds like the user:group on the vdsm log file are root:root, if yes - it's probably due to first start manually and not by the scripts. > > -Message d'origine- > De : users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] De la > part de snmis...@linux.vnet.ibm.com Envoyé : mardi 14 août 2012 22:20 > À : Douglas Landgraf Cc : users@ovirt.org Objet : Re: [Users] Ovirt > 3.1 : node installation fails with no reason > > > Quoting Douglas Landgraf: > >> Hi Sharad, >> >> On 08/14/2012 03:16 PM, snmis...@linux.vnet.ibm.com wrote: >>> Hi, >>> >>> Manually uninstall libjpeg and install it. Then try to add it >>> using the GUI. >>> >> Did you get any bug around this? > In my case, I had done some manual deletes and thought that this error was > due to something I did. Lets wait and see if this solves Vincent's issue. If > it does, then I will open a defect. > > -Sharad >> Thanks! >> >>> -Sharad >>> >>> Quoting Douglas Landgraf: >>> >>>> Hi Vicent, >>>> >>>> On 08/14/2012 06:18 AM, Vincent Miszczak wrote: >>>>> Hello guys, >>>>> >>>>> I have upgraded both my engine and node from Fedora 16 to Fedora 17. >>>>> >>>>> I have added the 3.1 release repo to both servers. >>>>> >>>>> My engine is working as expected. Now I want to add my node to it, >>>>> but it fails everytime I try (the GUI says "Install Failed"), >>>>> despite the installation log on the node show that everything is >>>>> OK. >>>>> >>>>> I've looked to everything I've think about, cannot find why this >>>>> fails :/ >>>>> >>>> The below logs are all that you have in /tmp/vds_* in the Node side? >>>> Could you please attach the log from engine? >>>> I am wondering what might happened. >>>> >>>> >>>>> On the node : >>>>> >>>>> Tue, 14 Aug 2012 12:00:57 DEBUG Start VDS Validation >>>>> >>>>> Tue, 14 Aug 2012 12:00:57 DEBUGEntered VdsValidation(subject >>>>> = '192.168.3.24', random_num = >>>>> 'c8008897-9996-43a0-a712-dbb99d72ed71', rev_num = 'None', >>>>> >>>>> installVirtualizationService = 'True', installGlusterService = >>>>> 'False') >>>>> >>>>> Tue, 14 Aug 2012 12:00:57 DEBUGSetting up Package Sacks >>>>> >>>>> Tue, 14 Aug 2012 12:00:58 DEBUGHost properly registered with >>>>> RHN/Satellite. >>>>> >>>>> Tue, 14 Aug 2012 12:00:58 DEBUG>>>> component='RHN_REGISTRATION' status='OK' message='Host properly >>>>> registered with RHN/Satellite.'/> >>>>> >>>>> Tue, 14 Aug 2012 12:00:59 DEBUG
Re: [Users] Ovirt 3.1 : node installation fails with no reason
Hi, [root@ovirt-node-01 vdsm]# cat /var/log/vdsm-reg/vdsm-reg.log cat: /var/log/vdsm-reg/vdsm-reg.log: No such file or directory [root@ovirt-engine ~]# cat /var/log/vdsm-reg/vdsm-reg.log cat: /var/log/vdsm-reg/vdsm-reg.log: No such file or directory I've not cleanup anything about logs since my new proper re-install. Maybe rpm remove/install have cleanup those files ? -Message d'origine- De : Douglas Landgraf [mailto:dougsl...@redhat.com] Envoyé : vendredi 24 août 2012 22:48 À : Vincent Miszczak Cc : snmis...@linux.vnet.ibm.com; users@ovirt.org Objet : Re: [Users] Ovirt 3.1 : node installation fails with no reason Hello Vincent, On 08/24/2012 12:11 PM, Vincent Miszczak wrote: > Hi guys, > > I'm finally running my node, but cannot say what was the real problem. > To solve it I just flushed everything on node and engine (vdsm*, libvirt*, > ovirt*), installed again, run engine-cleanup and engine-setup. > > Sorry I cannot be more precise, but the engine or node did really log nothing > about "Install Failed". The engine should really log about that. Can you please share the logs with us? > > I'm still having an issue on my node : > Vdsmd does not start at startup. > > [root@ovirt-node-01 ~]# service vdsmd status Redirecting to > /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop > Server Manager >Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) >Active: inactive (dead) >CGroup: name=systemd:/system/vdsmd.service > > [root@ovirt-node-01 ~]# cat /var/log/boot.log|grep -i vdsm > [root@ovirt-node-01 ~]# > > [root@ovirt-node-01 ~]# journalctl |grep -i vdsm > [root@ovirt-node-01 ~] > > Vdsm log shows nothing. It seems it is really not started. Can you please check: /var/log/vdsm-reg/vdsm-reg.log in the node side as well? Thanks! -- Cheers Douglas -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
