After upgrade to 4.4.0 from 4.3.0 => Impossible to update former users

JayPe · 2025-10-21T14:06:21.682Z

When saving a user : [not_found] User could not be found (COMMAND-ugjs0upun6) When changing a user password : [failed_precondition] Password not found (COMMAND-G8dh3) I can't do any modification (save) on users that have been created before the upgrade. The weird thing is that I'm seeing them correctly.

A

Ask Inkeep•10/21/25, 2:06 PM

Hi @JayPe, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

A

Ask Inkeep•10/21/25, 2:06 PM

Answer

I wasn't able to find a direct answer, here are some relevant sources:

[Bug]:: Unable to Assign or Update Roles for User After Upgrade to ZITADEL 4.0.2 (1) : This closed GitHub issue describes similar problems with user modifications after upgrade, where users experienced issues assigning or updating roles for users after upgrading to ZITADEL v4.0.2.
```
User has not set a password
```
User has not set a password
```
User has not set a password
```
User has not set a password
error on change password API call
(2) : This discussion addresses password-related errors when changing user passwords, particularly noting issues that can occur when users are created in non-default organizations.

A

Ask Inkeep•10/21/25, 2:06 PM

To learn more, see the sources I considered:

[1] [Bug]:: Unable to Assign or Update Roles for User After Upgrade to ZITADEL 4.0.2
[2]

User has not set a password

User has not set a password

User has not set a password

User has not set a password error on change password API call

A

Ask Inkeep•10/21/25, 2:06 PM

Feel free to tag @Ask Inkeep with additional questions.

AAsk Inkeep To learn more, see the sources I considered: [[1] [Bug]:: Unable to Assign or...

A

Ask InkeepAPP•10/21/25, 2:08 PM

Got it. Tagging @Rajat for additional help.

J

JayPeOP•10/21/25, 2:08 PM

The issues you found are not relevant

J

JayPeOP•10/21/25, 2:17 PM

The only log I have :

time="2025-10-21T14:17:00Z" level=info msg=activity caller="/workspaces/zitadel/internal/activity/activity.go:105" domain="https://IDP_URL:443" grpcStatus=5 httpStatus=404 instance=325222083212607493 isSystemUser=false method=/zitadel.user.v2.UserService/UpdateHumanUser org=325222083212673029 path= requestMethod= trigger=resourceAPI user=325222083213262853

time="2025-10-21T14:17:00Z" level=info msg=activity caller="/workspaces/zitadel/internal/activity/activity.go:105" domain="https://IDP_URL:443" grpcStatus=5 httpStatus=404 instance=325222083212607493 isSystemUser=false method=/zitadel.user.v2.UserService/UpdateHumanUser org=325222083212673029 path= requestMethod= trigger=resourceAPI user=325222083213262853

time="2025-10-21T14:17:00Z" level=info msg=activity caller="/workspaces/zitadel/internal/activity/activity.go:105" domain="https://IDP_URL:443" grpcStatus=5 httpStatus=404 instance=325222083212607493 isSystemUser=false method=/zitadel.user.v2.UserService/UpdateHumanUser org=325222083212673029 path= requestMethod= trigger=resourceAPI user=325222083213262853

time="2025-10-21T14:17:00Z" level=info msg=activity caller="/workspaces/zitadel/internal/activity/activity.go:105" domain="https://IDP_URL:443" grpcStatus=5 httpStatus=404 instance=325222083212607493 isSystemUser=false method=/zitadel.user.v2.UserService/UpdateHumanUser org=325222083212673029 path= requestMethod= trigger=resourceAPI user=325222083213262853

J

JayPeOP•10/21/25, 2:47 PM

I tried to restore a database backup of the version 4.3.0, and launching the version 4.3.0 :
Error with the migrations :
Message=unable to update state Parent=(ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification (SQLSTATE 42P10))" name=repeatable_fill_fields_for_instance_domains

J

JayPeOP•10/21/25, 2:52 PM

Well with a former backup it works ... the version 4.3.0 and the version 4.4.0 ... really weird

R

Rajat•10/21/25, 3:00 PM

hey @JayPe glad you figured out, upgrades are sometimes flaky, I will recommend you to pls open a bug.
BUT when I see your logs, your domain name is

domain="https://IDP_URL:443"

domain="https://IDP_URL:443"

domain="https://IDP_URL:443"

domain="https://IDP_URL:443" and as a result you seem to be getting

grpcStatus=5 httpStatus=404

grpcStatus=5 httpStatus=404

grpcStatus=5 httpStatus=404

grpcStatus=5 httpStatus=404 did I miss something or

IDP_URL

IDP_URL

IDP_URL

IDP_URL is a variable that gets populated ?.

RRajat hey @JayPe glad you figured out, upgrades are sometimes flaky, I will recommend ...

J

JayPeOP•10/21/25, 3:01 PM

I've replaced with IDP_URL to avoid displaying it

R

Rajat•10/21/25, 3:16 PM

ah cool

I saw both in same line so I drew an obvious conclusion ahahah!.
Because the error is flaky and not always, maybe opening an issue would be the best way.