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

Error regarding syncing workflow #869

Closed
abishek-murali opened this issue Feb 27, 2019 · 1 comment
Closed

Error regarding syncing workflow #869

abishek-murali opened this issue Feb 27, 2019 · 1 comment

Comments

@abishek-murali
Copy link

Hi all!

I've been playing with Kubeflow and noticed that once my pipelines completed the ml-persistence-agent pod continued spewing out the following error at a regular intervals -

time="2019-02-27T16:32:26Z" level=error msg="Permanent failure while syncing resource 
(kubeflow/calculation-pipeline-grqzn): CustomError (code: 1): Syncing Workflow (calculation-pipeline-
grqzn): permanent failure: CustomError (code: 1): Error while reporting workflow resource (code: 
InvalidArgument, message: Report workflow failed.: Invalid input error: Failed to update run 
ce4322d1-3a11-11e9-8c52-0a58ac1f1417. Row not found.): rpc error: code = InvalidArgument desc = 
Report workflow failed.: Invalid input error: Failed to update run 
ce4322d1-3a11-11e9-8c52-0a58ac1f1417. Row not found., &{TypeMeta:{Kind: APIVersion:} 
ObjectMeta:{Name:calculation-pipeline-grqzn GenerateName:calculation-pipeline- 
Namespace:kubeflow 

I exceeded my logzio limit for the day and these errors are a significant portion of them. Any help regarding this error or ways to suppress these logs would be helpful

@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

This should be fixed once we garbage collect the Kubernetes resources (i.e. workflows) that have been terminated. Resolving as a duplicate of #844

@vicaire vicaire closed this as completed Mar 26, 2019
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants