Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1390173 - Test more pod to pod connectivity test combinations #11717

Merged
merged 2 commits into from
Nov 3, 2016

Conversation

pravisankar
Copy link

Created 2 isolated and 2 global namespaces on every node, so that pod to pod connectivity
tests can be performed among same/different namespaces, same/different nodes and global/non-global pods.

@pravisankar
Copy link
Author

@openshift/networking PTAL

@knobunc
Copy link
Contributor

knobunc commented Nov 2, 2016

[test]

Copy link
Contributor

@knobunc knobunc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -74,7 +76,7 @@ func (d *NetworkDiagnostic) Check() types.DiagnosticResult {
return d.res
}
if !ok {
d.res.Warn("DNet2002", nil, fmt.Sprintf("Skipping network diagnostics check. Reason: Not using openshift network plugin."))
d.res.Warn("DNet2002", nil, "Skipping network diagnostics check. Reason: Not using openshift network plugin.")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should split out cleanups like this into separate commits

@@ -148,6 +148,13 @@ func (d CheckPodNetwork) checkConnection(pods1, pods2 []kapi.Pod, warnMsg string
}
}
}

if !sameNamespace && !strings.Contains(warnMsg, "global to non-global projects") {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why don't you warn in that case? Is there some better way of testing for that than doing a substring check on the warning message?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't want to warn in this case because same namespace can't have global and non-global pods at the same time. May be we can make the caller pass a flag to checkConnection() to check this condition or not.

Ravi Sankar Penta added 2 commits November 2, 2016 19:08
Created 2 isolated and 2 global namespaces on every node, so that pod to pod connectivity
tests can be performed among same/different namespaces, same/different nodes and global/non-global pods.
@pravisankar
Copy link
Author

Separated bug fix and cleanup.
Caller of checkConnection() will tell whether to check same namespace condition.
@knobunc @danwinship updated, ptal

@danwinship
Copy link
Contributor

LGTM
flake is #9076, [test]

@danwinship
Copy link
Contributor

flake is #10773
[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to fd725e2

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11060/) (Base Commit: 3b6c372)

@knobunc
Copy link
Contributor

knobunc commented Nov 3, 2016

[merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented Nov 3, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11060/) (Image: devenv-rhel7_5307)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to fd725e2

@openshift-bot openshift-bot merged commit 6abb256 into openshift:master Nov 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants