-
Notifications
You must be signed in to change notification settings - Fork 175
Closed
Labels
component/testTests not covered by a more specific component labelTests not covered by a more specific component labelkind/defectBehavior that is inconsistent with what's intendedBehavior that is inconsistent with what's intendedpriority/p0team/lifecycle
Milestone
Description
Seen in https://ci.vcna.io/vmware/vic/16168. The Suggest resources - Invalid datacenter test in Group6-VIC-Machine.6-05-Create-Validation failed because of a VCH name collision with a previous VCH (from test Group12-VCH-BC.12-01-Delete) whose certs dir was not cleaned up.
I think this is due to
| ${ret}= Run bin/vic-machine-linux delete --target %{TEST_URL} --user %{TEST_USERNAME} --password=%{TEST_PASSWORD} --compute-resource=%{TEST_RESOURCE} --name %{VCH-NAME} --force |
The test doesn't cleanup the certs directory after deleting the VCH. Also, it deletes the VCH directly instead of using the Cleanup VIC Appliance On Test Server or a similar secret keyword that redacts the username and password.
Acceptance criteria:
- Test cleans up the certs dir
- Test uses a secret keyword to delete the VCH
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
component/testTests not covered by a more specific component labelTests not covered by a more specific component labelkind/defectBehavior that is inconsistent with what's intendedBehavior that is inconsistent with what's intendedpriority/p0team/lifecycle