USHIFT-3271: Prevent pod name-collisions in storage tests #3516
Conversation
…uite, a pod may still be deleting when a new pod with the same name is created, which creates a name collision. extracted namespace generation into its own keyword and updated storage tests to create/cleanup a unique namespace per test case. this will isolate the pods and prevent name collisions Signed-off-by: Jon Cope <jcope@redhat.com>
|
@copejon: This pull request references USHIFT-3271 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
bot
added
the
approved
…n before setting up kubeconfig Signed-off-by: Jon Cope <jcope@redhat.com>
|
/test microshift-metal-tests |
1 similar comment
|
/test microshift-metal-tests |
Signed-off-by: Jon Cope <jcope@redhat.com>
|
/test microshift-metal-tests |
|
/test microshift-metal-tests |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: copejon, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@copejon: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
No description provided.