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

smoke test is not working as expected #1482

Closed
Amulyam24 opened this issue Nov 8, 2023 · 3 comments · Fixed by #1512
Closed

smoke test is not working as expected #1482

Amulyam24 opened this issue Nov 8, 2023 · 3 comments · Fixed by #1512
Assignees
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@Amulyam24
Copy link
Contributor

/kind bug
/area provider/ibmcloud

https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-cluster-api-provider-ibmcloud-smoke-test

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/provider/ibmcloud Issues or PRs related to ibmcloud provider labels Nov 8, 2023
@Amulyam24
Copy link
Contributor Author

/assign

@mkumatag mkumatag added this to the v0.7 milestone Nov 9, 2023
@Prajyot-Parab
Copy link
Contributor

@Amulyam24 Is this issue still relevant? seems like a false alarm to me (can you please share more data/log if its persistent)

@Amulyam24
Copy link
Contributor Author

Amulyam24 commented Nov 15, 2023

@Prajyot-Parab, yes this is still a relevant issue. If you check the logs of the current runs, the test stops after building the controller image but ideally the test should create a kind cluster and check if the controllers are deployed successfully.

Logs from older runs:
152289762-e00ec253-a7c3-406a-8fbf-1096a6d05367

Will check on what changed and fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants