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

make setup-integration-tests fail #5454

Closed
chozhansoftware opened this issue Sep 21, 2022 · 6 comments
Closed

make setup-integration-tests fail #5454

chozhansoftware opened this issue Sep 21, 2022 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@chozhansoftware
Copy link

chozhansoftware commented Sep 21, 2022

Describe the bug:

The make setup-integration-tests fails with the following error:

% make setup-integration-tests                
/Users/<username>/cert-manager-code/cert-manager/_bin/tools/helm package --app-version=v1.9.0-beta.1-124-g231a0460b40e18 --version=v1.9.0-beta.1-124-g231a0460b40e18 --destination "_bin/" ./_bin/helm/cert-manager
Error: validation: chart.metadata.version is required
make: *** [_bin/cert-manager-v1.9.0-beta.1-124-g231a0460b40e18.tgz] Error 1

Expected behaviour:

The command runs successfully

Steps to reproduce the bug:

  • clone the repo
  • cd cert-manager
  • Run make setup-integration-tests

Anything else we need to know?:
I tried in Mac and Ubuntu 18.04. It failed with exactly same error.

Environment details::

  • Kubernetes version: Not applicalble
  • Cloud-provider/provisioner: N/A
  • cert-manager version: master, 231a046
  • Install method: N/A

/kind bug

@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 21, 2022
@chozhansoftware
Copy link
Author

In this file _bin/helm/cert-manager/Chart.yaml, I had to edit the version field to set the value to version: "v0.0.0". After making this change manually, the make setup-integration-tests worked fine! This is a workaround.

@iomarcovalente
Copy link

this fails with make e2e-setup too

@jetstack-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

@jetstack-bot jetstack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 29, 2022
@jetstack-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

@jetstack-bot jetstack-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 28, 2023
@jetstack-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

@jetstack-bot
Copy link
Contributor

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants