[ https://issues.apache.org/jira/browse/DTACLOUD-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy closed DTACLOUD-441. ---------------------------------- Closing this JIRA out - will log any new issues test cleanup in a new JIRA record. > api tests don't clean up after themselves > ----------------------------------------- > > Key: DTACLOUD-441 > URL: https://issues.apache.org/jira/browse/DTACLOUD-441 > Project: DeltaCloud > Issue Type: Test > Components: Server > Environment: Fgcp driver > Reporter: Dies Koper > Assignee: Ronelle Landy > Priority: Minor > Attachments: [PATCH] DTACLOUD441-442.eml > > > 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"]} (Ex > ception) > 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 > `reverse_each' > from > D:/programs/Ruby187/lib/ruby/gems/1.8/gems/minitest-4.4.0/lib/minitest/unit.rb:782:in > `autorun' > 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 operation. -- 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: http://www.atlassian.com/software/jira