hello:
Ovirt-engine-4.0.2.6 is installed.
but the 'ISO_DOMAIN' storage space always smaller than 1G.
the status always 'Unattached'.
That's why?
Thank you !
330AF182@B592FE2F.D5B1EC57
Description: Binary data
___
Devel mailing list
De
Evgheni,
Can you try switching the current RAM drive with zram?
On Wed, Sep 28, 2016 at 11:43 PM, Nir Soffer wrote:
> On Wed, Sep 28, 2016 at 11:39 PM, Yaniv Kaul wrote:
> > On Sep 28, 2016 11:37 PM, "Nir Soffer" wrote:
> >>
> >> On Wed, Sep 28, 2016 at 11:20 PM, Nir Soffer
> wrote:
> >> > On
On Wed, Sep 28, 2016 at 11:39 PM, Yaniv Kaul wrote:
> On Sep 28, 2016 11:37 PM, "Nir Soffer" wrote:
>>
>> On Wed, Sep 28, 2016 at 11:20 PM, Nir Soffer wrote:
>> > On Wed, Sep 28, 2016 at 10:31 PM, Barak Korren
>> > wrote:
>> >> The CI setup did not change recently.
>> >
>> > Great
>> >
>> >> Al
On Sep 28, 2016 11:37 PM, "Nir Soffer" wrote:
>
> On Wed, Sep 28, 2016 at 11:20 PM, Nir Soffer wrote:
> > On Wed, Sep 28, 2016 at 10:31 PM, Barak Korren
wrote:
> >> The CI setup did not change recently.
> >
> > Great
> >
> >> All standard-CI jobs run inside mock (chroot) which is stored on top
>
On Wed, Sep 28, 2016 at 11:20 PM, Nir Soffer wrote:
> On Wed, Sep 28, 2016 at 10:31 PM, Barak Korren wrote:
>> The CI setup did not change recently.
>
> Great
>
>> All standard-CI jobs run inside mock (chroot) which is stored on top
>> of a regular FS, so they should not be affected by the slave
On Wed, Sep 28, 2016 at 10:31 PM, Barak Korren wrote:
> The CI setup did not change recently.
Great
> All standard-CI jobs run inside mock (chroot) which is stored on top
> of a regular FS, so they should not be affected by the slave OS at all
> as far as FS settings go.
>
> But perhaps some sla
The CI setup did not change recently.
All standard-CI jobs run inside mock (chroot) which is stored on top
of a regular FS, so they should not be affected by the slave OS at all
as far as FS settings go.
But perhaps some slave-OS/mock-OS combination is acting strangely, so
could you be more speci
Hi all,
It seems that the CI setup has changed, and /var/tmp is using now tempfs.
This is not compatible with vdsm tests, assuming that /var/tmp is a real file
system. This is the reason we do not use /tmp.
We have lot of storage tests using directio, and directio cannot work on
tempfs.
Please
Hi everyone.
A branch for 4.0.5 was created today (ovirt-engine-4.0.5), please push your
4.0.5 patches to that branch as well as the 4.0 branch.
It was branched from the 4.0 branch at 10:30 IST so everything that was
merged before that is included in this branch.
Tal.
___
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start in 40 minutes.
If you're a maintainer for any of the projects included in oVirt
distribution and you have changes in your package ready to be released
please:
- bump version and release to be GA ready
- tag you
10 matches
Mail list logo