[vdsm] Vdsm network functional tests taking slave offline

2014-01-23 Thread David Caro
Hi!


We have been seeing the slave that is used for the network tests getting offline
from time to time, it was dues to vdsm_functional_tests not cleaning up
properly, as removing all the *dummy* interface configurations from
/etc/sysconfig/network-scripts and restarting the network brings it back again.

Can you take a look on why it would not have been cleaning up properly?

the last job that made the host go offline is:
http://jenkins.ovirt.org/job/vdsm_network_functional_tests/1173/console

The number of the dummy interface that was left over was 6 (not sure it's
reelevant, but just in case).

Thanks!

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization RD

Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605



signature.asc
Description: OpenPGP digital signature
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel


Re: [vdsm] Vdsm network functional tests taking slave offline

2014-01-23 Thread Dan Kenigsberg
On Thu, Jan 23, 2014 at 01:17:21PM +0100, David Caro wrote:
 Hi!
 
 
 We have been seeing the slave that is used for the network tests getting 
 offline
 from time to time, it was dues to vdsm_functional_tests not cleaning up
 properly, as removing all the *dummy* interface configurations from
 /etc/sysconfig/network-scripts and restarting the network brings it back 
 again.
 
 Can you take a look on why it would not have been cleaning up properly?
 
 the last job that made the host go offline is:
 http://jenkins.ovirt.org/job/vdsm_network_functional_tests/1173/console
 
 The number of the dummy interface that was left over was 6 (not sure it's
 reelevant, but just in case).

It seems that Jenkins killed the job forcefully, before it had the
chance to clean after itself:

testIPv6ConfigNetwork   FATAL: Unable 
to delete script file /home/jenkins/workspace/tmp/hudson6940503892814963275.sh
hudson.util.IOException2: remote file operation failed: 
/home/jenkins/workspace/tmp/hudson6940503892814963275.sh at 
hudson.remoting.Channel@67a91450:fedora19-vm01
at hudson.FilePath.act(FilePath.java:906)
at hudson.FilePath.act(FilePath.java:883)
at hudson.FilePath.delete(FilePath.java:1268)
...

Does jenkins have the ability to add a job-specific cleanup script, to be
excuted on such occasions? I'm sure Toni could populate it witha couple
of lines to remove remainders?
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel


Re: [vdsm] [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues

2014-01-23 Thread Sandro Bonazzola
Il 23/01/2014 15:21, Brad House ha scritto:
 On 01/23/2014 08:30 AM, Sandro Bonazzola wrote:
 It seems that VDSM is not working on your system.
 Can you attach vdsm logs?

 
 vdsm log is empty
 
 # ls -l /var/log/vdsm/vdsm.log
 -rw-r--r-- 1 root root 0 Jan 20 10:13 /var/log/vdsm/vdsm.log
 
 
 # ps -ef | grep -i vdsm
 root  1628 1  0 09:16 ?00:00:00 /usr/bin/python 
 /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock
 
 
 # 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: failed (Result: start-limit) since Thu 2014-01-23 09:16:38 EST; 
 1min 26s ago
   Process: 2387 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh 
 --post-stop (code=exited, status=0/SUCCESS)
   Process: 2380 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 
 /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE)
   Process: 2328 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh 
 --pre-start (code=exited, status=0/SUCCESS)
 
 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit vdsmd.service 
 entered failed state.
 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service 
 holdoff time over, scheduling restart.
 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Stopping Virtual 
 Desktop Server Manager...
 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Starting Virtual 
 Desktop Server Manager...
 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service 
 start request repeated too quickly, refusing to start.

what's this . It's the first start of vdsmd!


 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Failed to start 
 Virtual Desktop Server Manager.
 Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit vdsmd.service 
 entered failed state.
 
 
 I've attached the supervdsm.log and 
 ovirt-hosted-engine-setup-20140123091611.log incase that's helpful.
 
 Thanks.
 -Brad


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel


Re: [vdsm] [Users] ovirtmgmt vanishes after reboot

2014-01-23 Thread Antoni Segura Puimedon


- Original Message -
 From: Fabian Deutsch fabi...@redhat.com
 To: Francisco Pérez fpere...@gmail.com, VDSM Project Development 
 vdsm-devel@lists.fedorahosted.org
 Cc: us...@ovirt.org
 Sent: Thursday, January 23, 2014 5:12:17 PM
 Subject: Re: [Users] ovirtmgmt vanishes after reboot
 
 Am Donnerstag, den 23.01.2014, 12:34 -0300 schrieb Francisco Pérez:
   Hi. I have configured an ovirt-engine to manage an ovirt node
  succesfully. I have created VM and all runs well but im trying to do
  some escenario testing and i have found an issue.
  
  
   If somehow the ovirt node is rebooted(Power failure, crash, manual
  reboot, etc) when its comes up it does not start the ovirtmgmt
  network. Even if in the ovirt-engine you save network configuration or
  if you execute persist
  on /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt. It tells you it's
  already been added to the configuration.
  
  
   Is this normal behavior after ovirt node's is rebooted? Am i doing
  something wrong?
 
 Hey Francisco,
 
 that sounds like a bug.
 VDSM Devs, how can we debug why the network is not brought up?

Well, we should check if after the reboot 
/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt
and /etc/sysconfig/network-scripts/ifcfg-emX (or whatever the name of the
interface ovirtmgmt sits on is) are present. If vdsmd is started and properly
listening and if that is the case. virsh -r net-list has
vdsm-ovirtmgmt

 
 - fabian
 
 
 ___
 Users mailing list
 us...@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel