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

Error Starting local Podset Operator test (crash) #11

Open
ryanj opened this issue Jun 4, 2019 · 8 comments
Open

Error Starting local Podset Operator test (crash) #11

ryanj opened this issue Jun 4, 2019 · 8 comments
Labels
help wanted Extra attention is needed

Comments

@ryanj
Copy link
Member

ryanj commented Jun 4, 2019

In the "Start the Operator" step of the Podset Operator section, the user is asked to test their local operator code by running:

operator-sdk up local --namespace myproject

Expected: Watch to see if the podset operator is started. Try listing pods or deployments related to the operator for the initial test. Then load a CR and watch for pods that are created by the operator code.

Actual: Crash / closed connection. Users can restart the workshop by clicking in the top right corner to open the nav menu, then select "Restart Session".

@ryanj
Copy link
Member Author

ryanj commented Jun 4, 2019

This is the last big step in the podset operator section. High priority bug

@ryanj ryanj added the help wanted Extra attention is needed label Jun 4, 2019
@madorn
Copy link
Contributor

madorn commented Jun 6, 2019

I'm seeing this issue and also seeing signal: killed in the middle of runnning operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=PodSet.

Golang version within terminal dashboard pod is go1.11.5, this is below the prereq.

Before continuing to troubleshoot further should we remove the package here and manually fetch/install/setup go1.12.5 in the build file ?

@ryanj
Copy link
Member Author

ryanj commented Jun 6, 2019

@GrahamDumpleton
Copy link

It is installed from the .workshop/build script. Update to whatever tool versions you need.

@madorn
Copy link
Contributor

madorn commented Jun 9, 2019

See #13.

@madorn
Copy link
Contributor

madorn commented Jun 9, 2019

#14 should resolve the issues with the operator-sdk crashing.

@jorgemoralespou
Copy link
Contributor

Both PR are merged, so after re testing this one should be closed

@madorn
Copy link
Contributor

madorn commented Jun 10, 2019

@jorgemoralespou thanks Jorge. tested and looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants