Sync for BaseOS for AlmaLinux or CentOS 8 Stream fails with 'DistributionTree' object has no attribute 'filename'
Offending line is this one https://github.com/pulp/pulpcore/blob/master/pulpcore/plugin/stages/artifact_stages.py#L355 and was introduced with this commit https://github.com/pulp/pulpcore/commit/349f2137d970f87190749b417cfa137dc0f99ff5#diff-28560cb4dba596314e3577becbd1974a015d47c08f8f17b38e6030a701999169 which landed in 3.15.0 and backported to 3.14.z
We cannot reference
filename on the content https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/content.py#L467
#3 Updated by firstname.lastname@example.org about 1 month ago
#7 Updated by ggainey about 1 month ago
This is def a bug, and I am prepping a PR for it. However, I cannot reproduce the problem on core/master. Using the following remotes:
http://mirror.phx1.us.spryservers.net/almalinux/8.4/BaseOS/aarch64/kickstart/ https://mirror.slu.cz/rocky/8.4/BaseOS/aarch64/kickstart/ http://mirror.phx1.us.spryservers.net/almalinux/8.4/BaseOS/aarch64/os/ https://mirror.slu.cz/rocky/8.4/BaseOS/aarch64/os/ http://mirror.centos.org/centos/8-stream/BaseOS/aarch64/os/
I have sync'd on_demand, immediate (for ks-repos), autopublish, and mirror. Duplicate-file-paths I get - but not the failure noted in the foreman-issue in #c3. core/master is 3.16dev, and there have been a number of fixes addressing remote-artifacts since 3.14. It's possible we just never hit this path any more. It's also possible that the repos were in a suboptimal state which has been fixed - CentOS8-Stream, for example, was updated yesterday.
In any event - the traceback is a bug, PR to address it incoming.
Please register to edit this issue