deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <>
Subject [jira] [Created] (DTACLOUD-441) api tests don't clean up after themselves
Date Mon, 28 Jan 2013 10:15:12 GMT
Dies Koper created DTACLOUD-441:

             Summary: api tests don't clean up after themselves
                 Key: DTACLOUD-441
             Project: DeltaCloud
          Issue Type: Test
          Components: Server
         Environment: Fgcp driver
            Reporter: Dies Koper
            Assignee: Dies Koper
            Priority: Minor

When running DC api tests (rake tests:deltacloud in root tests folder), the following is logged
at the end (when using with Fgcp):

CLEANING UP... resources for deletion: {:firewalls=>[], :instances=>["UZXC0GRT-ZG8ZJCJ07-S-0113"],
:keys=>[], :images=>[]}
CLEANUP attempt finished... resources looks like: {:instances=>["UZXC0GRT-ZG8ZJCJ07-S-0113"]}
deltacloud/instances_test.rb:71: Unable to delete all created resources - please check: {:instances=>["UZXC0GRT-ZG8ZJCJ07-S-0113"]}
        from deltacloud/instances_test.rb:244:in `call'
        from deltacloud/instances_test.rb:244:in `to_proc'
        from D:/programs/Ruby187/lib/ruby/gems/1.8/gems/minitest-4.4.0/lib/minitest/unit.rb:782:in
        from D:/programs/Ruby187/lib/ruby/gems/1.8/gems/minitest-4.4.0/lib/minitest/unit.rb:782:in

The reason it failed to delete them is because it only tried to stop them, not destroy them.
For Fgcp, stopping an instance doesn't destroy it.

Suggesting to add code that calls the destroy_instance operation on instances after the stop

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message