Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 674694

Summary:	Some hardware profiles load wrong profile details
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Angus Thomas <athomas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	wes hayutin <whayutin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.3.1	CC:	akarol, cpelland, dajohnso, deltacloud-maint, dgao, ssachdev, whayutin
Target Milestone:	alpha
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-16 13:43:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Johnson 2011-02-02 22:51:00 UTC

Description of problem:
Clicking on several hardware profiles loads the details from the wrong profile.

Working profiles:   m1.large, m1.small, t1.micro, m1.xlarge
Broken profiles:    m2.4xlarge, m2.xlarge, m2.2xlarge, c1.medium, c1.xlarge


Steps to Reproduce:
1.  Go to hardware profiles
2.  Click on m1.large and notice its details are displayed
3.  Now click on 'm2.4xlarge'
  
Actual results:
Notice t1.micro details are displayed

Expected results:
correct details displayed

Additional info:
I originally opened bug 674442 but closed it when I noticed that the details did display when using the postgres db, (I was running with a sqlite db). Then I realized that the app was displaying the wrong details so I opened this new bug.

Comment 1 Dave Johnson 2011-02-02 23:02:32 UTC

[root@cloudEng-qe-vm conductor]# git show
commit 70526a6f9b3b51e54c581f35410f255c3749a987

Comment 2 wes hayutin 2011-03-11 16:59:25 UTC

adding to the ce-beta blocking tracker

Comment 3 Dave Johnson 2011-03-16 13:43:08 UTC

ui design has changed thus invalidating this bug

Comment 4 wes hayutin 2011-12-08 13:58:15 UTC

perm close