Version
pulpcore==3.107.1
pulp-rpm==3.35.2
pulp-container=2.27.6
Describe the bug
I have 1000+ RPM repositories. In first run, only 700+ RPM repositories are synchronised successfully. In second run some repos synced successfully and final only in 3rd the last 25 repositories are synced successfully. In the 3rd execution all replication sync tasks are completed successfully and the distribution objects updated the versions for the 25 repositories only. The distributions object which completed successfully in the first/second run are not pointing to any repository versions or repository or publication. The subsequent replication tasks get completed with no change found in upstream pulp server.
To Reproduce
In the replica server create a distribution artifact which has the same base-path in matching with any of the repository the upstream-pulp server. The upstream-pulp replication task will fail in the first run due to the base-path conflict. Before the second run, destroy the distribution which we were created locally in the replica server. And then run upstream-pulp replication for second time.
Expected behavior
Pulp replication should have the track records of successfully synced repositories and which are due for update of pulp upstream object.
Version
pulpcore==3.107.1
pulp-rpm==3.35.2
pulp-container=2.27.6
Describe the bug
I have 1000+ RPM repositories. In first run, only 700+ RPM repositories are synchronised successfully. In second run some repos synced successfully and final only in 3rd the last 25 repositories are synced successfully. In the 3rd execution all replication sync tasks are completed successfully and the distribution objects updated the versions for the 25 repositories only. The distributions object which completed successfully in the first/second run are not pointing to any repository versions or repository or publication. The subsequent replication tasks get completed with no change found in upstream pulp server.
To Reproduce
In the replica server create a distribution artifact which has the same base-path in matching with any of the repository the upstream-pulp server. The upstream-pulp replication task will fail in the first run due to the base-path conflict. Before the second run, destroy the distribution which we were created locally in the replica server. And then run upstream-pulp replication for second time.
Expected behavior
Pulp replication should have the track records of successfully synced repositories and which are due for update of pulp upstream object.