Open furkatgofurov7 opened 1 year ago
Cluster API does nothing: https://github.com/kubernetes-sigs/cluster-api/blob/main/Makefile#L836
So, I think we just need to document this behavior and allow users to run "make docker-build-e2e && make test-e2e" if they don't have the image built.
Cluster API does nothing: https://github.com/kubernetes-sigs/cluster-api/blob/main/Makefile#L836
So, I think we just need to document this behavior and allow users to run "make docker-build-e2e && make test-e2e" if they don't have the image built.
yes, was checking it as well. Something like https://github.com/kubernetes-sigs/cluster-api/blob/f3e3bda15c62f6cecb235c943f4ff337ce4ab5d1/docs/book/src/developer/testing.md?plain=1#L178C1-L180 should suffice in that case, but not sure where we need to put them
/triage accepted /kind documentation /help /good-first-issue
@furkatgofurov7: This request has been marked as suitable for new contributors.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
/remove-kind bug
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
What steps did you take and what happened: When running e2e tests locally using Makefile targets (
make test-e2e
ormake test-e2e-run
) both will fail, IF you have never run themake-docker-build-e2e
target on the repo (if you have an operator image with dev tag locally, you would not see this problem, but that is not the case for everyone) which builds an operator image withdev
tag.That is because
make test-e2e-run
sets E2E_OPERATOR_IMAGE to http://gcr.io/k8s-staging-capi-operator/cluster-api-operator:dev, spins up a kind cluster and loads that image into cluster:Later on in the tests, operator deployment will not come up properly and fail:
What did you expect to happen: run
make test-e2e
andmake test-e2e-run
successfullyTo reproduce:
Additional information: I see we have 2 options in this case:
make-docker-build-e2e
target tomake test-e2e-run
so that we always build the image first before running e2e tests locallymake-docker-build-e2e
is a prerequisite for successfully running e2e tests locallyAny other suggestions?
Environment:
kubectl version
):/etc/os-release
):macOS/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]