Re: [ovirt-users] IP Address Stealing

2016-08-03 Thread Subhendu Ghosh
Not built into ovirt AFAIK,  but an ebtables rule can allow you to filter out 
mac+ip combinations 

Look at the anti-spoofing rules on ebtables.netfilter.org

It doesn't prevent the user adding it in the vm, but the infrastructure blocks 
it's usage.


From: Bill Bill 
Sent: Aug 3, 2016 22:40
To: users@ovirt.org
Subject: [ovirt-users] IP Address Stealing

Hello,

 

It is possible to prevent a VM from adding an IP? For example, if we provision 
a VM with one IP, if the user has root access they can simply add random IP’s 
from within the same range as sub interfaces: eth0:0 eth0:1 eth0:2 so on and so 
forth.

 

Subnetting is not ideal in this situation because it’s a huge waste of IP space.

 ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] IP Address Stealing

2016-08-03 Thread Bill Bill
Hello,

It is possible to prevent a VM from adding an IP? For example, if we provision 
a VM with one IP, if the user has root access they can simply add random IP’s 
from within the same range as sub interfaces: eth0:0 eth0:1 eth0:2 so on and so 
forth.

Subnetting is not ideal in this situation because it’s a huge waste of IP space.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ovirt4.0.1 and new node, migration fails

2016-08-03 Thread Bill James

opened bug 1363900.
It also includes recent logs from all 3 servers.

Also tried updating vdsm to 4.18.10-1 and restarted ovirt-engine.
No change in results.

I can migrate VMs to new node but not initially assign VMs to that node.


On 07/29/2016 09:31 AM, Bill James wrote:
ok, I will raise a bug. Yes it is very frustrating just having button 
not work without explanation.
I don't know if this is related, the new host that I am having 
troubles with is running 4.0.1.1-1,

other other host is running 4.0.0.6-1

I was planning on migrating VMs then upgrade the older host.
Also Cluster is still in 3.6 mode, also waiting for upgrade of older 
node.

All storage domains are on older node, its the NFS server.


hmm, just retried migration so I could get vdsm logs from both hosts.
1 VM worked, the other 3 failed.
And I still can't assign VMs to new node.

VM that worked: f4cd4891-977d-44c2-8554-750ce86da7c9

Not sure what's special about it.
It and 45f4f24b-2dfa-401b-8557-314055a4662c are clones from same 
template.



Attaching logs from 2 nodes and engine now.



On 7/29/16 4:00 AM, Michal Skrivanek wrote:

On 28 Jul 2016, at 18:37, Bill James  wrote:

I'm trying to test out ovirt4.0.1.
I added a new hardware node to the cluster. Its status is Up.
But for some reason when I create a new VM and try to select 
"Specific Host" the radio button doesn't let me select it so I can't 
assign a VM to new node.

please raise that as a bug if there is no explanation why


When I try to migrate a VM to new node it fails with:

MigrationError: Domain not found: no domain with matching uuid 
'45f4f24b-2dfa-401b-8557-314055a4662c'



What did I miss?
for migration issues you always need to include vdsm logs from both 
source and destination host. Hard to say otherwise. Anything special 
about your deployment?



ovirt-engine-4.0.1.1-1.el7.centos.noarch
vdsm-4.18.6-1.el7.centos.x86_64

storage is NFS.

Attached logs.

___ 


Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to login to the WEB UI

2016-08-03 Thread Martin Perina
On Wed, Aug 3, 2016 at 5:25 PM, Fabrice Bacchella <
fabrice.bacche...@icloud.com> wrote:

> Next step :
>
> The UI says, even with a restarted navigator:
>
> org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code
> 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null') at [Source: java.io.StringReader@74749f78; line: 3,
> column: 2]
>

​I haven't seen this error before, could you please share server.log and
engine.log?
​


>
>
> I shift-reload, got a welcome screen, click on "Administration portal". I
> then got a warning. The vhost for ovirt is "ovirt.mydomain", but I got a
> redirect to:
>
> https://ovirt.mydomain/ovirt-engine/webadmin/sso/login?_url=https%3A%2F%2Fovirt.mydomain%2Fovirt-engine%2Fwebadmin%2F%3Flocale%3Den_US=en_US
> that then redirect to:
>
> https://realhost.mydomain:443/ovirt-engine/sso/oauth/authorize?client_id=ovirt-engine-core_type=code_uri=https%3A%2F%2Fovirt.mydomain%3A443%2Fovirt-engine%2Fwebadmin%2Fsso%2Foauth2-callback=ovirt-app-admin+ovirt-app-portal+ovirt-ext%3Dauth%3Asequence-priority%3D%7E=5ku3vXkfb10
>
> And it fail with again with still:
> org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code
> 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null') at [Source: java.io.StringReader@328a4512; line: 3,
> column: 2]​


