openwrt / openwrt/asu

invalid config provided: invalid network "pasta"

Open
#1,601 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
450
Forks
111
PR merge metrics
No merged PRs in 30d

Description

I tried updating FW on my router using owut download, using my self-hosted ASU server. However, the owut command fails with the error in the title.

Full output here

ASU-Server     https://asu.my.domain
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        bananapi_bpi-r3
Package-arch   aarch64_cortex-a53
Version-from   24.10.4 r28959-29397011cc (kernel 6.6.110)
Version-to     24.10.6 r29141-81be8a8869 (kernel 6.6.127)
109 packages are out-of-date
Request hash:
  9e263cac716212aa26a61989e25734730e993dbf0202cc1a7f23be64b170ea92
--
Status:   queued - 0 ahead of you
Progress:   0s total =   0s in queue +   0s in build
--
Status:   init
Progress:   1s total =   0s in queue +   1s in build
--
Status:   failed
Progress:   3s total =   0s in queue +   3s in build

Build failed in   3s total =   0s in queue +   3s to build:
ASU server stderr =
Traceback (most recent call last):
  File "/app/.venv/lib/python3.14/site-packages/rq/worker.py", line 1439, in perform_job
    return_value = job.perform()
  File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1318, in perform
    self._result = self._execute()
                   ~~~~~~~~~~~~~^^
  File "/app/.venv/lib/python3.14/site-packages/rq/job.py", line 1376, in _execute
    result = self.func(*self.args, **self.kwargs)
  File "/app/asu/build.py", line 463, in build
    result = _build(build_request, job)
  File "/app/asu/build.py", line 194, in _build
    container = podman.containers.create(
        image,
    ...<7 lines>...
        environment=environment,
    )
  File "/app/.venv/lib/python3.14/site-packages/podman/domain/containers_create.py", line 382, in create
    response.raise_for_status(not_found=ImageNotFound)
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.14/site-packages/podman/api/client.py", line 85, in raise_for_status
    raise APIError(cause, response=self._response, explanation=message)
podman.errors.exceptions.APIError: 500 Server Error: Internal Server Error (invalid config provided: invalid network "pasta")

ERROR: Build failed with status 500
The above errors are often due to the upgrade server lagging behind the
build server, first suggestion is to wait a while and try again.

I've tried debugging the problem myself, but I think my podman knowledge is lacking. I've been using the netavark network backend until now with no issues, but given the error here it appears that I have to use pasta now - is that right? Or do I just need to manually create a "pasta" network somehow?

More info that may help:

podman-compose --version
['podman', '--version', '']
using podman version: 4.3.1
podman-composer version  1.0.3
podman --version
podman version 4.3.1
pasta --version
pasta unknown version
Copyright Red Hat
GNU Affero GPL version 3 or later <https://www.gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Apt shows this version of the passt package:
passt/oldstable,now 0.0~git20230309.7c7625d-1 amd64 [installed]

I'm running Debian 12 (bookworm) which may explain why some of these are rather old. I started down the path to updating to 13 (trixie), but ran into some unrelated issues I'd rather avoid solving unless it's really necessary. Any idea what's wrong and how I can get my server building again?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at asu/build.py around the podman.containers.create call reported at line 194, then compare the server's Podman, pasta/passt, and Debian versions with the network configuration used there. Reproduce the build failure and determine whether the ASU setup supports this network configuration on the reported environment. Done means the same owut request completes without the invalid-network error.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
backend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.