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

[release-4.5] Bug 1851839: Make e2e tests more stable #130

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #124

/assign martinkunc

@martinkunc
Copy link
Contributor

/retitle [release-4.5] Bug 1851839: Make e2e tests more stable

@openshift-ci-robot openshift-ci-robot changed the title [release-4.5] Make e2e tests more stable [release-4.5] Bug 1851839: Make e2e tests more stable Jun 29, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jun 29, 2020
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "4.5.z" instead
  • expected Bugzilla bug 1851839 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.5] Bug 1851839: Make e2e tests more stable

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/test-infra repository.

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected Bugzilla bug 1851839 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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/test-infra repository.

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "4.5.z" instead
  • expected Bugzilla bug 1851839 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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/test-infra repository.

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "4.5.z" instead
  • expected dependent Bugzilla bug 1851840 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is NEW instead
  • expected dependent Bugzilla bug 1851840 to target a release in 4.6.0, 4.6.z, but it targets "4.5.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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/test-infra repository.

@martinkunc
Copy link
Contributor

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "4.5.z" instead
  • expected dependent Bugzilla bug 1851840 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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/test-infra repository.

@martinkunc
Copy link
Contributor

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected dependent Bugzilla bug 1851840 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is NEW instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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/test-infra repository.

@martinkunc
Copy link
Contributor

/bugzilla refresh
/test e2e-aws

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh
/test e2e-aws

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/test-infra repository.

@martinkunc
Copy link
Contributor

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. labels Jun 29, 2020
@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1851840 is in the state VERIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Bugzilla bug 1851840 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

In response to this:

/bugzilla refresh

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jun 29, 2020
@martinkunc
Copy link
Contributor

/test e2e-aws

@iNecas
Copy link
Contributor

iNecas commented Jul 1, 2020

What was the change that actually makes the tests more stable?

Also I would love for @lina-nikiforova to give her blessing, as main author of this area of the repo.

@@ -7,6 +7,7 @@ test-unit:
.PHONY: test-unit

test-e2e:
go test ./test/integration -run ^\(TestPullSecretExists\)$$ -timeout 2h

Choose a reason for hiding this comment

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

do we need 2h here?

Copy link
Contributor

Choose a reason for hiding this comment

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

I have created another PR with shorter period here: #135

@@ -102,7 +133,7 @@ func restartInsightsOperator(t *testing.T) {

for _, pod := range pods.Items {
clientset.CoreV1().Pods("openshift-insights").Delete(pod.Name, &metav1.DeleteOptions{})
err := wait.PollImmediate(1*time.Second, 20*time.Minute, func() (bool, error) {
err := wait.PollImmediate(1*time.Second, 1*time.Minute, func() (bool, error) {

Choose a reason for hiding this comment

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

I don't think pods are usually deleted within 1 minute, I'd give it more time

Copy link
Contributor

Choose a reason for hiding this comment

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

Actually 1 minute is with quite a reserve. Normally it takes few seconds and Kubernetes is making sure that deletion wont be longer then Grace period, which is 30s in IO pod.
You can see moure about it here: https://cloud.google.com/blog/products/gcp/kubernetes-best-practices-terminating-with-grace

@@ -115,7 +146,7 @@ func restartInsightsOperator(t *testing.T) {
}

// check new pods are created and running
errPod := wait.PollImmediate(1*time.Second, 10*time.Minute, func() (bool, error) {
errPod := wait.PollImmediate(1*time.Second, 1*time.Minute, func() (bool, error) {

Choose a reason for hiding this comment

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

same, I don't think 1 minute is enough

@martinkunc
Copy link
Contributor

@iNecas Actually this is just a backport of #124, so I would need to create another PR to master with changes suggested here, if there will be some.
The main problem was that tests were modifying the cluster, for example removing secret, while other test was relying on existence of the same secret.
Code I added is reverting changes done in tests, so that other tests can run safely.

@martinkunc
Copy link
Contributor

/test e2e-aws

2 similar comments
@martinkunc
Copy link
Contributor

/test e2e-aws

@martinkunc
Copy link
Contributor

/test e2e-aws

@martinkunc
Copy link
Contributor

@lina-nikiforova Can you please approve, so that Ivan could add the label ?

@lina-is-here
Copy link

lgtm

@iNecas
Copy link
Contributor

iNecas commented Jul 17, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iNecas, openshift-cherrypick-robot

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2020
@martinkunc
Copy link
Contributor

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@martinkunc: This pull request references Bugzilla bug 1851839, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.z) matches configured target release for branch (4.5.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1851840 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1851840 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

In response to this:

/bugzilla refresh

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/test-infra repository.

@sdodson sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jul 30, 2020
@openshift-merge-robot openshift-merge-robot merged commit 8aafa0d into openshift:release-4.5 Jul 30, 2020
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: openshift/insights-operator#130. Bugzilla bug 1851839 has been moved to the MODIFIED state.

In response to this:

[release-4.5] Bug 1851839: Make e2e tests more stable

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants