Bug 714935 - "No Matching Provider Hardware Profiles Could be found" is displayed when clicked on New Hardware profile
Summary: "No Matching Provider Hardware Profiles Could be found" is displayed when cli...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Jiri Tomasek
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 11:21 UTC by Aziza Karol
Modified: 2012-01-26 12:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 13:17:24 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Aziza Karol 2011-06-21 11:21:21 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.From control panels. select "Hardware Profiles"
2.click on "New Hardware Profile".
3."No Matching Provider Hardware Profiles Could be found " is displayed.
 
I think this message should be displayed when we do "check Matches".
 
Actual results:


Expected results:


Additional info:
[root@nec-em19 aeolus-configure]# rpm -qa  | grep aeolus
rubygem-aeolus-cli-0.0.1-1.fc14.20110620142346git1c969a7.noarch
aeolus-conductor-doc-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-conductor-daemons-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-conductor-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-all-0.3.0-0.fc14.20110620142346git1c969a7.noarch
aeolus-configure-2.0.1-0.fc14.20110602110128git5cb9257.noarch
Comment 1 wes hayutin 2011-06-21 13:17:24 UTC 
could not recreate..

[root@nec-em9 noarch]# rpm -qa | grep aeolus
aeolus-conductor-daemons-0.3.0-0.fc14.20110621130906gita33fdea.noarch
aeolus-all-0.3.0-0.fc14.20110621130906gita33fdea.noarch
rubygem-aeolus-cli-0.0.1-1.fc14.20110621130906gita33fdea.noarch
aeolus-conductor-devel-0.3.0-0.fc14.20110621130906gita33fdea.noarch
aeolus-conductor-0.3.0-0.fc14.20110621130906gita33fdea.noarch
aeolus-configure-2.0.1-0.fc14.20110602110128git5cb9257.noarch
aeolus-conductor-doc-0.3.0-0.fc14.20110621130906gita33fdea.noarch
[root@nec-em9 noarch]# 

You will need to create provider and provider account for this to work.. Ping me w/ questions
Comment 2 wes hayutin 2011-06-21 14:05:52 UTC 
ah.. yes.. now I do see the issue..

No Matching Provider Hardware Profiles Could be found
Comment 3 Jiri Tomasek 2011-06-23 13:30:14 UTC 
fixed in commit 9adb404ce8e40abb73db0d8227862e73c090b345
Comment 4 Aziza Karol 2011-07-01 10:00:32 UTC 
Message not displayed when clicked on New Hardware profile.

verified on:
[root@ibm-x3950m2-01 ~]# rpm -qa | grep aeolus
rubygem-aeolus-cli-0.0.1-1.fc14.20110630225932gitafa30be.noarch
aeolus-configure-2.0.1-0.fc14.20110628141215gitb8aaf85.noarch
aeolus-conductor-daemons-0.3.0-0.fc14.20110630225932gitafa30be.noarch
aeolus-conductor-0.3.0-0.fc14.20110630225932gitafa30be.noarch
aeolus-all-0.3.0-0.fc14.20110630225932gitafa30be.noarch
aeolus-conductor-doc-0.3.0-0.fc14.20110630225932gitafa30be.noarch
Comment 5 wes hayutin 2011-07-05 15:04:09 UTC 
removing ce-p2-beta
Comment 6 wes hayutin 2011-07-05 15:07:51 UTC 
second attempt to remove ce-p2-beta
Comment 7 wes hayutin 2011-08-01 19:56:00 UTC 
release pending...
Comment 8 wes hayutin 2011-08-01 19:57:39 UTC 
release pending...
Comment 10 wes hayutin 2011-12-08 13:51:17 UTC 
perm close
Comment 11 wes hayutin 2011-12-08 13:54:16 UTC 
closing out old bugs
Note You need to log in before you can comment on or make changes to this bug.