> Many requests were send to ovirt.mydomain, but just one to
> realhost.mydomain:443, I don't know why.
>

​You need to have correctly set up engine FQDN and it has to be resolvable.
If you don't have correctly set engine FQDN, you can fix that ​
​using ovirt​-engine-rename tool, more info can be found at:

https://www.ovirt.org/documentation/how-to/networking/changing-engine-hostname/

Also be aware that you need to use that engine FQDN to access oVirt 4.0


> I didn't ask for any SSO, I already use my own (CAS), it was working well
> and the update never ask for activating something new.
>

​This is one of the oVirt 4.0 features​, we have implemented OAUTH SSO for
all engine parts: webadmin, userportal and restapi. If you are using CAS
(althought it's officially supported by oVirt), that probably means you
have configured cas authentication on Apache, passing authenticated
username using aaa-misc as authn extension and aaa-ldap as authz extension
(to get group memberships for authenticated user). If that's true then
please take a look at

https://bugzilla.redhat.com/show_bug.cgi?id=1342192

there are some changes on Apache configuration (the bug is for kerberos,
but I suspect similar config is needed also for cas module in apache).


>
> > Le 3 août 2016 à 15:09, Martin Perina  a écrit :
> >
> > Hi,
> > please follow steps as described in BZ:
> >
> > 1. Create /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf (you
> may choose different filename but it has to end with '.conf' suffix) with
> following content:
> >
> >   ENGINE_HTTPS_PKI_TRUST_STORE=""
> >   ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD=" keystore>"
> >
> > 2. Restart the engine
> >
> > If the above doesn't work please attach server.log/engine.log
> >
> > Thanks
> >
> > Martin Perina
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Migrate machines in unknown state?

2016-08-03 Thread Nicolás

Hi,

We're running oVirt 4.0.1 and today I found out that one of our hosts 
has all its VMs in an unknown state. I actually don't know how (and 
when) did this happen, but I'd like to restore service possibly without 
turning off these machines. The host is up, the VMs are up, 'qemu' 
process exists, no errors, it's just the VMs running on it that have a 
'?' where status is defined.


Is it safe in this case to simply modify database and set those VM's 
status to 'up'? I remember having to do this a time ago when we faced 
storage issues, it didn't break anything back then. If not, is there a 
"safe" way to migrate those VMs to a different host and restart the host 
that marked them as unknown?


Thanks.

Nicolás

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to login to the WEB UI

2016-08-03 Thread Fabrice Bacchella
Next step :

The UI says, even with a restarted navigator:

org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): 
expected a valid value (number, String, array, object, 'true', 'false' or 
'null') at [Source: java.io.StringReader@74749f78; line: 3, column: 2] 


I shift-reload, got a welcome screen, click on "Administration portal". I then 
got a warning. The vhost for ovirt is "ovirt.mydomain", but I got a redirect to:
https://ovirt.mydomain/ovirt-engine/webadmin/sso/login?_url=https%3A%2F%2Fovirt.mydomain%2Fovirt-engine%2Fwebadmin%2F%3Flocale%3Den_US=en_US
that then redirect to:
https://realhost.mydomain:443/ovirt-engine/sso/oauth/authorize?client_id=ovirt-engine-core_type=code_uri=https%3A%2F%2Fovirt.mydomain%3A443%2Fovirt-engine%2Fwebadmin%2Fsso%2Foauth2-callback=ovirt-app-admin+ovirt-app-portal+ovirt-ext%3Dauth%3Asequence-priority%3D%7E=5ku3vXkfb10

And it fail with again with still:
org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): 
expected a valid value (number, String, array, object, 'true', 'false' or 
'null') at [Source: java.io.StringReader@328a4512; line: 3, column: 2] 

Many requests were send to ovirt.mydomain, but just one to 
realhost.mydomain:443, I don't know why.

I didn't ask for any SSO, I already use my own (CAS), it was working well and 
the update never ask for activating something new.  
  


> Le 3 août 2016 à 15:09, Martin Perina  a écrit :
> 
> Hi,
> please follow steps as described in BZ:
> 
> 1. Create /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf (you may 
> choose different filename but it has to end with '.conf' suffix) with 
> following content:
> 
>   ENGINE_HTTPS_PKI_TRUST_STORE=""
>   ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD=""
> 
> 2. Restart the engine
> 
> If the above doesn't work please attach server.log/engine.log
> 
> Thanks
> 
> Martin Perina

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to login to the WEB UI

2016-08-03 Thread Martin Perina
Hi,
please follow steps as described in BZ:

