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

Github Action-Release Helm Charts is failing #1353

Open
zhanggbj opened this issue Dec 16, 2024 · 1 comment
Open

Github Action-Release Helm Charts is failing #1353

zhanggbj opened this issue Dec 16, 2024 · 1 comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@zhanggbj
Copy link
Collaborator

Which jobs are failing?

https://github.com/kubernetes/cloud-provider-vsphere/actions/runs/12347309309/job/34454202551#step:5:107

Which tests are failing?

Release Helm Charts

Looking up latest tag...
Discovering changed charts since 'v1.32.0-rc.0'...
Installing chart-releaser on /opt/hostedtoolcache/cr/v1.6.1/x86_64...
Adding cr directory to PATH...
Packaging chart 'charts/vsphere-cpi'...
Successfully packaged chart in /home/runner/work/cloud-provider-vsphere/cloud-provider-vsphere/charts/vsphere-cpi and saved it to: .cr-release-packages/vsphere-cpi-1.32.1.tgz
Releasing charts...
Error: error creating GitHub release vsphere-cpi-chart-1.32.1: POST https://api.github.com/repos/kubernetes/cloud-provider-vsphere/releases: 403 Resource not accessible by integration []
Usage:
  cr upload [flags]

Since when has it been failing?

Last successful run is 1 month ago

Testgrid link

No response

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Relevant SIG(s)

/sig

@zhanggbj zhanggbj added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Dec 16, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants