Yes, postgresql 9.2 JDBC drivers are the only working and supported JDBC
drivers. Also please be aware that we test and only PostgreSQL 9.2 for
oVirt, so there may be other issues with newer versions.
On Tue, May 23, 2017 at 11:15 PM, Yedidyah Bar David
wrote:
> On Wed, May
And tasks are not available through the REST API, I think.
> Le 24 mai 2017 à 11:07, Martin Perina a écrit :
>
> Hi,
>
> there is no direct link between sessions and commands executed by them in UI.
> You can take a look into Tasks tab in bottom right corner, if there are
AFAIK content of Tasks tab in webadmin should be available under
/ovirt-engine/api/jobs , but sessions are not exposed to API.
On Wed, May 24, 2017 at 11:58 AM, Fabrice Bacchella <
fabrice.bacche...@orange.fr> wrote:
> And tasks are not available through the REST API, I think.
>
> Le 24 mai 2017
I'm playing with perf in vm and getting inconsistent result. But I wonder if
it's a kvm, ovirt or hardware problem.
On a ovirt's vm:
$ sudo perf list | grep Hardware | wc -l
1
$ lscpu
...
Model name:Intel Core Processor (Haswell, no TSX)
On another ovirt's vm:
$ sudo perf list |
>
> Le 24 mai 2017 à 16:26, Yedidyah Bar David a écrit :
>>
>> A good solution usually used by java app is to provide the need jars. That
>> the purpose of maven like tools.
>>
>
> We can also simply add to the spec file '< 9.3' or something like that,
> until we fix the
Thanks, that's what we've put in place too
Logan
>
> On May 24, 2017 at 2:20 AM Fabrice Bacchella
> wrote:
>
> In /etc/yum.repos.d/pgdg-94-centos.repo, I added :
>
> [pgdg94]
> ...
> exclude=postgresql-jdbc
>
> > >
> > Le
On Wed, May 24, 2017 at 5:04 PM, Fabrice Bacchella
wrote:
>
> Le 24 mai 2017 à 15:25, supp...@jac-properties.com a écrit :
>
> Which makes sense seeing as that's what Red Hat officially supports. It
> just made sense for our infrastructure to put it on our postgres
Which makes sense seeing as that's what Red Hat officially supports. It just
made sense for our infrastructure to put it on our postgres cluster that is
running 9.5.x. Unfortunately things like this happen sometimes when running a
slightly unsupported infrastructure.
Is this worth putting
> Le 24 mai 2017 à 15:25, supp...@jac-properties.com a écrit :
>
> Which makes sense seeing as that's what Red Hat officially supports. It just
> made sense for our infrastructure to put it on our postgres cluster that is
> running 9.5.x. Unfortunately things like this happen sometimes when
Hi everyone, i've just subscribed to the maling list, I was going to ask
one thing about ovirt in the IRC channel but no one was there.
I've been using ovirt since 3.1, today we have one enviroment with 1 Ovirt
Engine and 3 baremetal that we use for virtualization running the Ovirt
3.6.3. We have
Hi,
I setup an ovirt hosted enine, in only one server with local gluster bricks.
When running a MS SQL 2012 process to rebuild a data base, which take around 4
hours, after a while the VM is paused with the error:
vm has been paused due to unknown storage
The VM disk is in Thin provision
On Wed, May 24, 2017 at 8:28 PM, Odilon Junior
wrote:
> Hi everyone, i've just subscribed to the maling list, I was going to ask
> one thing about ovirt in the IRC channel but no one was there.
>
Welcome to the oVirt community!
>
> I've been using ovirt since 3.1,
>
Ran `make clean install-dev` and the process freezes at:
[INFO] weaveinfo Join point 'constructor-execution(void
com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))'
in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
(ControlFlowAnalyzer.java:905) advised
On Thu, May 25, 2017 at 6:05 AM, Leni Kadali Mutungi
wrote:
> Ran `make clean install-dev` and the process freezes at:
> [INFO] weaveinfo Join point 'constructor-execution(void
> com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))'
> in
In /etc/yum.repos.d/pgdg-94-centos.repo, I added :
[pgdg94]
...
exclude=postgresql-jdbc
> Le 23 mai 2017 à 23:06, supp...@jac-properties.com a écrit :
>
> Wow, that looks almost exactly like what we're seeing.
>
> Unfortunately, downgrading from postgresql-jdbc-42.1.1 to 42.0.0, restarting
>
No one has the answer ?
> Le 18 mai 2017 à 09:58, Sandro Bonazzola a écrit :
>
> Adding some people who may be able to answer
>
> On Wed, May 17, 2017 at 11:45 AM, Fabrice Bacchella
> > wrote:
> I'm back
Mostly read in threads and docs that the upgrade path should be 3.6.x ->
4.0.x -> 4.1.x
I did it that way and it did work perfectly.
Rgds,
Arsène
On 05/24/2017 10:52 AM, Yaniv Kaul wrote:
On Wed, May 24, 2017 at 5:36 AM, Richard Chan
17 matches
Mail list logo