ERROR when installing from scratch (jboss/keycloak, repository does not exist)

[nb_glur (Stephan Glur)]

Hi,
when trying to install from scratch, following this manual:
https://eaasi.gitlab.io/eaasi_user_handbook/overview/install/setup.html

It seems like jboss/keycloak is no longer available for download, and therefore eaasi deployment fails:

Updating password for user 'webapi'...
ALTER ROLE
Stopping eaasi-database ...
[1A[2KStopping eaasi-database ... [32mdone[0m[1BRemoving eaasi-database ...
[1A[2KRemoving eaasi-database ... [32mdone[0m[1BRemoving network eaasi

stdout_lines:

TASK [update service facts] *************************************************************************************************************************************************************************************
ok: [eaas-gateway] => changed=false
censored: ‘the output has been hidden due to the fact that ‘‘no_log: true’’ was specified for this result’

TASK [set_fact] *************************************************************************************************************************************************************************************************
ok: [eaas-gateway] => changed=false
ansible_facts:
_eaas_service: eaas.service

TASK [ensure eaas-server is restarted] **************************************************************************************************************************************************************************
fatal: [eaas-gateway]: FAILED! => changed=false
msg: |-
Unable to start service eaas.service: Job for eaas.service failed because the control process exited with error code.
See “systemctl status eaas.service” and “journalctl -xe” for details.

PLAY RECAP ******************************************************************************************************************************************************************************************************
eaas-gateway : ok=106 changed=19 unreachable=0 failed=1 skipped=37 rescued=0 ignored=1

emil@emil-ubuntu:/opt/eaasi-installer$ systemctl status eaas.service
● eaas.service - EaaS Service runing at /opt/eaasi
Loaded: loaded (/etc/systemd/system/eaas.service; enabled; vendor preset: enabled)
Active: activating (start-post) (Result: exit-code) since Fri 2024-09-06 16:01:54 CEST; 1min 6s ago
Process: 22539 ExecStart=/usr/local/bin/docker-compose --project-name eaas --file ./docker-compose.yaml --file /opt/eaasi/eaasi-ui/docker-compose.yaml up (code=exited, status=1/FAILURE)
Process: 22532 ExecStartPre=/opt/eaasi/hooks/runner.sh pre-start (code=exited, status=0/SUCCESS)
Main PID: 22539 (code=exited, status=1/FAILURE); Control PID: 22540 (sh)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/eaas.service
├─22540 sh /opt/eaasi/hooks/runner.sh post-start
├─22546 sh ./01-update-keycloak-config.sh
└─24130 sleep 1s

Sep 06 16:01:54 emil-ubuntu systemd[1]: Starting EaaS Service runing at /opt/eaasi…
Sep 06 16:01:54 emil-ubuntu runner.sh[22532]: [HOOKS] No pre-start hooks found!
Sep 06 16:01:54 emil-ubuntu runner.sh[22540]: [HOOKS] Running post-start hooks…
Sep 06 16:01:54 emil-ubuntu runner.sh[22540]: [HOOKS] → 01-update-keycloak-config.sh
Sep 06 16:01:55 emil-ubuntu docker-compose[22539]: Pulling keycloak (jboss/keycloak:15.0.2)…
Sep 06 16:01:56 emil-ubuntu docker-compose[22539]: The image for the service you’re trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.
Sep 06 16:01:56 emil-ubuntu docker-compose[22539]: Continue with the new image? [yN]pull access denied for jboss/keycloak, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied
Sep 06 16:01:56 emil-ubuntu systemd[1]: eaas.service: Main process exited, code=exited, status=1/FAILURE

Is maybe the eaasi-installer or a referenced container outdated?

Many thanks and BR,
Stephan

[ethan.gates]

Hi @nb_glur , indeed, it looks like the jboss/keycloak repository has been deprecated and should be replaced with quay.io/keycloak/keycloak. It may be possible to fix this by editing the relevant config line in the docker-compose.yaml file generated by the eaasi-installer (even after a partial/failed deployment, it should be located under /opt/eaasi, if I’m reading your EaaSI configuration correctly from the systemctl status output)

i.e. edit:

keycloak:
    image: jboss/keycloak: 15.0.2

to:

keycloak:
   image: quay.io/keycloak/keycloak: 15.0.2

That specific 15.0.2 container should still be available in that repo, so with luck it should be pulled and everything else will proceed as expected.

If issues continue to persist, we are in the process of examining dependency issues throughout the stack as part of a wider effort to craft a more maintainable release, so our ability to support deployments of these older versions and components of the codebase from ~2021 or earlier will be extremely limited. We hope to have much more recent/updated code available for test purposes soon, perhaps by the end of the year.

@nb_glur, by chance are you attending the iPres conference in Ghent next week? We will be hosting an EaaSI-related “Birds of a Feather” discussion session there and it would be lovely to connect on your experiments with EaaSI and the status of our program and the software moving forward if so

[nb_glur (Stephan Glur)]

Hi @ethan.gates ,

many thanks for your fast and helpful answer!
Indeed one can edit the docker-compose.yaml and point to another container.
image: quay.io/keycloak/keycloak:15.0.2 works.

But afterwards I still fail to get it running.
So I think I will have to wait for the next version of eaasi to become available, and then continue with my tests.
Or is there a way to work already with the new version which is development?

Unfortunaletly I will not be at iPres in Gent, but great to hear, that eaasi is being discussed there!

Best regards and many thanks,
Stephan

[ethan.gates]

Ah, I’m sorry, I was hopeful it would be that simple, but yes, if there are further dependency or deployment issues occurring we would ask you to wait for either a new public release and/or more up-to-date instructions on how best to test. Apologies, both the EaaSI program (whose grant-funded phase is closing) and the software itself are in a moment of transition, and we are working hard to ultimately make the software development both more maintainable and more transparent for outside contribution; there should be more details posted in the Program Announcements soon and I’ll be editing the Handbook and the Support Policy here in the Forum shortly to be more accurate about where we’re at.