[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.
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@andrewklau.com> To: users@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.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message ----- | From: "Laszlo Hornyak" <lhornyak@redhat.com> | To: "Andrew Lau" <andrew@andrewklau.com>, "Noam Slomianko" <nslomian@redhat.com> | Cc: users@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@andrewklau.com> | > To: users@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
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) 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@redhat.com> wrote:
----- Original Message ----- | From: "Laszlo Hornyak" <lhornyak@redhat.com> | To: "Andrew Lau" <andrew@andrewklau.com>, "Noam Slomianko" < nslomian@redhat.com> | Cc: users@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@andrewklau.com> | > To: users@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
I was able to test, the beta version doesn't have the fix but nightly does. On Fri, Sep 6, 2013 at 6:22 PM, Andrew Lau <andrew@andrewklau.com> wrote:
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)
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@redhat.com>wrote:
----- Original Message ----- | From: "Laszlo Hornyak" <lhornyak@redhat.com> | To: "Andrew Lau" <andrew@andrewklau.com>, "Noam Slomianko" < nslomian@redhat.com> | Cc: users@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@andrewklau.com> | > To: users@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
----- Original Message -----
From: "Andrew Lau" <andrew@andrewklau.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: "users" <users@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@redhat.com > wrote:
----- Original Message ----- | From: "Laszlo Hornyak" < lhornyak@redhat.com > | To: "Andrew Lau" < andrew@andrewklau.com >, "Noam Slomianko" < | nslomian@redhat.com > | Cc: users@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@andrewklau.com > | > To: users@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
The patch for the fix only appears to be in the nightlies, my beta install the issue was back. 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 Thanks, Andrew On Fri, Sep 6, 2013 at 7:04 PM, Doron Fediuck <dfediuck@redhat.com> wrote:
----- Original Message -----
From: "Andrew Lau" <andrew@andrewklau.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: "users" <users@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@redhat.com > wrote:
----- Original Message ----- | From: "Laszlo Hornyak" < lhornyak@redhat.com > | To: "Andrew Lau" < andrew@andrewklau.com >, "Noam Slomianko" < | nslomian@redhat.com > | Cc: users@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@andrewklau.com > | > To: users@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Andrew Lau" <andrew@andrewklau.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: "users" <users@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@redhat.com > wrote:
----- Original Message -----
From: "Andrew Lau" < andrew@andrewklau.com > To: "Doron Fediuck" < dfediuck@redhat.com > Cc: "users" < users@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@redhat.com > wrote:
----- Original Message ----- | From: "Laszlo Hornyak" < lhornyak@redhat.com > | To: "Andrew Lau" < andrew@andrewklau.com >, "Noam Slomianko" < | nslomian@redhat.com > | Cc: users@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@andrewklau.com > | > To: users@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Il giorno 06/set/2013 11:14, "Doron Fediuck" <dfediuck@redhat.com> ha scritto:
----- Original Message -----
From: "Andrew Lau" <andrew@andrewklau.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: "users" <users@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.
If one wants to test right now the upcoming 3.3, nightly is ok? No risk to get engine 3.4, correct? Or is there any rc repo? Gianluca
Here's an extract of the error: 2013-09-06 18:55:49 DEBUG otopi.plugins.ovirt_engine_setup.db.schema plugin.execute:446 execute-output: ['/usr/share/ovirt-engine/dbscripts/upgrade.sh', '-s', 'localhost', '-p', '5432'$ psql:create_views.sql:400: ERROR: column vm_templates.single_qxl_pci does not exist LINE 18: vm_templates.single_qxl_pci as single_qxl_pci, ^ 2013-09-06 18:55:49 DEBUG otopi.context context._executeMethod:137 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 127, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/db/schema.py", line 261, in _miscUpgrade osetupcons.DBEnv.PGPASS_FILE File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 451, in execute command=args[0], RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute On Fri, Sep 6, 2013 at 7:25 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com>wrote:
Il giorno 06/set/2013 11:14, "Doron Fediuck" <dfediuck@redhat.com> ha scritto:
----- Original Message -----
From: "Andrew Lau" <andrew@andrewklau.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: "users" <users@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.
If one wants to test right now the upcoming 3.3, nightly is ok? No risk to get engine 3.4, correct? Or is there any rc repo? Gianluca
----- Original Message -----
From: "Andrew Lau" <andrew@andrewklau.com> To: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Cc: "users" <users@ovirt.org> Sent: Friday, September 6, 2013 12:46:13 PM Subject: Re: [Users] oVirt API Code 500 with Foreman
Here's an extract of the error:
2013-09-06 18:55:49 DEBUG otopi.plugins.ovirt_engine_setup.db.schema plugin.execute:446 execute-output: ['/usr/share/ovirt-engine/dbscripts/upgrade.sh', '-s', 'localhost', '-p', '5432'$ psql:create_views.sql:400: ERROR: column vm_templates.single_qxl_pci does not exist LINE 18: vm_templates.single_qxl_pci as single_qxl_pci, ^
Thanks Andrew. This was added here: http://gerrit.ovirt.org/#/c/16803/14/packaging/dbscripts/create_views.sql Shahar, can you please take a look?
2013-09-06 18:55:49 DEBUG otopi.context context._executeMethod:137 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 127, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/db/schema.py", line 261, in _miscUpgrade osetupcons.DBEnv.PGPASS_FILE File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 451, in execute command=args[0], RuntimeError: Command '/usr/share/ovirt-engine/dbscripts/upgrade.sh' failed to execute
On Fri, Sep 6, 2013 at 7:25 PM, Gianluca Cecchi < gianluca.cecchi@gmail.com > wrote:
Il giorno 06/set/2013 11:14, "Doron Fediuck" < dfediuck@redhat.com > ha scritto:
----- Original Message -----
From: "Andrew Lau" < andrew@andrewklau.com > To: "Doron Fediuck" < dfediuck@redhat.com > Cc: "users" < users@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.
If one wants to test right now the upcoming 3.3, nightly is ok? No risk to get engine 3.4, correct? Or is there any rc repo? Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
Andrew Lau -
Doron Fediuck -
Gianluca Cecchi -
Laszlo Hornyak