Hide Forgot
Description of problem: Running cucumber tests reports that the "Launch new deployment" scenario of the "Manage Deployments" cucumber feature fails. Initially, the test failed due to the mock provider account and mock pool family were not associated. The original error I received was: Could not find a matching backend provider, errors: There are no provider accounts associated with pool family of selected pool. I added the step for the association, but the test failed because the image was not pushed to the provider account. The error as it's displayed on the page looks like: Could not find a matching backend provider, errors: my_mock_provider: image is not pushed to this provider account At this point, I can't figure out how to mock out the fact that an image is pushed to a provider account. It appears that one possible path is to mock out the Instance#matches method so that it returns no errors and a list containing the mocked provider account. Version-Release number of selected component (if applicable): How reproducible: Run cucumber tests on conductor. I currently have checked out: c5269b9030311879955672d1645e2d312542031a
I started to look into this and kind of wonder how this ever worked. It seems like there are multiple things wrong. I changed the tests to set up a provider and provider account (there were none), but now I'm onto errors about it not finding images in warehouse.
There's apparently a lot in play here. This is in the repo: commit 9ef53f0625725aae6b6ad0598ad66e9efd569be1 Author: Tomas Hrcka <thrcka> Date: Thu Oct 6 19:13:06 2011 +0200 Fixed failing deployment cucumber test. edited by Scott Seago <sseago> This requires mfojtik's HWP validation patch on deltacloud-core (probably pushed by now). -- However, that deltacloud-core patch doesn't appear to have hit the repos yet.
This is fixed. The last bit was a deltacloud bug. It's fixed in 0.4.1, but 0.4.1 is newer than 0.5.0, so developer systems with 0.5.0 installed will need to downgrade, or remove 0.5.0 and reinstall to get 0.4.1 (now that 0.5.0 is out of the repo).
Feature: Manage Deployments In order to manage my cloud infrastructure As a user I want to manage my deployments Background: # features/deployment.feature:6 Given I am an authorised user # features/step_definitions/pool_steps.rb:16 And I am logged in # features/step_definitions/authentication.rb:61 Scenario: List deployments # features/deployment.feature:10 Given there is a deployment named "MySQL Cluster" belonging to "Databases" owned by "bob" # features/step_definitions/deployment_steps.rb:1 And I am on the pools page # features/step_definitions/web_steps.rb:59 When I follow link with ID "filter_view" # features/step_definitions/custom_web_steps.rb:16 And I follow "details_deployments" within "#tab-container-1-nav" # features/step_definitions/web_steps.rb:50 Then I should see "MySQL Cluster" # features/step_definitions/web_steps.rb:121 And I should see "bob" # features/step_definitions/web_steps.rb:121 [root@qeblade31 ~]# rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-10.el6.noarch aeolus-conductor-doc-0.8.0-36.el6.noarch aeolus-all-0.8.0-36.el6.noarch rubygem-aeolus-cli-0.4.0-0.20120227105812git15ef29d.el6.noarch aeolus-conductor-0.8.0-36.el6.noarch aeolus-configure-2.5.0-15.el6.noarch aeolus-conductor-daemons-0.8.0-36.el6.noarch aeolus-conductor-devel-0.8.0-36.el6.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html