I had succeeded to do the upgrade manually without any problem
This seems to be related to the engine-setup when it calls the task cleaner SPs
Didi, can you have a look ?
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Eli Mesika emes...@redhat.com
Cc:
Hi,
just a quick question:
Would this imply that you need to create
separate bugs to track these solved on master bugs
for the next release?
So you know the fix/feature really hit's the release?
Or how would you track that?
--
Mit freundlichen Grüßen / Regards
Sven Kieske
- Original Message -
From: Lior Vernia lver...@redhat.com
To: devel@ovirt.org, in...@ovirt.org
Sent: Wednesday, January 28, 2015 10:44:44 AM
Subject: Move bugs to ON_QA based on snapshot builds?
Hello everyone,
I wanted to suggest that we automate the change of oVirt 3.6 bug
On 01/28/2015 01:35 PM, Barak Korren wrote:
Sandro,
I remember vaguely that you have to use the 'postgres' user when connecting.
I don't see user information in the URL, maybe it needs to be:
jdbc:postgresql://postgres@localhost/engine_dao_tests
Or maybe:
On 28/01/15 11:53, Sven Kieske wrote:
Hi,
just a quick question:
Would this imply that you need to create
separate bugs to track these solved on master bugs
for the next release?
So you know the fix/feature really hit's the release?
Or how would you track that?
I would stop the
On 01/28, Sahina Bose wrote:
On 01/28/2015 02:58 PM, Sahina Bose wrote:
On 01/28/2015 01:35 PM, Barak Korren wrote:
Sandro,
I remember vaguely that you have to use the 'postgres' user when
connecting.
I don't see user information in the URL, maybe it needs to be:
Hello everyone,
I wanted to suggest that we automate the change of oVirt 3.6 bug status
from MODIFIED to ON_QA based on nightly snapshot builds.
The motivation should be clear: when bugs are fixed on the master
branch, the fix becomes readily available for verification as soon as
the next
Hi,
Development cycle for oVirt 3.5.2 release started and we're now going to
schedule this release.
A release management entry has been added for tracking the schedule of 3.5.2 [0]
A bug tracker [1] has been created and currently has no open blockers.
Maintainers:
- Please be sure that 3.5
On 28/01/15 11:51, Sahina Bose wrote:
On 01/28/2015 02:58 PM, Sahina Bose wrote:
On 01/28/2015 01:35 PM, Barak Korren wrote:
Sandro,
I remember vaguely that you have to use the 'postgres' user when
connecting.
I don't see user information in the URL, maybe it needs to be:
Hi,
I haven't many news for 3.6 this week:
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external project schedules
On 28/01/15 13:20, Dan Kenigsberg wrote:
I wonder if Vdsm should keep the
last tx/rx used by this VM so Engine can collect it, and charge the VM
properly.
From the user perspective:
yes! nice feature!
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service
I see you rebuilt and it passed (though it failed after the merge).
I'll look into that last failure.
One seems like a connectivity issue between the slave and artifactory (failed
to fetch the artifact) but the artifact is there now,, I'm rerunning.
Looking into the unit tests issue.
On
No objections, patch looks great and works. Moving on.
Thanks all :)
Greg
- Original Message -
From: Greg Sheremeta gsher...@redhat.com
To: devel@ovirt.org
Cc: Juan Hernández jhern...@redhat.com
Sent: Tuesday, January 20, 2015 10:30:44 AM
Subject: Re: [ovirt-devel] CORS enabled for
Il 29/01/2015 09:44, Yair Zaslavsky ha scritto:
- Original Message -
From: Eli Mesika emes...@redhat.com
To: Yedidyah Bar David d...@redhat.com
Cc: devel@ovirt.org, Yair Zaslavsky yzasl...@redhat.com, infra
in...@ovirt.org, Sandro Bonazzola
sbona...@redhat.com
Sent: Wednesday,
14 matches
Mail list logo
