Here is the updated schedule for oVirt 3.5.0.
These are tentative planning dates and may change:
General availability: 2014-08-04
RC Build: 2014-07-15
oVirt 3.5 Second Test Day: 2014-07-01
Branching - Beta release: 2014-06-16
oVirt 3.5 First Test Day:
Hi,
just found this in supervdsm.log:
MainProcess|storageRefresh::DEBUG::2014-03-19
17:34:57,752::iscsi::390::Storage.Misc.excCmd::(forceScsiScan) '/bin/dd
of=/sys/class/scsi_host/host0/scan' (cwd None)
MainProcess|storageRefresh::DEBUG::2014-03-19
Hi,
I just stumbled upon a defunct supervdsm process:
root 2824 2815 0 Apr04 ?00:01:01 /usr/bin/python
/usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock
--pidfile /var/run/vdsm/supervdsmd.pid
qemu 31321 2824 0 May02 ?00:00:00 [supervdsmServer]
On Fri, May 09, 2014 at 01:04:18PM +, Sven Kieske wrote:
Hi,
just found this in supervdsm.log:
MainProcess|storageRefresh::DEBUG::2014-03-19
17:34:57,752::iscsi::390::Storage.Misc.excCmd::(forceScsiScan) '/bin/dd
of=/sys/class/scsi_host/host0/scan' (cwd None)
I don't see anything in supervdsm.log
just one error at all related to a vm network.
in vdsm log I got these timeouts repeatedly:
Thread-25::DEBUG::2014-05-02
09:02:43,652::fileSD::222::Storage.Misc.excCmd::(getReadDelay) '/bin/dd
iflag=direct
On Fri, May 09, 2014 at 02:39:29PM +, Sven Kieske wrote:
I don't see anything in supervdsm.log
Still, I believe that the bug is worth reopening - it's a process leak,
and it should be avoided. I believe that it can be easily solved by
adding zombiereaper to supervdsm.
just one error at
Well, you called for it:
https://bugzilla.redhat.com/show_bug.cgi?id=1096312
Have a nice weekend!
I also attached myself to the other BZ, please reopen.
Am 09.05.2014 17:05, schrieb Dan Kenigsberg:
This is unrelated - that's Vdsm complaining about guest agents not
heart-beating. It's log noise
