Bug 1267213

Summary:	Getting 'Unexpected error encountered' exception page while accessing Pods and Container Services page.
Product:	Red Hat CloudForms Management Engine	Reporter:	Nikhil Gupta <ngupta>
Component:	UI - OPS	Assignee:	Alissa <abonas>
Status:	CLOSED WORKSFORME	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.5.0	CC:	hkataria, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	5.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-30 14:46:49 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 Nikhil Gupta 2015-09-29 11:10:18 UTC

Description of problem:

- Go to "CFME webui -> Containers -> Pods", it is giving below error:
~~~
ERROR: column container_groups.project does not exist LINE 1: ...stems"."id" = "container_groups"."ems_id" WHERE ((container_... ^ [container_group/show_list] 
~~~

- Go to "CFME webui -> Containers -> Container Services", it is giving below error:
~~~
 ERROR: column container_services.project does not exist LINE 1: ...ems"."id" = "container_services"."ems_id" WHERE ((container_... ^ [container_service/show_list] 
~~~

Version-Release number of selected component (if applicable):

5.5.0.1-alpha1.20150915151429_2230bd4


How reproducible:
Always

Actual results:
Getting exception.

Expected results:
It should load respective page.

Additional info:
While these pages as below, it is showing respective pages:

Go to "CFME webui -> Containers -> Providers -> Relationships -> Pods/Container Services

Test environment: https://10.65.234.116/ (User:admin Pass:smartvm)

Comment 2 Alissa 2015-09-30 14:45:19 UTC

*** Bug 1267214 has been marked as a duplicate of this bug. ***

Comment 3 Alissa 2015-09-30 14:46:49 UTC

I can't reproduce it on the latest master.
Also, from the error above it seems that the schema migration was not completed/not properly ran, so the code on that environment does not match db schema. 
Please update that environment - both code and db (db:migrate) and recheck.