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
Migrations won't work if the storage backend is Azure or S3 #2843
Comments
It looks like there are also issues with https://github.com/pulp/pulp_rpm/blob/main/pulp_rpm/app/migrations/0003_DATA_incorrect_json.py Which ought to be fixed at the same time |
Alternatively, we could just say "these backends aren't supported until version X" if it's difficult |
dralley
changed the title
Migration 0044 won't work if the storage backend is Azure or S3
Migrations won't work if the storage backend is Azure or S3
Nov 1, 2022
pavelpicka
added a commit
to pavelpicka/pulp_rpm
that referenced
this issue
Nov 3, 2022
avoid using ``os.path...`` for support all storage backedns closes: pulp#2843
pavelpicka
added a commit
to pavelpicka/pulp_rpm
that referenced
this issue
Nov 3, 2022
avoid using ``os.path...`` for support all storage backedns closes: pulp#2843
dralley
pushed a commit
that referenced
this issue
Nov 3, 2022
avoid using ``os.path...`` for support all storage backedns closes: #2843
@markgoddard I'm doing a release now (3.18.8) with the fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.18
Describe the bug
This line uses the
os
module, which will fail when the storage backend in use is not the local filesystem.https://github.com/pulp/pulp_rpm/blob/main/pulp_rpm/app/migrations/0044_noartifact_modules.py#L18
Our tests are passing only because there is no data in the system prior to the migration: #2829
The text was updated successfully, but these errors were encountered: