Description of problem: Deltacloud API can return enumerable architecture when asking for hardware profiles. Problem is that conductor uses only 'default' value when searching for proper HW profile and ignores other enum options. We should update conductor HWP matching methods to support enum architecture. Alternatively deltacloud API could be updated to not return architecture of enum type -> CCing Michal Fojtik and David Lutterkort. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It was fixed in deltacloud-client version 0.4.0-1.
Matching Provider Hardware Profiles Provider Name Hardware Profile Name Architecture Memory Storage Virtual CPU ec2-us-east-1 c1.xlarge x86_64 7168 1690 20 mock m1-large x86_64 7680.0 - 15360 850, 1024 2 verified.. [root@unused ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.4.0-0.20110919181505git369190d.fc15.noarch aeolus-configure-2.0.2-4.20110916125556git5a94390.fc15.noarch aeolus-conductor-0.4.0-0.20110919181505git369190d.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20110919181505git369190d.fc15.noarch aeolus-all-0.4.0-0.20110919181505git369190d.fc15.noarch rubygem-aeolus-image-0.1.0-3.20110919115936gitd1d24b4.fc15.noarch [root@unused ~]#
*** Bug 739177 has been marked as a duplicate of this bug. ***