This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Improve test coverage by addressing test gaps for vSphere docker volume plugin #793

Closed

1 of 3 tasks

shuklanirdesh82 opened this issue Dec 5, 2016 · 1 comment

Assignees

Labels

component/test-infrastructure kind/test

Contributor

shuklanirdesh82 commented Dec 5, 2016 •

edited

Loading

This issue is focusing on adding more tests for plugin module.

[Test Automation - 1 test] Volume attached to node 1, issue volume operations from node 2 #743 (exercise volume operations from multiple endpoint)
Add test: creating vSphere docker volume on freshly created VM shouldn't run into issue reported #656 #794 (create vSphere volume on newly created vm)
Add Test: create volume with access:read-write and later change it to read-only #820 (update access option for the volume)

shuklanirdesh82 added component/test-infrastructure kind/test labels

shuklanirdesh82 self-assigned this

Contributor

tusharnt commented Mar 1, 2017

Individual issues are already filed for tracking.

tusharnt closed this as completed

# for free to subscribe to this conversation on GitHub. Already have an account? #.