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

Handle test namespace creation and deletion as operator-sdk names are… #901

Closed
wants to merge 1 commit into from
Closed

Handle test namespace creation and deletion as operator-sdk names are… #901

wants to merge 1 commit into from

Conversation

kevinearls
Copy link
Contributor

… too long.

The update to operator-sdk 0.15.1 included a change where namespace names became much longer. https://github.com/operator-framework/operator-sdk/blob/master/pkg/test/context.go#L53 This resulted in a number of tests failing on OpenShift because of route names that were too long and other issues.

With this change tests run on OpenShift will manage the creation and deletion of namespaces instead of using the one created by the operator sdk.

Signed-off-by: Kevin Earls [email protected]

@jpkrohling
Copy link
Contributor

Question: what exactly is failing? If it's the route that we talked before, then the bug is actually in the operator, as it shouldn't create a route with an invalid name.

By the way, this is going to conflict with #897.

@kevinearls
Copy link
Contributor Author

@jpkrohling In one case it was definitely the route name. The others were not so obvious, so I was hoping to use this as a way to fix tests, and then investigate if necessary.

I can investigate the other failures before proceeding.

@kevinearls kevinearls closed this Feb 25, 2020
@kevinearls
Copy link
Contributor Author

This is no longer needed as the problem was fixed with #904 and #915

@kevinearls kevinearls deleted the fix-test-namespaces branch February 25, 2020 09:45
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