Chris, Could you provide a version of pulp you are using and also share your use case?
Thank you, Tanya On Mon, Feb 3, 2020 at 10:44 PM Chris Taylor (chtaylo2) <[email protected]> wrote: > We have a Pulp server which acts as a master content provider. > Subsequently we have global sites, running their own Pulp server which sync > directly from the master. I’m finding during the publishing, each of the > repodata/*XML* files have packages in random orders. > > For example: > Site 1: > $ curl > https://<server1>/repodata/8da5461a50987cce81ca57a4e699edc64815c45024416cb74bdd431fd4748a31-primary.xml.gz > | gunzip | grep '<name>' | head -n3 > <name>atomic-registries</name> > <name>ansible</name> > <name>cockpit-packagekit</name> > > Site 2: > $ curl > https://<server2>/repodata/79524dc840b7c913836ccc44d06ae0c5a3235abfde8d2af6a59bdc0f5a7e6c5b-primary.xml.gz > | gunzip | grep '<name>' | head -n3 > <name>docker-client</name> > <name>cockpit-machines</name> > <name>kubernetes-client</name> > > > If you do a SORT + md5sum on the above files, they match so the order on > the publishing is causing this. Is there any way to force > consistent/alphabetical ordering of packages in these files? > > Thanks! > /Chris > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
