Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Keycloak 26.2.0 released

345 views
Skip to first unread message

Stian Thorgersen

unread,
Apr 11, 2025, 9:25:04 AMApr 11
to

Arif EROL

unread,
Apr 18, 2025, 4:20:08 PMApr 18
to Keycloak User

Hi Stian Thorgersen,

I tried to upgrade from version 26.1.4 to 26.0.2 in my test environment. However, when I attempted to start my container, I encountered the following error:

"ERROR: A provider JAR was updated since the last build, please rebuild for this to be fully utilized."

Do you have any idea what might be causing this issue?

Thank you in advance for your support.

Best regards,
Arif EROL


11 Nisan 2025 Cuma tarihinde saat 16:25:04 UTC+3 itibarıyla Stian Thorgersen şunları yazdı:

Björn Pedersen

unread,
Apr 22, 2025, 4:03:30 AMApr 22
to Keycloak User
Arif EROL schrieb am Freitag, 18. April 2025 um 22:20:08 UTC+2:

Hi Stian Thorgersen,

I tried to upgrade from version 26.1.4 to 26.0.2 in my test environment. However, when I attempted to start my container, I encountered the following error:

"ERROR: A provider JAR was updated since the last build, please rebuild for this to be fully utilized."

Do you have any idea what might be causing this issue?

Thank you in advance for your support.



I did also observe this, the workaround was to start it without the `--optimized` flag.  

There are quite few changes to available features and flags , but i could not yet  identify which setting is changed between the stored version and the runtime setting.

Björn

Václav Muzikář

unread,
Apr 23, 2025, 9:57:33 AMApr 23
to Björn Pedersen, arif....@gmail.com, Keycloak User
Hi,
there's a new validation in 26.2 for detecting changes in providers. In order to properly reflect changes in providers, the build command needs to be run. It is run implicitly when the --optimized flag is not used, otherwise it needs to be executed explicitly. That's always been the case, we just now validate it to prevent unexpected behaviour and it is clear to the user what is happening.

I suspect this might be the case that some provider was changed after the build command was executed. If not, I would like to ask you to create a GH Issue with steps to reproduce.

Thanks.

Vašek

--
You received this message because you are subscribed to the Google Groups "Keycloak User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to keycloak-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/keycloak-user/eddd8aa6-c978-44d4-a4f4-e4c37936c724n%40googlegroups.com.


--

Václav Muzikář

Principal Software Engineer, Keycloak

Red Hat

Björn Pedersen

unread,
Apr 25, 2025, 3:52:55 AMApr 25
to Keycloak User
Václav Muzikář schrieb am Mittwoch, 23. April 2025 um 15:57:33 UTC+2:
Hi,
there's a new validation in 26.2 for detecting changes in providers. In order to properly reflect changes in providers, the build command needs to be run. It is run implicitly when the --optimized flag is not used, otherwise it needs to be executed explicitly. That's always been the case, we just now validate it to prevent unexpected behaviour and it is clear to the user what is happening.

I suspect this might be the case that some provider was changed after the build command was executed. If not, I would like to ask you to create a GH Issue with steps to reproduce.

Thanks.



It looks like https://github.com/keycloak/keycloak/issues/38893 is the same thing. I am also using a multistage build here, with a custom theme provider. I guess the logic for detecting changed providers needs not only look at time stamps etc., but probablyy needs at least a hash of the files to decide if  something changed.

Václav Muzikář

unread,
Apr 28, 2025, 4:22:01 AMApr 28
to Björn Pedersen, arif....@gmail.com, Keycloak User

Václav Muzikář

unread,
Apr 29, 2025, 2:44:54 AMApr 29
to Arif EROL, Keycloak User
Have you run the touch command to update the timestamps?

On Mon, Apr 28, 2025 at 11:31 PM Arif EROL <arif....@gmail.com> wrote:
  No. In the issue you mentioned, a build is triggered again in the last line: "RUN /opt/keycloak/bin/kc.sh build". I tried that, but it didn’t solve the problem.  

Václav Muzikář <vmuz...@redhat.com>, 28 Nis 2025 Pzt, 11:21 tarihinde şunu yazdı:

Václav Muzikář

unread,
Apr 30, 2025, 3:06:13 AMApr 30
to Arif EROL, Keycloak User
In that case, could you please open a GitHub Issue with steps to reproduce, incl. details about your environment like Docker version etc.?

On Tue, Apr 29, 2025 at 10:36 PM Arif EROL <arif....@gmail.com> wrote:

Dear Václav Muzikář

Yes, I have executed the following commands as suggested:

RUN touch -m --date=@1743465600 /opt/keycloak/*
RUN /opt/keycloak/bin/kc.sh build

However, the issue still persists after running them. Please let me know if there are any additional steps I should take or if you need further information to help troubleshoot the problem.

Best regards,


Václav Muzikář <vmuz...@redhat.com>, 29 Nis 2025 Sal, 09:44 tarihinde şunu yazdı:
Reply all
Reply to author
Forward
0 new messages