Its also pending when/if the 4.3 suites are ready and working,
I think they are still WIP.
On Thu, Feb 28, 2019 at 9:50 AM Yedidyah Bar David wrote:
> On Wed, Feb 27, 2019 at 9:56 PM Nir Soffer wrote:
> >
> > When starting manual OST job, we can select engine version.
> > The available option
Hi,
We have a failure on the project in basic suite, master branch. The recent
failure was in patch:
https://gerrit.ovirt.org/#/c/98087/1 - Add pre-seed for ovirt-web-ui
CQ is pointing at the below as the root cause (which was merged a while
back):
https://gerrit.ovirt.org/#/c/97491/ - Add pre-se
Hi,
The test failed due to not finding master storage domain
I am seeing a build of engine that passed so its possible that this is
related to the random failures we have been having on other tests but since
the change reported is storage related, can you please review the logs to
see if anything
Hi,
On yesterday's vdsm weekly call, we were discussing the need of making
Python 3 vdsm RPM packages.
Some facts:
- it doesn't make a lot sense to spend much time on trying to package
everything - it's completely impossible i.e. to run vdsm without having
'sanlock' module
- our current vd
The oVirt Project is pleased to announce the general availability of oVirt
4.3.1, as of February 26th, 2019.
This update is the first in a series of stabilization updates to the 4.3
series.
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS
On Thu, Feb 28, 2019 at 12:01 PM Dafna Ron wrote:
> Hi,
>
> The test failed due to not finding master storage domain
> I am seeing a build of engine that passed so its possible that this is
> related to the random failures we have been having on other tests but since
> the change reported is stor
On Thu, Feb 28, 2019 at 1:06 PM Marcin Sobczyk wrote:
> Hi,
>
> On yesterday's vdsm weekly call, we were discussing the need of making
> Python 3 vdsm RPM packages.
>
> Some facts:
>
> - it doesn't make a lot sense to spend much time on trying to package
> everything - it's completely impossible
On Thu, Feb 28, 2019 at 1:07 PM Marcin Sobczyk wrote:
>
> Hi,
>
> On yesterday's vdsm weekly call, we were discussing the need of making
> Python 3 vdsm RPM packages.
>
> Some facts:
>
> - it doesn't make a lot sense to spend much time on trying to package
> everything - it's completely impossible
On 2/28/19 12:30 PM, Dan Kenigsberg wrote:
On Thu, Feb 28, 2019 at 1:07 PM Marcin Sobczyk wrote:
Hi,
On yesterday's vdsm weekly call, we were discussing the need of making
Python 3 vdsm RPM packages.
Some facts:
- it doesn't make a lot sense to spend much time on trying to package
everythin
On Thu, Feb 28, 2019 at 1:30 PM Dan Kenigsberg wrote:
> On Thu, Feb 28, 2019 at 1:07 PM Marcin Sobczyk
> wrote:
> >
> > Hi,
> >
> > On yesterday's vdsm weekly call, we were discussing the need of making
> > Python 3 vdsm RPM packages.
> >
> > Some facts:
> >
> > - it doesn't make a lot sense to
On 2/28/19 12:30 PM, Dan Kenigsberg wrote:
I am afraid of fresh starts; I'd very much prefer to start from the
sh*tty thing we have, and evolve it. A lot of time, re-writing a piece
of software is tempting, but existing code is imbued with knowledge of
past problems, which is often forgotten when
Marcin Sobczyk writes:
> Hi,
>
> On yesterday's vdsm weekly call, we were discussing the need of making
> Python 3 vdsm RPM packages.
>
> Some facts:
>
> - it doesn't make a lot sense to spend much time on trying to package
> everything - it's completely impossible i.e. to run vdsm without
> havi
Thanks Nir.
I will skip the test until the bug is fixed.
Thanks,
Dafna
On Thu, Feb 28, 2019 at 11:12 AM Nir Soffer wrote:
> On Thu, Feb 28, 2019 at 12:01 PM Dafna Ron wrote:
>
>> Hi,
>>
>> The test failed due to not finding master storage domain
>> I am seeing a build of engine that passed s
Hi,
We are still getting random failures on this test.
Is anyone working on this?
Thanks,
Dafna
On Wed, Feb 27, 2019 at 9:10 PM Nir Soffer wrote:
> On Wed, Feb 27, 2019 at 4:31 PM Dan Kenigsberg wrote:
>
>> HTH
>>
>>
>> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13163/art
ovirt-engine-nodejs-modules is just for frontend web javascript stuff, and
it has no logic -- it's a giant tarball of modules. There's no way it could
be related to storage failures in OST.
So, false positive? Not sure why it won't pass though.
Greg
On Thu, Feb 28, 2019 at 4:52 AM Dafna Ron wro
Hi,
I've posted a series of patches:
https://gerrit.ovirt.org/#/q/topic:py3-rpm-packages+(status:open+OR+status:merged)
They do a couple of things:
* add an '--enable-python3-build' argument to 'autogen.sh'
* modify 'Makefile.am' so it uses either 'vdsm.spec.in' or
'vdsm-py3.spec.in' fil
On Thu, Feb 28, 2019 at 11:52 AM Dafna Ron wrote:
> Hi,
>
> We have a failure on the project in basic suite, master branch. The recent
> failure was in patch:
> https://gerrit.ovirt.org/#/c/98087/1 - Add pre-seed for ovirt-web-ui
>
> CQ is pointing at the below as the root cause (which was merged
17 matches
Mail list logo
