-
Notifications
You must be signed in to change notification settings - Fork 55
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
DB Migration fails with ERROR: relation "core_artifact" does not exist at character 28 #641
Comments
Hi @jeremyatourville This is surprising. We tried reproducing it, albiet with the latest images, and it worked. Our usual advise would be to drop the database and try again, although it looks like you did create the fresh database directory. |
@mikedep333 When you say drop the database - is there a specific command to run? I am getting a message that you can't drop the currently open DB. Or are you saying delete everything under the pgsql folder? Alternatively, what image versions were you able to make work? My understanding is that the container image tag |
I also have the problem with |
@mikedep333 @wahello can you post your docker compose file, the result of docker-compose up -d and the log from when you are starting up the containers? (similar to what I posted above) |
I did try making some changes to my docker-compose.yml file. I changed the container tags being used. I now have the following:
This made no change. I still get the same error as my original post. |
It resolved by making a Maybe, It's about absence of writing permission.
|
Hmmmm... that's intersting behavior. I would not have expected that but it totally makes sense. In the example I posted, my docker-compose file is using bind mount in Linux. However, when I tried the same compose setup on Windows with docker desktop I chose to use native docker volumes and I still was getting that behavior. So I would have never guessed that. I'm glad to hear it's working for you. I'm going to give it a shot on my Linux machine and see what happens. |
So I noticed today that my docker log shows this info: I didn't see that in my earlier log. |
Version
docker.io/library/postgres:13
docker.io/library/redis:latest
pulp/pulp-minimal:latest
pulp/pulp-web:latest
Describe the bug
service "migration_service" didn't completed successfully: exit 139
is seen when running docker-compose up -ddocker logs show this line -
ERROR: relation "core_artifact" does not exist at character 28
To Reproduce
Use compose.folders.yaml from git
mkdir ./pgsql ./pulp_storage
sudo chown 700:700 ./pulp_storage
sudo chown 26:26 ./pgsql
Expected behavior
DB Migration should complete without issues
Additional context
I am running Rocky 8.9 and Docker/Docker-Compose My system is air-gapped and I am pulling images from my private repo.
Folder structure:
The text was updated successfully, but these errors were encountered: