[Users] oVirt API Code 500 with Foreman

Fri Sep 6 09:14:17 UTC 2013


----- Original Message -----
> From: "Andrew Lau" <andrew at andrewklau.com>
> To: "Doron Fediuck" <dfediuck at redhat.com>
> Cc: "users" <users at ovirt.org>
> Sent: Friday, September 6, 2013 12:07:50 PM
> Subject: Re: [Users] oVirt API Code 500 with Foreman
> 
> The patch for the fix only appears to be in the nightlies, my beta install
> the issue was back.
> 
Since the official release is expected in the coming days, I'd suggest not
to invest time on the beta release.

> In regards to the upgrade issue, I ran engine-setup after enabling the
> nightly repo. It updated all the packages but ran into the error and rolled
> back all the packages.
> 
> [ INFO ] Updating database schema
> [ ERROR ] Failed to execute stage 'Misc configuration': Command
> '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute
> [ INFO ] Yum Performing yum transaction rollback
> 
> 
There should be a reference to a log file with additional details
which may provide the actual error. Try to find the actual sql (or
other) error which made the db upgrade fail.

> 
> Thanks,
> Andrew
> 
> 
> On Fri, Sep 6, 2013 at 7:04 PM, Doron Fediuck < dfediuck at redhat.com > wrote:
> 
> 
> 
> 
> 
> ----- Original Message -----
> > From: "Andrew Lau" < andrew at andrewklau.com >
> > To: "Doron Fediuck" < dfediuck at redhat.com >
> > Cc: "users" < users at ovirt.org >
> > Sent: Friday, September 6, 2013 11:22:16 AM
> > Subject: Re: [Users] oVirt API Code 500 with Foreman
> > 
> > Looks like the same issue is still in 3.3 beta version.. I'm not able to
> > upgrade to nightly as it's giving me another error while trying to upgrade
> > (
> > [ ERROR ] Failed to execute stage 'Misc configuration': Command
> > '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute)
> > 
> 
> Obviously this needs to be resolved regardless of the Foreman search issue,
> which was already resolved.
> Can you provide some more details on the upgrade issue?
> 
> > But the foreman issue in terms of DB search:
> > 
> > Operation FAILED: statementcallback; bad sql grammar select * from (select
> > *
> > from vds groups view where ( vds group id in (select vds groups storage
> > domain.vds group id from vds groups storage domain left outer join storage
> > pool with storage domain on vds groups storage domain.storage pool
> > id=storage pool with storage domain.id where ( storage pool with storage
> > domain.name like '%datacenter\\ m1%' or storage pool with storage
> > domain.description like '%datacenter\\ m1%' or storage pool with storage
> > domain.comment like '%datacenter\\ m1%' ) )) order by name asc ) as t1
> > offset (1 -1) limit 100; nested exception is
> > org.postgresql.util.psqlexception: error: column storage pool with storage
> > domain.comment does not exist
> > 
> > 
> > Thanks,
> > Andrew
> > 
> > 
> > On Wed, Aug 14, 2013 at 10:58 PM, Doron Fediuck < dfediuck at redhat.com >
> > wrote:
> > 
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > | From: "Laszlo Hornyak" < lhornyak at redhat.com >
> > | To: "Andrew Lau" < andrew at andrewklau.com >, "Noam Slomianko" <
> > | nslomian at redhat.com >
> > | Cc: users at ovirt.org
> > | Sent: Wednesday, August 14, 2013 10:53:19 AM
> > | Subject: Re: [Users] oVirt API Code 500 with Foreman
> > | 
> > | Hi,
> > | 
> > | Noam, looks like this is a bug in the free text comment, can you check
> > | it?
> > | I think this may be the issue. http://gerrit.ovirt.org/18061
> > | 
> > | Thx,
> > | Laszlo
> > | 
> > | ----- Original Message -----
> > | > From: "Andrew Lau" < andrew at andrewklau.com >
> > | > To: users at ovirt.org
> > | > Sent: Wednesday, August 14, 2013 8:35:03 AM
> > | > Subject: [Users] oVirt API Code 500 with Foreman
> > | > 
> > | > Hi,
> > | > 
> > | > Foreman guys say this is probably an oVirt side issue..
> > | > 
> > | > I was successfully able to hook up my foreman server to the oVirt
> > | > datacenter
> > | > using the compute resources section. It detected the available
> > | > datacenters
> > | > and logged in fine. Logs showed code 200, I can view the VMs available,
> > | > power them on and shut them down from the foreman UI.
> > | > 
> > | > But when I go to hosts->New Host and select oVirt I get the error:
> > | > 
> > | > Error loading virtual machine information: Internal Server Error
> > | > 
> > | > Logs are showing:
> > | > 
> > | > Operation FAILED: statementcallback; bad sql grammar select * from
> > | > (select
> > | > *
> > | > from vds groups view where ( vds group id in (select vds groups storage
> > | > domain.vds group id from vds groups storage domain left outer join
> > | > storage
> > | > pool with storage domain on vds groups storage domain.storage pool
> > | > id=storage pool with storage domain.id where ( storage pool with
> > | > storage
> > | > domain.name like '%dc_01%' or storage pool with storage
> > | > domain.description
> > | > like '%dc_01%' or storage pool with storage domain.comment like
> > | > '%dc_01%'
> > | > )
> > | > )) order by name asc ) as t1 offset (1 -1) limit 100; nested exception
> > | > is
> > | > org.postgresql.util.psqlexception: error: column storage pool with
> > | > storage
> > | > domain.comment does not exist
> > | > position: 421
> > | > Rendered common/500.html.erb (5.2ms)
> > | > Completed 500 Internal Server Error in 150ms (Views: 6.0ms |
> > | > ActiveRecord:
> > | > 0.3ms)
> > | > 
> > | > CentOS 6.4 - Foreman 1.2
> > | > CentOS 6.4 - oVirt 3.3 Nightly
> > | > 
> > | > Any suggestions?
> > | > 
> > | > Thanks,
> > | > Andrew.
> > | > 
> > 
> > A fix to it was just merged:
> > http://gerrit.ovirt.org/#/c/18061/
> > 
> > So you can re-build if you're working from sources,
> > or wait for the next build.
> > 
> > Doron
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> 
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>