1. Create /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf (you
may choose different filename but it has to end with '.conf' suffix) with
following content:

  ENGINE_HTTPS_PKI_TRUST_STORE=""
  ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD=""

2. Restart the engine

If the above doesn't work please attach server.log/engine.log

Thanks

Martin Perina


On Wed, Aug 3, 2016 at 2:49 PM, Fabrice Bacchella <
fabrice.bacche...@icloud.com> wrote:

> Indeed, the certificate for the web interface is not coming from ovirt's
> internal PKI, but from our own internal one.
>
> I have a custom trust store not located in /etc/pki/java/cacerts, I did
> try to add ENGINE_PROPERTIES="${ENGINE_PROPERTIES}
> javax.net.ssl.trustStore=.../allmyca.jks
> javax.net.ssl.trustStorePassword=''" in a file in
> /etc/ovirt-engine/engine.conf.d but it didn't help.
>
> Can I add them in /etc/pki/ovirt-engine/.truststore ?
> >
> > Le 3 août 2016 à 13:22, Martin Perina  a écrit :
> >
> > Hi,
> >
> > are you using HTTPS certificate signed by external CA? If so please
> follow steps described in Doc Text of
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1336838
> >
> > Thanks
> >
> > Martin Perina
> >
> >
> > On Wed, Aug 3, 2016 at 1:18 PM, Fabrice Bacchella <
> fabrice.bacche...@icloud.com> wrote:
> > After the upgrad, I'm unable to log in, I'm getting the following error:
> >
> >  sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path
> >  to requested target
> >
> >
> > Where should I look to correct that ?
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to login to the WEB UI

2016-08-03 Thread Fabrice Bacchella
Indeed, the certificate for the web interface is not coming from ovirt's 
internal PKI, but from our own internal one.

I have a custom trust store not located in /etc/pki/java/cacerts, I did try to 
add ENGINE_PROPERTIES="${ENGINE_PROPERTIES} 
javax.net.ssl.trustStore=.../allmyca.jks javax.net.ssl.trustStorePassword=''" 
in a file in /etc/ovirt-engine/engine.conf.d but it didn't help.

Can I add them in /etc/pki/ovirt-engine/.truststore ?
> 
> Le 3 août 2016 à 13:22, Martin Perina  a écrit :
> 
> Hi,
> 
> are you using HTTPS certificate signed by external CA? If so please follow 
> steps described in Doc Text of
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1336838
> 
> Thanks
> 
> Martin Perina
> 
> 
> On Wed, Aug 3, 2016 at 1:18 PM, Fabrice Bacchella 
>  wrote:
> After the upgrad, I'm unable to log in, I'm getting the following error:
> 
>  sun.security.validator.ValidatorException: PKIX path building failed: 
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
> valid certification path
>  to requested target
> 
> 
> Where should I look to correct that ?
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread nicola.gentile.to

Il 03/08/2016 14:04, Yedidyah Bar David ha scritto:
On Wed, Aug 3, 2016 at 2:51 PM, nicola.gentile.to 
 > wrote:


Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:

On Wed, Aug 3, 2016 at 2:30 PM,nicola.gentile.to 
   wrote:

Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:

Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:

After install you have to make a dependency so that VDSM Broker starts after
NFS Server

In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service \
   nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to keep
in mind...

Hi,

I try to upgrade from ovirt 3.6.7 to 4.0.1.

I follow this steps:

1. Update repository for 4.0.1

2. Disable old repository 3.6.7

3. run: yum update "ovirt-engine-setup*"

now an error occured:

yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
  * base:artfiles.org 
  * extras:ba.mirror.garr.it 
  * ovirt-4.0:ftp.nluug.nl 
  * ovirt-4.0-epel:epel.besthosting.ua 
  * updates:ba.mirror.garr.it 
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread Yedidyah Bar David
On Wed, Aug 3, 2016 at 2:51 PM, nicola.gentile.to <
nicola.gentile...@gmail.com> wrote:

> Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:
>
> On Wed, Aug 3, 2016 at 2:30 PM, 
> nicola.gentile.to  
> wrote:
>
> Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
>
> Two final steps I've done that are only necessary in my environment, where
> the host itslef is providing the NFS service for storage domains:
>
> After install you have to make a dependency so that VDSM Broker starts after
> NFS Server
>
> In /usr/lib/systemd/system/ovirt-ha-broker.service
>
> Added in section  [Unit] the line:
>
> After=nfs-server.service
>
> Also, for vdsmd service, in file vdsmd.service changed from:
>
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service
>
> to:
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service \
>   nfs-server.service
>
> NOTE: the files will be overwritten by future updates, so you have to keep
> in mind...
>
> Hi,
>
> I try to upgrade from ovirt 3.6.7 to 4.0.1.
>
> I follow this steps:
>
> 1. Update repository for 4.0.1
>
> 2. Disable old repository 3.6.7
>
> 3. run: yum update "ovirt-engine-setup*"
>
> now an error occured:
>
> yum update "ovirt-engine-setup*"
> Plugin abilitati:fastestmirror, langpacks, versionlock
> Repository centos-ovirt36 is listed more than once in the configuration
> Repository virtio-win-stable is listed more than once in the configuration
> Loading mirror speeds from cached hostfile
>  * base: artfiles.org
>  * extras: ba.mirror.garr.it
>  * ovirt-4.0: ftp.nluug.nl
>  * ovirt-4.0-epel: epel.besthosting.ua
>  * updates: ba.mirror.garr.it
> Risoluzione dipendenze
> --> Esecuzione del controllo di transazione
> ---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
> per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
> pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> --> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
> ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
> ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> --> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
> otopi-java-1.4.2-1.el7.centos.noarch
> ---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
> per essere un aggiornamento
> ---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> ---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> --> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> va in conflitto con ovirt-engine-reports-setup < 4.0.0
> --> Risoluzione delle dipendenze completata
> Errore: ovirt-engine-setup-base conflicts with
> ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
>  Si può 

[ovirt-users] [ANN] oVirt 4.0.2 Third Release Candidate is now available

2016-08-03 Thread Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the Third
Release Candidate of oVirt 4.0.2 for testing, as of August 3rd, 2016.

This release is available now for:
* Fedora 23 (tech preview)
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later

This release supports Hypervisor Hosts running:
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
* Fedora 23 (tech preview)
* oVirt Next Generation Node 4.0

This is pre-release software. Please take a look at our community page[1]
to know how to ask questions and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This pre-release should not to be used in production.

This update is the third release candidate of the second in a series of
stabilization updates to the 4.0 series.
4.0.2 brings 21 enhancements and nearly 200 bugfixes, including 91 high or
urgent severity fixes, on top of oVirt 4.0 series
See the release notes [3] for installation / upgrade instructions and a
list of new features and bugs fixed.

Notes:
* A new oVirt Live ISO is available. [4]
* A new oVirt Next Generation Node will be available soon [4].
* A new oVirt Engine Appliance is already available.
* Mirrors[5] might need up to one day to synchronize.

Additional Resources:
* Read more about the oVirt 4.0.2 release highlights:
http://www.ovirt.org/release/4.0.2/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/

[1] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.0.2/
[4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/
[5] http://www.ovirt.org/Repository_mirrors#Current_mirrors


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread nicola.gentile.to

Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:

On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
 wrote:

Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:

Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:

After install you have to make a dependency so that VDSM Broker starts after
NFS Server

In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
   supervdsmd.service sanlock.service vdsm-network.service \
   nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to keep
in mind...

Hi,

I try to upgrade from ovirt 3.6.7 to 4.0.1.

I follow this steps:

1. Update repository for 4.0.1

2. Disable old repository 3.6.7

3. run: yum update "ovirt-engine-setup*"

now an error occured:

yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
  * base: artfiles.org
  * extras: ba.mirror.garr.it
  * ovirt-4.0: ftp.nluug.nl
  * ovirt-4.0-epel: epel.besthosting.ua
  * updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
--> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
va in conflitto con ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
  Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread Yedidyah Bar David
On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
 wrote:
> Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
>
> Two final steps I've done that are only necessary in my environment, where
> the host itslef is providing the NFS service for storage domains:
>
> After install you have to make a dependency so that VDSM Broker starts after
> NFS Server
>
> In /usr/lib/systemd/system/ovirt-ha-broker.service
>
> Added in section  [Unit] the line:
>
> After=nfs-server.service
>
> Also, for vdsmd service, in file vdsmd.service changed from:
>
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service
>
> to:
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>   supervdsmd.service sanlock.service vdsm-network.service \
>   nfs-server.service
>
> NOTE: the files will be overwritten by future updates, so you have to keep
> in mind...
>
> Hi,
>
> I try to upgrade from ovirt 3.6.7 to 4.0.1.
>
> I follow this steps:
>
> 1. Update repository for 4.0.1
>
> 2. Disable old repository 3.6.7
>
> 3. run: yum update "ovirt-engine-setup*"
>
> now an error occured:
>
> yum update "ovirt-engine-setup*"
> Plugin abilitati:fastestmirror, langpacks, versionlock
> Repository centos-ovirt36 is listed more than once in the configuration
> Repository virtio-win-stable is listed more than once in the configuration
> Loading mirror speeds from cached hostfile
>  * base: artfiles.org
>  * extras: ba.mirror.garr.it
>  * ovirt-4.0: ftp.nluug.nl
>  * ovirt-4.0-epel: epel.besthosting.ua
>  * updates: ba.mirror.garr.it
> Risoluzione dipendenze
> --> Esecuzione del controllo di transazione
> ---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
> per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
> pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> --> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
> ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
> ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> --> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
> otopi-java-1.4.2-1.el7.centos.noarch
> ---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
> per essere un aggiornamento
> ---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> ---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> --> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> va in conflitto con ovirt-engine-reports-setup < 4.0.0
> --> Risoluzione delle dipendenze completata
> Errore: ovirt-engine-setup-base conflicts with
> ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
>  Si può provare ad usare --skip-broken per aggirare il problema
> ** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
> bash-4.2.46-20.el7_2.x86_64 è un duplicato di 

Re: [ovirt-users] Upgrade from 3.6 to 4.0

2016-08-03 Thread nicola.gentile.to

Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my environment, 
where the host itslef is providing the NFS service for storage domains:


After install you have to make a dependency so that VDSM Broker starts 
after NFS Server


In /usr/lib/systemd/system/ovirt-ha-broker.service

Added in section  [Unit] the line:

After=nfs-server.service

Also, for vdsmd service, in file vdsmd.service changed from:

After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
  supervdsmd.service sanlock.service vdsm-network.service

to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
  supervdsmd.service sanlock.service vdsm-network.service \
  nfs-server.service

NOTE: the files will be overwritten by future updates, so you have to 
keep in mind...



Hi,

I try to upgrade from ovirt 3.6.7 to 4.0.1.

I follow this steps:

1. Update repository for 4.0.1

2. Disable old repository 3.6.7

3. run: yum update "ovirt-engine-setup*"

now an error occured:

yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: artfiles.org
 * extras: ba.mirror.garr.it
 * ovirt-4.0: ftp.nluug.nl
 * ovirt-4.0-epel: epel.besthosting.ua
 * updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato 
per essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato 
per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos 
settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos 
settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos 
per il pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto: 
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il 
pacchetto: 
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch 
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch 
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento

--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere 
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il 
pacchetto: otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un 
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos 
settato per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos 
settato per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato 
per essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato 
per essere un aggiornamento

--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere 
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere 
un aggiornamento
--> Analisi conflitto: 
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch va in conflitto con 
ovirt-engine-reports-setup < 4.0.0

--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with 
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch

 Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di 
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di 

Re: [ovirt-users] Unable to login to the WEB UI

2016-08-03 Thread Martin Perina
Hi,

are you using HTTPS certificate signed by external CA? If so please follow
steps described in Doc Text of

https://bugzilla.redhat.com/show_bug.cgi?id=1336838

Thanks

Martin Perina


On Wed, Aug 3, 2016 at 1:18 PM, Fabrice Bacchella <
fabrice.bacche...@icloud.com> wrote:

> After the upgrad, I'm unable to log in, I'm getting the following error:
>
>  sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path
>  to requested target
>
>
> Where should I look to correct that ?
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Unable to login to the WEB UI

2016-08-03 Thread Fabrice Bacchella
After the upgrad, I'm unable to log in, I'm getting the following error:

 sun.security.validator.ValidatorException: PKIX path building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
valid certification path
 to requested target


Where should I look to correct that ?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Unusable log in engine.log

2016-08-03 Thread Fabrice Bacchella
In the engine.log, there are many line like that :
grep '2016-08-03 13:00:46,371 INFO  
.org.ovirt.engine.core.vdsbroker.HostDevListByCapsVDSCommand. 
.org.ovirt.thread.pool-8-thread-16. .28054a0c. ' 
/var/log/ovirt-engine/engine.log | wc   
  18574  179635

1 line
8574 words
179635 characters.

And at the INFO level. It's almost impossible to check logs with line like 
that. They should be :
1/at trace level
2/send to a dedicated file
3/don't be logged at all.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Upgrade to 4.0.1 failed with NPE on org.postgresql.jdbc.TypeInfoCache.getSQLType

2016-08-03 Thread Martin Perina
Hi,

we support only postgresql packages included in centos:

postgresql-9.2.15-1.el7_2.x86_64
postgresql-libs-9.2.15-1.el7_2.x86_64
postgresql-jdbc-9.2.1002-5.el7.noarch
postgresql-server-9.2.15-1.el7_2.x86_64

This is the postgresql version which we test.

In your special case downgrading postgresql-jdbc package to 9.2 may solve
the issue, but please be aware it's not tested and it may cause other
issues. The only correct way is to use PostgreSQL 9.2.

Martin Perina



On Wed, Aug 3, 2016 at 12:56 PM, Fabrice Bacchella <
fabrice.bacche...@icloud.com> wrote:

> Just a little investigation show :
>
> # lsof -p  | grep postgresql-jdbc.jar
> java2138 ovirt  mem   REG8,2486139 18729421
> /usr/share/java/postgresql-jdbc.jar
>
> rpm -qf /usr/share/java/postgresql-jdbc.jar
> postgresql-jdbc-9.4.1208-1.rhel7.noarch
>
> rpm -qi postgresql-jdbc-9.4.1208-1.rhel7.noarch
> ...
> URL : https://jdbc.postgresql.org/
>
> And indeed I needed to install pgdg-94-centos.repo, my note says the
> package was needed by ovirt, I don't remember why. And indeed :
> yum erase postgresql94-server
> ...
> Removing:
>  postgresql94-server
> x86_64 9.4.8-1PGDG.rhel7
> @pgdg94
> 17 M
> Removing for dependencies:
>  ovirt-engine
> noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> 2.6 M
>  ovirt-engine-backend
> noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> 13 M
>
> So I tried:
>
> yum downgrade postgresql-jdbc
> ...
> ---> Package postgresql-jdbc.noarch 0:9.2.1002-5.el7 will be a downgrade
> ...
>
> And now it (almost) works. I have other not linked problems that needs
> more investigations.
>
>
> Le 3 août 2016 à 12:39, Martin Perina  a écrit :
>
> Hi,
>
> what is the version of postgresql-jdbc package are you using? I saw this
> error only with latest postgresql-jdbc drivers 9.4-1209, but those are not
> packaged in RPMs AFAIK.
>
> Thanks
>
> Martin Perina
>
>
> On Wed, Aug 3, 2016 at 12:31 PM, Fabrice Bacchella <
> fabrice.bacche...@icloud.com> wrote:
>
>> I'm running on Centos 7, just upgraded to ovirt 4.01 using the procedure
>> given in the release notes.
>>
>> But now I'm getting that in /var/log/ovirt-engine/engine.log:
>>
>> 2016-08-03 12:04:39,751 ERROR [org.ovirt.engine.core.bll.Backend]
>> (ServerService Thread Pool -- 54) [] Error during initialization:
>> org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke
>> private void org.ovirt.engine.core.vds
>> broker.ResourceManager.init() on
>> org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e
>>at
>> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>>at
>> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
>> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>> ...
>> Caused by: java.lang.reflect.InvocationTargetException
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> [rt.jar:1.8.0_92]
>>at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> [rt.jar:1.8.0_92]
>>at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> [rt.jar:1.8.0_92]
>>at java.lang.reflect.Method.invoke(Method.java:498)
>> [rt.jar:1.8.0_92]
>>at
>> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
>> 

Re: [ovirt-users] Upgrade to 4.0.1 failed with NPE on org.postgresql.jdbc.TypeInfoCache.getSQLType

2016-08-03 Thread Fabrice Bacchella
Just a little investigation show :

# lsof -p  | grep postgresql-jdbc.jar
java2138 ovirt  mem   REG8,2486139 18729421 
/usr/share/java/postgresql-jdbc.jar

rpm -qf /usr/share/java/postgresql-jdbc.jar
postgresql-jdbc-9.4.1208-1.rhel7.noarch

rpm -qi postgresql-jdbc-9.4.1208-1.rhel7.noarch
...
URL : https://jdbc.postgresql.org/

And indeed I needed to install pgdg-94-centos.repo, my note says the package 
was needed by ovirt, I don't remember why. And indeed :
yum erase postgresql94-server
...
Removing:
 postgresql94-server
  x86_64 9.4.8-1PGDG.rhel7  
  @pgdg94   
  17 M
Removing for dependencies:
 ovirt-engine   
  noarch 4.0.1.1-1.el7.centos   
  @ovirt-4.0
 2.6 M
 ovirt-engine-backend   
  noarch 4.0.1.1-1.el7.centos   
  @ovirt-4.0
  13 M

So I tried:

yum downgrade postgresql-jdbc
...
---> Package postgresql-jdbc.noarch 0:9.2.1002-5.el7 will be a downgrade
...

And now it (almost) works. I have other not linked problems that needs more 
investigations.


> Le 3 août 2016 à 12:39, Martin Perina  a écrit :
> 
> Hi,
> 
> what is the version of postgresql-jdbc package are you using? I saw this 
> error only with latest postgresql-jdbc drivers 9.4-1209, but those are not 
> packaged in RPMs AFAIK.
> 
> Thanks
> 
> Martin Perina
> 
> 
> On Wed, Aug 3, 2016 at 12:31 PM, Fabrice Bacchella 
> > wrote:
> I'm running on Centos 7, just upgraded to ovirt 4.01 using the procedure 
> given in the release notes.
> 
> But now I'm getting that in /var/log/ovirt-engine/engine.log:
> 
> 2016-08-03 12:04:39,751 ERROR [org.ovirt.engine.core.bll.Backend] 
> (ServerService Thread Pool -- 54) [] Error during initialization: 
> org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke 
> private void org.ovirt.engine.core.vds
> broker.ResourceManager.init() on 
> org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e
>at 
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
>  [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at 
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
>  [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at 
> org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
>  [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) 
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) 
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
>  [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at 
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
>  [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at 
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) 
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at 
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) 
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
> ...
> Caused by: java.lang.reflect.InvocationTargetException
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> [rt.jar:1.8.0_92]
>at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> [rt.jar:1.8.0_92]
>at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [rt.jar:1.8.0_92]
>at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
>at 
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
>  [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>... 82 more
> Caused by: java.lang.NullPointerException
>at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:182)
>at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:178)
>at 
> org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1259)
>at 
> 

Re: [ovirt-users] Upgrade to 4.0.1 failed with NPE on org.postgresql.jdbc.TypeInfoCache.getSQLType

2016-08-03 Thread Martin Perina
Hi,

what is the version of postgresql-jdbc package are you using? I saw this
error only with latest postgresql-jdbc drivers 9.4-1209, but those are not
packaged in RPMs AFAIK.

Thanks

Martin Perina


On Wed, Aug 3, 2016 at 12:31 PM, Fabrice Bacchella <
fabrice.bacche...@icloud.com> wrote:

> I'm running on Centos 7, just upgraded to ovirt 4.01 using the procedure
> given in the release notes.
>
> But now I'm getting that in /var/log/ovirt-engine/engine.log:
>
> 2016-08-03 12:04:39,751 ERROR [org.ovirt.engine.core.bll.Backend]
> (ServerService Thread Pool -- 54) [] Error during initialization:
> org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke
> private void org.ovirt.engine.core.vds
> broker.ResourceManager.init() on
> org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e
>at
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
> ...
> Caused by: java.lang.reflect.InvocationTargetException
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.8.0_92]
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [rt.jar:1.8.0_92]
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_92]
>at java.lang.reflect.Method.invoke(Method.java:498)
> [rt.jar:1.8.0_92]
>at
> org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
> [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
>... 82 more
> Caused by: java.lang.NullPointerException
>at
> org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:182)
>at
> org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:178)
>at
> org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1259)
>at
> org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1040)
>at
> org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(GenericCallMetaDataProvider.java:353)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.initializeWithProcedureColumnMetaData(GenericCallMetaDataProvider.java:112)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory$1.processMetaData(CallMetaDataProviderFactory.java:133)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:299)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.createMetaDataProvider(CallMetaDataProviderFactory.java:73)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.springframework.jdbc.core.metadata.CallMetaDataContext.initializeMetaData(CallMetaDataContext.java:286)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.springframework.jdbc.core.simple.AbstractJdbcCall.compileInternal(AbstractJdbcCall.java:303)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.compileInternal(PostgresDbEngineDialect.java:108)
> [dal.jar:]
>at
> org.springframework.jdbc.core.simple.AbstractJdbcCall.compile(AbstractJdbcCall.java:288)
> [spring-jdbc.jar:4.2.4.RELEASE]
>at
> org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.getCall(SimpleJdbcCallsHandler.java:169)
> [dal.jar:]
>at
> 

[ovirt-users] Upgrade to 4.0.1 failed with NPE on org.postgresql.jdbc.TypeInfoCache.getSQLType

2016-08-03 Thread Fabrice Bacchella
I'm running on Centos 7, just upgraded to ovirt 4.01 using the procedure given 
in the release notes.

But now I'm getting that in /var/log/ovirt-engine/engine.log:

2016-08-03 12:04:39,751 ERROR [org.ovirt.engine.core.bll.Backend] 
(ServerService Thread Pool -- 54) [] Error during initialization: 
org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke private 
void org.ovirt.engine.core.vds
broker.ResourceManager.init() on 
org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e
   at 
org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at 
org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at 
org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at 
org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at 
org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at 
org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   at 
org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
...
Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
[rt.jar:1.8.0_92]
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
[rt.jar:1.8.0_92]
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [rt.jar:1.8.0_92]
   at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
   at 
org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
   ... 82 more
Caused by: java.lang.NullPointerException
   at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:182)
   at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:178)
   at 
org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1259)
   at 
org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1040)
   at 
org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(GenericCallMetaDataProvider.java:353)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.initializeWithProcedureColumnMetaData(GenericCallMetaDataProvider.java:112)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory$1.processMetaData(CallMetaDataProviderFactory.java:133)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:299)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.createMetaDataProvider(CallMetaDataProviderFactory.java:73)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.springframework.jdbc.core.metadata.CallMetaDataContext.initializeMetaData(CallMetaDataContext.java:286)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.springframework.jdbc.core.simple.AbstractJdbcCall.compileInternal(AbstractJdbcCall.java:303)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.compileInternal(PostgresDbEngineDialect.java:108)
 [dal.jar:]
   at 
