Hi, the details view of the repo is a good place to start. Just to clarify, the copy action does not act on the filsystem. It is only a database update, if it completes successfully then the items were copied. Where you can get into trouble is that the target repository will not be republished automatically after a copy. You need to manually run the publish command before the results of the copy will be visible on the filesystem.
-Barnaby ----- Original Message ----- From: "Sandro Roth" <[email protected]> To: "Vijayabalan Balakrishnan" <[email protected]>, [email protected] Sent: Thursday, February 19, 2015 2:43:47 AM Subject: Re: [Pulp-list] While cloning from parent repo - how to verify and ensure the new repo contents are exact copy of parent repo Hi there You could compare the unit counts. $ pulp-admin rpm repo list –details …. Content Unit Counts: Erratum: 171 Package Category: 9 Package Environment: 6 Package Group: 70 Rpm: 5254 Yum Repo Metadata File: 1 …. But I think if the copy task finishes successfully you can be sure everything got copied. Files don’t actually get copied, pulp is just symlinking and publishing again. Have a look at the tasks. $ pulp-admin tasks list Cheers Sandro From: [email protected] [mailto:[email protected]] On Behalf Of Vijayabalan Balakrishnan Sent: Mittwoch, 18. Februar 2015 20:19 To: [email protected] Subject: [Pulp-list] While cloning from parent repo - how to verify and ensure the new repo contents are exact copy of parent repo Creating the snapshot from parent repository Parent Repo Name - rhel7-parent I have created rhel7-parent and synced with rhn redhat through sync commands. Snapshot Name - rhel7-snapshot Create Empty repo First without any parent feed # pulp-admin rpm repo create --repo-id=rhel7-snapshot Copy all content(or) clone from master to clone (No parent Feed / Snapshot ) # pulp-admin rpm repo copy rpm --from-repo-id=rhel7-parent --to-repo-id=rhel7-snapshot The above command will create snapshot (at that point of time) from rhel7-parent repository without any feed association.So the following sync command wont work. # pulp-admin rpm repo sync run --repo-id 1Q2015-dev-rhel6 Now my question is how can we be sure when we create the clone, ALL files were copied ? When I created the repos with feed I had to sync several times before it ends successfully, I believe it is a bug, but at least we can verify that the new repo is an exact copy of the parent repo. Also while creating the snapshot (without feed option),how can we ensure all the rpm's were copied in the new snapshot repo ? Any thoughts ? Thanks, BVIJAY This email message and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify us immediately and destroy the original transmittal. You are hereby notified that any review, copying or distribution of it is strictly prohibited. Thank you for your cooperation. Header information contained in E-mails to and from the company are monitored for operational reasons in accordance with the Swiss data protection act. _______________________________________________ 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
