[BUG] - Duplicate key validation error on conda-store-server

[viniciusdc]

Describe the bug

I tested the latest release as part of Nebari's integration (upcoming) release and found the following error message from the conda-store-server pod:

INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade bf065abf375b -> 89637f546129, remove conda package build channel
Traceback (most recent call last):
  File "/opt/conda/envs/conda-store-server/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1964, in _exec_single_context
    self.dialect.do_execute(
  File "/opt/conda/envs/conda-store-server/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 942, in do_execute
    cursor.execute(statement, parameters)
psycopg2.errors.UniqueViolation: could not create unique index "_conda_package_build_uc"
DETAIL:  Key (package_id, subdir, build, build_number, sha256)=(182273, linux-64, h924138e_3, 3, 76c7405bcf2af639971150f342550484efac18219c0203c5ee2e38b8956fe2a0) is duplicated.

full log attached

dev-nebari-conda-store-server-59448568dd-7mbn9-1738275853668991320.log

Since I was not entirely sure if this was my own workspace (nebari's fault), I shifted to this repo's docker-compose to reach the same workspace I had on k8s. To my surprise, as soon as the service went online,e it crashed with a similar error message, as seen in the screenshot bellow:

Curiously, the issue went away, and the service started its usual self-checks, though the same can't be said for its Kubernetes counterpart since it enters a CrashLoopBack state.

Expected behavior

At least on Nebari's side, it will be usual running pods

How to Reproduce the problem?

• From a local nebari (Kubernetes):

  • Deploy a local nebari from pip install nebari with nebari init local -p mytest and subsequently nebari deploy -c nebari-config.yaml;
  • Then, after deployment completes, upgrade it to pip install git+https://github.com/nebari-dev/nebari.git@upgrade-conda-store and run the deploy command once again -- check with k9s for pod status

• From docker-compose:

  • Run docker-compose from main

Output

No response

Versions and dependencies used.

conda-store==2025.1.1

Anything else?

No response

[viniciusdc]

observation: I did update the DB by replacing the metadata_ value from {} to null for a few namespaces (namely admin, analyst, developer, global, nebari-git ) before upgrading to the RC test of nebari (k8s only), since I was using that as a way to test the recent fixes