You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Incorrect API key validation error when creating a new OLLAMA model #1945
I have searched the existing issues to avoid creating a duplicate
By submitting this issue, you agree to follow our Code of Conduct
I am using the latest version of the software
I have tried to clear cache/cookies or used incognito mode (if ui-related)
I can consistently reproduce this issue
🎯 Affected Service(s)
UI Service
🚦 Impact/Severity
Minor inconvenience
🐛 Bug Description
When I selected OLLAMA as model , while creating new model , I am getting validation error that "Please fill in all required fields and correct any errors."
I checked by locally running ui & cluster that which fields are required even though I have filled all required fields, the on console I got the error message in validation map that "API key is required for new models (except for Ollama or when you don't need an API key)"
I checked the I have selected OLLAMA model only , still I am getting this error.
Also validation message propagated on UI is also wrong.
🔄 Steps To Reproduce
Go to "/models/new"
Try to create new model by selecting ollama as provider.
Select ollama model (e.g. llama2)
Click Create Model. You will get message that "Please fill in all required fields and correct any errors."
🤔 Expected Behavior
Validation message is wrong , we should not get this validation message as for ollama api key is not required.
Also validation message propagated on UI is also wrong.
📱 Actual Behavior
Getting wrong validation message on UI , hence not able to create the model.
Activity
gauravshinde1729 commentedon May 30, 2026
I am working on this , I will submit the PR for this.
fix(ui): remove console log (kagent-dev#1945)
gauravshinde1729 commentedon May 30, 2026
@peterj Can you please check this PR
#1946
Thanks !
Fix/1945 fix for wrong validation being triggered (#1946)