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

🐛 E2E tests failing due to KUBECONFIG weirdness #435

Closed
cprivitere opened this issue Sep 19, 2022 · 0 comments · Fixed by #436
Closed

🐛 E2E tests failing due to KUBECONFIG weirdness #435

cprivitere opened this issue Sep 19, 2022 · 0 comments · Fixed by #436
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@cprivitere
Copy link
Member

E2E tests appear broken. Investigation points to kubectl not being able to connect to the cluster when it's time to install CPEM. This doesn't happen in the quickstart test, but does happen in most of the others. I believe this is due to some oddity where KUBECONFIG is set by the testing framework (this is just a theory). If we add explicit code back in to declare KUBECONFIG=/etc/kubernetes/admin.conf, it should resolve the issue.

@cprivitere cprivitere self-assigned this Sep 19, 2022
@cprivitere cprivitere added the kind/bug Categorizes issue or PR as related to a bug. label Sep 19, 2022
@cprivitere cprivitere changed the title E2E tests failing due to KUBECONFIG weirdness 🐛 E2E tests failing due to KUBECONFIG weirdness Sep 19, 2022
@cprivitere cprivitere modified the milestones: 0.7.0, 0.6.1 Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant