-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[bug] Kubeflow workflow runs are in "Pending Execution" state #10901
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
@sureshmol Are you able to fix this issue? I am facing same. |
/reopen |
@imranrazakhan: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
@sureshmoligi: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
@imranrazakhan |
@sureshmol: Reopened this issue. In response to this:
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. |
I also have the same issue, how can this be debugged? |
This might be related: kubeflow/manifests#2850 After querying the .well-known issuer and setting that in the m2m requestauth (and restarting ml-persistence), the pipeline run statusses are updated correctly. However, the cron-job for refreshing the JWKS keys for the m2m issuer fails due to a faulty |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Environment
git clone https://github.com/kubeflow/manifests.git
cd manifests
while ! kustomize build example | kubectl apply -f -; do echo "Retrying to apply resources"; sleep 10; done
Kubeflow version: 1.8
Kubernetes version: 1.27
Steps to reproduce
After installation of kubeflow, All the pods are in running state:
I have created a pipeline from UI using a yaml file and pipeline is successfully created. See image below of the pipeline:
![image](https://private-user-images.githubusercontent.com/23389075/339435962-988d70f8-9f1a-42cd-bead-5b32e18c90af.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNDMyOTgsIm5iZiI6MTczOTM0Mjk5OCwicGF0aCI6Ii8yMzM4OTA3NS8zMzk0MzU5NjItOTg4ZDcwZjgtOWYxYS00MmNkLWJlYWQtNWIzMmUxOGM5MGFmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA2NDk1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE3ZWJlMjdjNzY5MzU5YzVjNTViMGEwMTA1MTIxMGFmZmQ1MDFiN2M4YjI4MzFmMGVlNDE4OWNhMjZlNWRhNTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.zC9NLG1faq8VkP3rEFWyW3Dy3YJOz-74bUHzpMoggtE)
When i create a Run for this pipeline. Run are going into Pending Execution State and when i open the run, graphs are not loading yet. See image below:
![image](https://private-user-images.githubusercontent.com/23389075/339436210-55e9a3f4-0453-47a1-965c-81f3f9adce97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNDMyOTgsIm5iZiI6MTczOTM0Mjk5OCwicGF0aCI6Ii8yMzM4OTA3NS8zMzk0MzYyMTAtNTVlOWEzZjQtMDQ1My00N2ExLTk2NWMtODFmM2Y5YWRjZTk3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA2NDk1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI3MTNiMWI5ZTNjM2FlNGM0YjRkYzg1OWVkYTNjMzhjNTk2OWJmMzhkYzgxYmU5NTc1YmQxNDE1YTM2MDgwNmImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.pVEg4uavZZ1AhOmKP4QOOlUerZOUr8GUZBn4eURS6tw)
![image](https://private-user-images.githubusercontent.com/23389075/339436365-b0203bce-5387-4565-96eb-5014d0c5c82c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNDMyOTgsIm5iZiI6MTczOTM0Mjk5OCwicGF0aCI6Ii8yMzM4OTA3NS8zMzk0MzYzNjUtYjAyMDNiY2UtNTM4Ny00NTY1LTk2ZWItNTAxNGQwYzVjODJjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA2NDk1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM0ZmNjMGQxYjhlNDBkOTM0NmJkMWNkMzhhODAwNzkwM2Q4YWQ5Y2I1N2NkYmNiNWYwN2JlOGQ4M2QzMzM0YzEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.FrChxAyT6NHXihx8TJfYvGJsk_S106hGa8nEErr_flY)
But when I check for the workflow status using kubectl. Workflows are running started and completed successfully. Please see image below:
![image](https://private-user-images.githubusercontent.com/23389075/339441119-6cb153c4-566f-42b0-973a-011eb2c7cfc2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNDMyOTgsIm5iZiI6MTczOTM0Mjk5OCwicGF0aCI6Ii8yMzM4OTA3NS8zMzk0NDExMTktNmNiMTUzYzQtNTY2Zi00MmIwLTk3M2EtMDExZWIyYzdjZmMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA2NDk1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWNhMDYyODc4NDE3MzQ4OTBjOWYyNTRkZGEwYWMzYTc4MWUwNDgyOGM2ZmYzMDEzOTc1MzBjYzM3ZWJlYWVhOTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.orTyF_Jgzg_8Hs-uo9cmz_JH3cVURqAx7pM0nJNIPPo)
Expected result
I should be seeing the actual status of the workflows in the UI.
Can you please help me with this Bug, I am unable to figure out a solution for this
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: