[BUG] - Upgrading nebari to 2025.2.1rc1
leads to broken conda-store due to remaints of Docker builds
#2951
Labels
needs: triage 🚦
Someone needs to have a look at this issue and triage
type: bug 🐛
Something isn't working
Describe the bug
Another issue, in the latest conda-store migration, in
[2025.1.1](https://github.com/conda-incubator/conda-store/releases/tag/2025.1.1)
the DOCKER_BLOB column schema for the docker builds was removed, I initially assumed alambic would take care of any post DB update, but was wrong.In case any entries are present in the DB, the whole conda-store server breaks as seen below:
Fortunately removing all affected builds in the DB through the API solves the issue, I am planning on encapsulating this as an automated step in the upgrade command that will perform the following:
Expected behavior
fully functional conda-store server execution
OS and architecture in which you are running Nebari
Linux
How to Reproduce the problem?
Using any nebari deployment prior to
2025.2.1rc1
build a conda-store environment that requires a docker registry, then update nebari to its RCCommand output
Versions and dependencies used.
No response
Compute environment
GCP
Integrations
conda-store
Anything else?
No response
The text was updated successfully, but these errors were encountered: