Bug 1024961
Summary: | Error loading virtual machine information: Internal Server Error -- When Adding Host in Foreman | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Yamakasi <yamakasi.014> |
Component: | ovirt-engine-core | Assignee: | Ori Liel <oliel> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3 | CC: | acathrow, gklein, iheim, juan.hernandez, jvandewege, yamakasi.014, yeylon |
Target Milestone: | --- | ||
Target Release: | 3.4.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | infra | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-03-03 11:29:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yamakasi
2013-10-30 16:28:35 UTC
I have the same problem, same versions of oVirt and Foreman, 3.3.0-4.el6 and 1.3.0 Either Foreman or oVirt are internally generating the wrong query statement. What follows is what I posted to irc YamakasY: for reference: somewhere either Foreman or oVirt-engine is generating a wrong query. The view storage_pool_with_storage_domain is having a free_text_commnent column but either FM or oVirt is looking for a comment column. [12:46] YamakasY: my understanding of the ovirt code (30min looking around) is that there are calls which query the database for the layout of the table/view and then use that to construct the query or use the view and add columns to it using code. In the latter there is probably somewhere a line of code that adds the 'comment' column and then the query for storage_domains blows up. [12:47] YamakasY: my quick hack is regenerating the view with an extra column, comment, and then FM works again. YamakasY: ALTER TABLE storage_pool ADD COLUMN comment text; DROP VIEW storage_pool_with_storage_domain; CREATE OR REPLACE VIEW storage_pool_with_storage_domain AS SELECT storage_pool.id, storage_pool.name, storage_pool.description, storage_pool.free_text_comment, storage_pool.comment, storage_pool.storage_pool_type, storage_pool.status, storage_pool.master_domain_version, storage_pool.spm_vds_id, storage_pool.compatibility_version, storage_pool._create_date, storage_pool._update_date, storage_pool_iso_map.storage_id, storage_pool_iso_map.storage_pool_id, s torage_domain_static.storage_type, storage_domain_static.storage_domain_type, storage_domain_static.storage_domain_format_type, storage_domain_static.storage_name, storage_domain_static.storage, storage_domain_static.last_time_used_as_master FROM storage_pool LEFT JOIN storage_pool_iso_map ON storage_pool.id = storage_pool_iso_map.storage_pool_id LEFT JOIN storage_domain_static ON storage_pool_iso_map.storage_id = storage_domain_static.id; ALTER TABLE storage_pool_with_storage_domain OWNER TO engine; [12:55] YamakasY: Don't forget to backup your DATABASE!!!! setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc. I don't have this problem anymore since I upgraded to either 3.3.1 or 3.3.2 that I'm now using. oVirt-3.3.2el6 + Foreman-1.3.2 and oVirt-3.3.2-fc19 + Foreman-1.3.2 Joop Yamakasi - can you please check as well per comment 3? This was an error in the storage pool field autocompleter, and was fixed by the following change, included in 3.3.1: http://gerrit.ovirt.org/19217 |