Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicated client creation upon running setup to upgrade image versions #1133

Closed
moabu opened this issue Mar 30, 2022 · 0 comments · Fixed by #1134
Closed

Duplicated client creation upon running setup to upgrade image versions #1133

moabu opened this issue Mar 30, 2022 · 0 comments · Fixed by #1134
Assignees
Labels

Comments

@moabu
Copy link
Member

moabu commented Mar 30, 2022

Describe the bug
Upon upgrading the image versions or reapplying the setup in CN the persistence and configurator jobs are run. Because some entries were missing in the DB the persistence job activated the upgrade process. However, that lead to duplicate clients created which is an undesired effect.

To Reproduce
Steps to reproduce the behavior:

  1. Install using microk8s using an older image version such as v1.0.0-beta.15 with mysql as the backend
  2. Upgrade using helm upgrade to the latest with the _dev images
  3. Issue is observed

It can be reproduced with the following behavior as well.

  1. deploy cluster for the first time
  2. wipe configs and secrets
  3. re-deploy cluster (configurator will upload mounted config.json and secret.json that created during step 1)
  4. duplicate of Jans Role Based Client, admin-ui-client, and Jans Admin UI Client are created because the IDs are created during running persistence-loader (if not exist in config layer)

Expected behavior
No duplicated entries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants