debian migration fails with: PackageReleaseComponent matching query does not exist
This is debian migration related:
"traceback": " File \"/usr/lib/python3.6/site-packages/rq/worker.py\", line 936, in perform_job rv = job.perform() File \"/usr/lib/python3.6/site-packages/rq/job.py\", line 684, in perform self._result = self._execute() File \"/usr/lib/python3.6/site-packages/rq/job.py\", line 690, in _execute return self.func(*self.args, **self.kwargs) File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/tasks/migrate.py\", line 81, in migrate_from_pulp2 migrate_content(plan, skip_corrupted=skip_corrupted) File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/migration.py\", line 47, in migrate_content plugin.migrator.migrate_content_to_pulp3(skip_corrupted=skip_corrupted) File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/plugin/deb/migrator.py\", line 85, in migrate_content_to_pulp3 loop.run_until_complete(dm.create()) File \"/usr/lib64/python3.6/asyncio/base_events.py\", line 484, in run_until_complete return future.result() File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/plugin/content.py\", line 89, in create await pipeline File \"/usr/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py\", line 225, in create_pipeline await asyncio.gather(*futures) File \"/usr/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py\", line 43, in __call__ await self.run() File \"/usr/lib/python3.6/site-packages/pulpcore/plugin/stages/content_stages.py\", line 105, in run d_content.content.q() File \"/usr/lib/python3.6/site-packages/django/db/models/manager.py\", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File \"/usr/lib/python3.6/site-packages/django/db/models/query.py\", line 408, in get self.model._meta.object_name
PackageReleaseComponent matching query does not exist.
katello user filed it here: https://projects.theforeman.org/issues/32284
This feature (pulp_deb 2to3 migration within Katello) really is not ready to be used (entirely untested and also missing DB columns on the Katello side).
That being said, my thoughts on the bug:
- First of all the error message does not make any sense to me, since I do not believe the migration itself ever "queries" for existing "PackageReleaseComponent" units. Is this a re-migration scenario?
Things I just don't know enough about yet (but are possible error sources):
- What do Katello migration plans look like? (So far I have only tested pulp_deb 2to3 with "simple" migration plans).
- Katello (in Pulp 2 world) did a lot of copying of Pulp repositories. I am not sure of the top of my head what exactly pulp_deb metadata units in such copied repos look like, and how that might interact with the pulp_deb 2to3 migration.
#4 Updated by email@example.com 23 days ago
Some highlights from the irc conversation - in case some pulp_debian packages were corrupted or artifact missing, it will be skipped. PackageReleaseComponent creation relies on the package being already saved by that time https://github.com/pulp/pulp-2to3-migration/blob/master/pulp_2to3_migration/app/plugin/deb/pulp_2to3_models.py#L454
This could become a fix for what might be the underlying problem: https://github.com/pulp/pulp-2to3-migration/pull/353
#7 Updated by firstname.lastname@example.org 20 days ago
I don't really understand this traceback: At some point during the pipeline run, during the
ContentSaverstage, while looping over
d_content.d_artifactsdjango complains that a
matching query does not existfor the artifactless type
I think you should look at pulpcore 3.7 branch https://github.com/pulp/pulpcore/blob/3.7/pulpcore/plugin/stages/content_stages.py#L105
Please register to edit this issue