Test failed: [ import_template_from_glance ]
Link to suspected patches:
https://gerrit.ovirt.org/#/c/80450/
Link to Job:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2397/
Link to logs:
On Thu, Sep 7, 2017 at 3:59 PM, Miroslava Voglova
wrote:
> It's because upgrade to Postgres 9.5. There is patch that edit README with
> more instructions how to proceed [1].
>
> [1] https://gerrit.ovirt.org/#/c/81536/
>
I'm trying to improve that patch to have it handled
It's because upgrade to Postgres 9.5. There is patch that edit README with
more instructions how to proceed [1].
[1] https://gerrit.ovirt.org/#/c/81536/
On Thu, Sep 7, 2017 at 3:12 PM, Greg Sheremeta wrote:
> Just in case it helps:
>
Just in case it helps:
greg@dauntless:/home/greg/projects/ovirt-engine(master↑1|✔) % noglob rpm
-qa postgres*
postgresql-server-9.6.3-1.fc26.x86_64
postgresql-9.6.3-1.fc26.x86_64
postgresql-libs-9.6.3-1.fc26.x86_64
On Thu, Sep 7, 2017 at 9:10 AM, Jakub Niedermertl
wrote:
>
I have the same issue.
On Thu, Sep 7, 2017 at 2:40 PM, Greg Sheremeta wrote:
> I just rebased and engine wouldn't serve the UI (404) although it looked
> like it started. I tried to run engine setup, and getting:
>
>
I just rebased and engine wouldn't serve the UI (404) although it looked
like it started. I tried to run engine setup, and getting:
greg@dauntless:/home/greg/projects/ovirt-engine(master↑1|✔) %
ovirt_engine_setup
[ INFO ] Stage: Initializing
Setup was run under unprivileged user this
Piotr Kliczewski writes:
> On Thu, Sep 7, 2017 at 11:32 AM, Milan Zamazal wrote:
>> Piotr Kliczewski writes:
>>
>
>>> There few ways I could get there:
>>> 1. Testing some code and creating vdsm and later dropping db
On Thu, Sep 7, 2017 at 11:32 AM, Milan Zamazal wrote:
> Piotr Kliczewski writes:
>
>> There few ways I could get there:
>> 1. Testing some code and creating vdsm and later dropping db and
>> reinstalling the host with "new db"
>> 2. Vms
Piotr Kliczewski writes:
> There few ways I could get there:
> 1. Testing some code and creating vdsm and later dropping db and
> reinstalling the host with "new db"
> 2. Vms provisioned manually.
I.e. outside oVirt? If they are external VMs then it explains why you
Piotr Kliczewski writes:
> On Wed, Sep 6, 2017 at 6:35 PM, Milan Zamazal wrote:
>> Piotr Kliczewski writes:
>>
>
>>> I pulled the latest engine master [1] and I see following exception
>>> below. Is it known issue?
>>
On Wed, Sep 6, 2017 at 6:35 PM, Milan Zamazal wrote:
> Piotr Kliczewski writes:
>
>> I pulled the latest engine master [1] and I see following exception
>> below. Is it known issue?
>
> Piotr, what's the libvirt version on your host? Is the
Tests are not meant to talk to vdsm. You can try this [1]. I wrote it
some time ago but I think that it should work for you.
It is able to use engine's or vdsm's certificates.
Thanks,
Piotr
[1] https://github.com/pkliczewski/vdsm-smoke
On Thu, Sep 7, 2017 at 8:54 AM, pengyixiang
hello, everyone!
I try to run JsonRpcClient to call "Host.getCapabilities" without a running
ovirt engine but with a running vdsm, so I write a case to run this file:
backend/manager/modules/vdsbroker/src/test/java/org/ovirt/engine/core/vdsbroker/jsonrpc/JsonRpcIntegrationTest.java
but
13 matches
Mail list logo