Cannot create pipelines

[ProjectMoon]

Which component(s) is affected?

Kubero UI

Describe the bug

Whenever I try to create a pipeline using the UI, I get a JavaScript error about this.buildpacks[0] being undefined.

Uncaught TypeError: can't access property "value", this.buildpackList[0] is undefined
    createPipeline https://cloud.example.com/assets/form-Do9FEJ7E.js:1
    14 https://cloud.example.com/assets/form-Do9FEJ7E.js:24
    yd https://cloud.example.com/assets/index-DWKKnYyN.js:26
    eo https://cloud.example.com/assets/index-DWKKnYyN.js:17
    pt https://cloud.example.com/assets/index-DWKKnYyN.js:17
    pt https://cloud.example.com/assets/index-DWKKnYyN.js:17
    n https://cloud.example.com/assets/index-DWKKnYyN.js:25

Steps to reproduce

1. Click new pipeline.
2. Fill in form (build from source on or off; doesn't matter)
3. Click create.

Expected behavior

Pipeline created.

Screenshots

No response

Additional information

Is the buildpack list supposed to be downloaded server-side maybe? Perhaps there's something wrong with my server config? Everything seems to be up and running.

Debug information

No response

[mms-gianni]

There might be a typo in the default config v2 default config.

https://github.com/kubero-dev/kubero/blob/main/server/config.example.yaml#L51

This is fixed in Version 3 since this config part was migrated to a local sqliteDB

[ProjectMoon]

Is there a way to either: upgrade to v3 beta/alpha/whatever, or fix the typo?

I am only testing it out, so the installation is clean and easily wipeable.

[ProjectMoon]

Like I see the config, but where do I edit that file? 🤔 Is it part of the kubero-config config map?

[ProjectMoon]

OK, found the instructions for testing the RC. Getting this when running rc18 for v3 though:

[Kubero] 1  - 08/08/2025, 10:34:19 AM   ERROR [DatabaseService] PrismaClientInitializationError: Error querying the database: Error code 14: Unable to open the database file

PrismaClientInitializationError:
Invalid `prisma.runpack.findFirst()` invocation:


Error querying the database: Error code 14: Unable to open the database file
    at ri.handleRequestError (/app/server/node_modules/@prisma/client/runtime/library.js:121:7759)
    at ri.handleAndLogRequestError (/app/server/node_modules/@prisma/client/runtime/library.js:121:6784)
    at ri.request (/app/server/node_modules/@prisma/client/runtime/library.js:121:6491)
    at async l (/app/server/node_modules/@prisma/client/runtime/library.js:130:9812)
    at async DatabaseService.seedRunpacks (/app/server/database/database.service.js:374:30) {
  clientVersion: '6.13.0',
  errorCode: undefined,
  retryable: undefined
}

[ProjectMoon]

OK so on 2.x, I changed buildpacks to buildPacks (capital P) and now I'm able to create a pipeline!

[mms-gianni]

Is there a way to either: upgrade to v3 beta/alpha/whatever, or fix the typo?

I am only testing it out, so the installation is clean and easily wipeable.

Sure. I think rc.18 works as expected (need to fix the forgejo part probably)
https://github.com/kubero-dev/kubero/pkgs/container/kubero%2Fkubero/477166073?tag=v3.0.0-rc.18

// edit
The release date is planned for Monday (as long I can't find any blocking bug)

[mms-gianni]

Also make sure to use the latest operator image
https://github.com/kubero-dev/kubero-operator/pkgs/container/kubero-operator%2Fkuberoapp/477159067?tag=v0.1.10-rc.5

[ProjectMoon]

Hmm, switched operator image and now pods are saying pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.. It seems to want a kubero-data volume?

[ProjectMoon]

So what I did was update the image on the resource in the operator system namespace. Is that enough to get the operator updated?

[mms-gianni]

The UI image also

[ProjectMoon]

The UI image also

I'm running v3 rc18 of the UI and the v1.10 of the operator, I think

[mms-gianni]

I was not able to reproduce it on my cluster. Did you manage to run it ? I'm also available (CEST) on discord for quicker Answers.

[ProjectMoon]

Nope. The volume needs to be created, I guess. Dunno why it didn't create automatically. The persistent volume claim is just pending, which means the pod is pending.