[GH-ISSUE #10027] YAML parsing fails with cryptic error "Fatal Error: Failed to parse assistant: models.0: Invalid inputmodels.1: Invalid input" #6576

Closed
opened 2026-04-12 18:12:32 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @sammyvoncheese on GitHub (Mar 28, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10027

What is the issue?

After updating to version 1.0.5 I got an error message when loading. I have a large config.yaml which has grown over time, with lots of old/unnecessary or possibly outdated stuff in it. Because of this, every model had tools enabled (I never checked each one to see if they actually supported tools)

Image

The error is caused by values this value in the yaml. In the cases I showed, those 2 models will fail because of
capabilities: - tools_use

Removing that from the yaml will allow it to load.

Here are 2 examples where it fails.

schema: v1
version: 1.0.0


models:

  - name: gemma3:27b
    provider: ollama
    model: gemma3:27b
    apiBase: http://127.0.0.1:11434
    defaultCompletionOptions:
        maxtokens: 4056
        temperature: 0.2
        topP: .2
    capabilities:
      - tools_use
    roles:
      - chat

  - name: qwen2.5:32b
    provider: ollama
    model: qwen2.5:32b
    apiBase: http://127.0.0.1:11434
    defaultCompletionOptions:
        maxtokens: 8000
        temperature: 0.2
        topP: .2
    capabilities:
      - tools_use
    roles:
      - chat
    ``` 


### Relevant log output

```shell

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

ollama version is 0.6.2

Originally created by @sammyvoncheese on GitHub (Mar 28, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10027 ### What is the issue? After updating to version 1.0.5 I got an error message when loading. I have a large config.yaml which has grown over time, with lots of old/unnecessary or possibly outdated stuff in it. Because of this, every model had tools enabled (I never checked each one to see if they actually supported tools) ![Image](https://github.com/user-attachments/assets/d00552d0-995f-4b68-8b7b-e3edd29bf3ba) The error is caused by values this value in the yaml. In the cases I showed, those 2 models will fail because of ```capabilities: - tools_use``` Removing that from the yaml will allow it to load. Here are 2 examples where it fails. ```name: "config.yaml" schema: v1 version: 1.0.0 models: - name: gemma3:27b provider: ollama model: gemma3:27b apiBase: http://127.0.0.1:11434 defaultCompletionOptions: maxtokens: 4056 temperature: 0.2 topP: .2 capabilities: - tools_use roles: - chat - name: qwen2.5:32b provider: ollama model: qwen2.5:32b apiBase: http://127.0.0.1:11434 defaultCompletionOptions: maxtokens: 8000 temperature: 0.2 topP: .2 capabilities: - tools_use roles: - chat ``` ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version ollama version is 0.6.2
GiteaMirror added the bug label 2026-04-12 18:12:32 -05:00
Author
Owner

@rick-github commented on GitHub (Mar 28, 2025):

Doesn't appear to be an ollama issue. ollama does't parse YAML files for configuration.

<!-- gh-comment-id:2761941220 --> @rick-github commented on GitHub (Mar 28, 2025): Doesn't appear to be an ollama issue. ollama does't parse YAML files for configuration.
Author
Owner

@sammyvoncheese commented on GitHub (Apr 2, 2025):

my bad, wrong repo.. ugh.

<!-- gh-comment-id:2773850015 --> @sammyvoncheese commented on GitHub (Apr 2, 2025): my bad, wrong repo.. ugh.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#6576