Installation of Zusam fails

Hi @Team Genius

I was just about to install Zusam, but it failed with the following error message:

add-module ghcr.io/geniusdynamics/zusam:latest 1
<7>podman-pull-missing ghcr.io/geniusdynamics/zusam:latest
Trying to pull ghcr.io/geniusdynamics/zusam:latest
Error: unable to copy from source docker://ghcr.io/geniusdynamics/zusam:latest: initializing source docker://ghcr.io/geniusdynamics/zusam:latest: Requesting bearer token: received unexpected HTTP status: 403 Forbidden
Traceback (most recent call last):
File “/usr/local/agent/bin/podman-pull-missing”, line 35, in
subprocess.run([‘podman’, ‘pull’, image_url]).check_returncode()
File “/usr/lib64/python3.11/subprocess.py”, line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '[‘podman’, ‘pull’, 'ghcr.io/geniusdynamics/zusam:latest’]’ returned non-zero exit status 125.
Traceback (most recent call last):
File “/var/lib/nethserver/cluster/actions/add-module/50update”, line 84, in
agent.run_helper(‘podman-pull-missing’, image_url, progress_callback=agent.get_progress_callback(0,33)).check_returncode()
File “/usr/lib64/python3.11/subprocess.py”, line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '(‘podman-pull-missing’, 'ghcr.io/geniusdynamics/zusam:latest’)’ returned non-zero exit status 1.

1 Like

For this i had just done the initial program setup but did not dig deep into it

1 Like

@allall, please note that when an app announcement has not been made yet, it says so on the wiki. In this case “The Zusam app announcement TBA”.

So TBA means not officially released yet, but a work in progress. But feel free to test and provide feedback!

2 Likes

Thanks for the Info @LayLow.

But wouldn’t it be better to wait with the release until the app is working?

Github is always a work in progress and is a public directory. Hence the specific mentioning on the wiki if there was an announcement for a stable/test release. The announcement by the module author will hold the specific details. Also the wiki show the maturity of modules where can filter on the release status ( See the app directory and filtering options) and explenation / caption (blue buttons) .

It shows that “Zusam” is still listed as an Alpha release.

2 Likes

Thank you @LayLow

Now i understand the situation much better.

1 Like

For those usually scouting our repo, just to help you. Here is our release metric.

Without Release
Any NS8 module without a release of any kind on github, do not install, it might not work.

Dev tagged Release
Any App with a dev tagged release, usually means, we have gotten the foundations ok, and you can install configure and possibly play around with it, might still need alot of works to be done.
These are mostly, development testing release.

Beta release
this are fully working modules and apps, However, might still need some additional features, env or functions to be added, so we are not comfortable to release it it, but it can be tested by community.
Migration to release, or RC, might require manual steps.

Release candidates (RC)
When you see a Module with RC tag, usually, We have finished on it, and stopped adding any new features. Migration to a release is feasible. Sometimes we skip this for simple projects

Numbered release
This is usually ready for prime time, and we might be adding to our genforge soon.

2 Likes

Thanks, but please note this is ONLY the case for the “Genius” repo. Other repo’s may have other schematics, so please always check the respective “readme.md” and the forum announcements.

Currently there are 16 different repo’s.

2 Likes

@LayLow is there a possibility of adding number of apps on each repo, from this page ns8:repositories [NethServer & NethSecurity]

That can be done in the apps directory overview by selecting the desired repo from the drop-down list. GeniusD repo shows Found: 86 / 175, so the repo has 86 apps out of a total of 175 available apps.

1 Like