org.springframework.jdbc.core.simple.AbstractJdbcCall.compile(AbstractJdbcCall.java:288)
 [spring-jdbc.jar:4.2.4.RELEASE]
   at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.getCall(SimpleJdbcCallsHandler.java:169)
 [dal.jar:]
   at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:146)
 [dal.jar:]
   at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeReadList(SimpleJdbcCallsHandler.java:109)
 [dal.jar:]
   at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeRead(SimpleJdbcCallsHandler.java:101)
 [dal.jar:]
   at 
org.ovirt.engine.core.dao.VdsDynamicDaoImpl.get(VdsDynamicDaoImpl.java:129) 
[dal.jar:]
   at 

[ovirt-users] upgrade to ovirt 4 failed

2016-08-03 Thread Fabrice Bacchella
I'm running on Centos 7, just upgraded to ovirt 4.01 using the procedure given 
in the release notes.

But now I'm getting that in /var/log/ovirt-engine/engine.log:

2016-08-03 12:04:39,751 ERROR [org.ovirt.engine.core.bll.Backend] 
(ServerService Thread Pool -- 54) [] Error during initialization: 
org.jboss.weld.exceptions.WeldException: WELD-49: Unable to invoke private 
void org.ovirt.engine.core.vds
broker.ResourceManager.init() on 
org.ovirt.engine.core.vdsbroker.ResourceManager@28b87a8e
at 
org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at 
org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at 
org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at 
org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at 
org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at 
org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
at 
org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) 
[weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
...
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
[rt.jar:1.8.0_92]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
[rt.jar:1.8.0_92]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [rt.jar:1.8.0_92]
at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_92]
at 
org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98)
 [weld-core-impl-2.3.2.Final.jar:2.3.2.Final]
... 82 more
Caused by: java.lang.NullPointerException
at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:182)
at org.postgresql.jdbc.TypeInfoCache.getSQLType(TypeInfoCache.java:178)
at 
org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1259)
at 
org.postgresql.jdbc.PgDatabaseMetaData.getProcedureColumns(PgDatabaseMetaData.java:1040)
at 
org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(GenericCallMetaDataProvider.java:353)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.initializeWithProcedureColumnMetaData(GenericCallMetaDataProvider.java:112)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory$1.processMetaData(CallMetaDataProviderFactory.java:133)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:299)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.createMetaDataProvider(CallMetaDataProviderFactory.java:73)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.springframework.jdbc.core.metadata.CallMetaDataContext.initializeMetaData(CallMetaDataContext.java:286)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.springframework.jdbc.core.simple.AbstractJdbcCall.compileInternal(AbstractJdbcCall.java:303)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.compileInternal(PostgresDbEngineDialect.java:108)
 [dal.jar:]
at 
org.springframework.jdbc.core.simple.AbstractJdbcCall.compile(AbstractJdbcCall.java:288)
 [spring-jdbc.jar:4.2.4.RELEASE]
at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.getCall(SimpleJdbcCallsHandler.java:169)
 [dal.jar:]
at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:146)
 [dal.jar:]
at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeReadList(SimpleJdbcCallsHandler.java:109)
 [dal.jar:]
at 
org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeRead(SimpleJdbcCallsHandler.java:101)
 [dal.jar:]
at 
org.ovirt.engine.core.dao.VdsDynamicDaoImpl.get(VdsDynamicDaoImpl.java:129) 
[dal.jar:]
at 

Re: [ovirt-users] storage domain operation python api sample codes needed

2016-08-03 Thread Ondra Machacek

On 08/02/2016 10:53 PM, Huan He (huhe) wrote:

Hi,

I can’t figure out how to do the following, a sample code will be helpful.

Put a storage domain in maintenance mode
Detach the storage domain
Remove the storage domain


Are you looking for v4 or v3 examples?
Those are completelly different SDKs so examples will be different as well.
For v4 you can inspire here:

 https://github.com/oVirt/ovirt-engine-sdk/tree/master/sdk/examples



By the way, do you have an API doc or wiki?


There is for v4:

 https://jhernand.fedorapeople.org/ovirt-api-explorer/#/

not sure about v3



Thanks,
Huab



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users