-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Cache Deployer - Error when upgrading in GCP marketplace #4299
Comments
/assign @Ark-kun However, that seems to magically create enough resources so that the second run have all we need. |
and cache-server is no longer working properly, when I create new runs, they don't get cached results.
I'm getting these error messages. |
Thank you for finding and reporting this issue.
The deployer could not re-install the config, so the secret and the config became out of sync. It's pretty easy to fix - we just need to add the proper roles to the deployer. |
…4299 (kubeflow#4320) * Backend - Cache - Fixed reinstallation by adding missing roles * Stop ignoring the deletion errors * Added patch permission as well It should not be triggered, but might be useful in the future.
…4299 (kubeflow#4320) * Backend - Cache - Fixed reinstallation by adding missing roles * Stop ignoring the deletion errors * Added patch permission as well It should not be triggered, but might be useful in the future.
…4299 (kubeflow#4320) * Backend - Cache - Fixed reinstallation by adding missing roles * Stop ignoring the deletion errors * Added patch permission as well It should not be triggered, but might be useful in the future.
What steps did you take:
What happened:
Here's the error log for cache deployer:
What did you expect to happen:
cache-deployer should succeed for the first run
Environment:
How did you deploy Kubeflow Pipelines (KFP)?
GCP marketplace
KFP version: Upgrade from 0.5.1 to 1.0.0
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind bug
The text was updated successfully, but these errors were encountered: