Closed ipanova closed 1 week ago
it appears to be rpm only ( so far) issue. container seems to work properly
In [2]: Manifest.objects.first()
Out[2]: <Manifest: pk=0f00aa5a-f6a9-4ffe-a165-399b8fbb261d>
In [3]: m= Manifest.objects.first()
In [4]: m
Out[4]: <Manifest: pk=0f00aa5a-f6a9-4ffe-a165-399b8fbb261d>
In [5]: m.contentartifact_set
Out[5]: <django.db.models.fields.related_descriptors.create_reverse_many_to_one_manager.<locals>.RelatedManager at 0x7f2e9441bd00>
In [6]: m.contentartifact_set.all()
Out[6]: <QuerySet [<ContentArtifact: pk=16e513f6-a453-47ff-b735-528c5b7fc371>]>
In [7]: ca=m.contentartifact_set.all()[0]
In [8]: ca.remoteartifact_set
Out[8]: <django.db.models.fields.related_descriptors.create_reverse_many_to_one_manager.<locals>.RelatedManager at 0x7f2e9443be20>
In [9]: ca.remoteartifact_set.all()
Out[9]: <RemoteArtifactQuerySet [<RemoteArtifact: pk=f4c27061-4bd3-4c61-a614-9bd52719ceb7>, <RemoteArtifact: pk=e7162670-8d23-4e5d-a0c4-9f145193bdef>]>
maybe this has some impact RemoteArtifactSaver(fix_mismatched_remote_artifacts=True)
in the rpm pipeline
The usual suspect says the codepath is in pulpcore RemoteArtifactSaver(fix_mismatched_remote_artifacts=True) so moving accordingly
This has not bring any issues so far and there is no further evidence of this problem occurring anymore.
Version main and probably older