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

Enable test for persistent storage #303

Merged

Conversation

kosyfrances
Copy link
Contributor

We no longer run tests using minikube in a VM on the CI infrastructure
but with GCP

Fixes #292

Depends on #302

@kosyfrances kosyfrances self-assigned this Jun 29, 2018
@kosyfrances kosyfrances force-pushed the kosy/test-persistent-storage branch 4 times, most recently from d947a03 to 6305e52 Compare July 3, 2018 13:40
@krnowak
Copy link
Contributor

krnowak commented Jul 3, 2018

Needs a rebase.

We no longer run tests using minikube in a VM on the CI infrastructure
but with GCP

Signed-off-by: Kosy Anyanwu <kosy@kinvolk.io>
@kosyfrances kosyfrances force-pushed the kosy/test-persistent-storage branch from 6305e52 to 4cea43c Compare July 3, 2018 14:03
Copy link
Contributor

@krnowak krnowak left a comment

Choose a reason for hiding this comment

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

The test makes me wonder if we should validate that the pods are actually created. The creation of a pod can fail if the persistent volume claim can't be fulfilled. And I'm not sure if the tests actually tests it. What do you think?

@@ -255,6 +252,13 @@ func TestPersistentStorage(t *testing.T) {
}
})(persisted.Name)

// Delete the ephemeral resource created
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we also do the same for persistent one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, other tests do not use it so I skipped it instead. The whole cluster still gets deleted at the end of the test anyway.

@kosyfrances
Copy link
Contributor Author

The test makes me wonder if we should validate that the pods are actually created. The creation of a pod can fail if the persistent volume claim can't be fulfilled. And I'm not sure if the tests actually tests it. What do you think?

@krnowak I am not sure right now, let me think about it for a bit.

@kosyfrances kosyfrances force-pushed the kosy/test-persistent-storage branch 3 times, most recently from 5ad23ae to 4cea43c Compare July 5, 2018 10:53
@kosyfrances
Copy link
Contributor Author

kosyfrances commented Jul 5, 2018

@krnowak The test actually waits for the persisted pod to be in a running state here https://github.com/kinvolk/habitat-operator/blob/4cea43c6323f59495c811705d3070a5b6c423d5a/test/e2e/v1beta1/operator_test.go#L262
so yes, pods are actually created

@krnowak
Copy link
Contributor

krnowak commented Jul 6, 2018

Oh, I overlooked that. In that case, LFAD.

@krnowak krnowak merged commit 3c975ca into habitat-sh:master Jul 6, 2018
@krnowak krnowak deleted the kosy/test-persistent-storage branch July 6, 2018 10:58
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.

2 participants