Bug 2128080

This is the last way I found out to get Similar Results as what is displayed in Content --> Sync Status page


# curl -ksu admin:RedHat1! "https://`hostname -f`/foreman_tasks/api/tasks?search=label=Actions::Katello::Repository::Sync&&per_page=1000" | json_reformat | egrep "^                            \"text\": \"repository|                \"output\":"  | awk -F'":' '{print $NF"|"}' | paste - - | column -s"|" -t

 "repository 'Red Hat Enterprise Linux 7 Server - Extras RPMs x86_64'"                        	 "New packages: 26 (41.1 MB)."   
 "repository 'Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64'"  	 "No new packages."   
 "repository 'Red Hat Satellite Tools 6.10 for RHEL 6 Server - ELS RPMs x86_64'"              	 "No new packages."   
 "repository 'Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64'"  	 "No new packages."   
 "repository 'Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64'"  	 "No new packages."   
 "repository 'Red Hat Enterprise Linux 6 Server - Extended Life Cycle Support RPMs x86_64'"   	 "No new packages."   
 "repository 'Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64'"  	 "No new packages."   
 "repository 'Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server'"                         	 "No new packages."   
 "repository 'ubi8/ubi-minimal'"                                                              	 "No JSON object could be decoded"   
 "repository 'ubi8/ubi-minimal'"                                                              	 "No JSON object could be decoded"   
 "repository 'ubi8/ubi-minimal'"                                                              	 "No JSON object could be decoded"   
 "repository 'Red Hat Enterprise Linux 6 Server - Extended Life Cycle Support RPMs x86_64'"   	 "Processing metadata"   


Basically, I target all the "Actions::Katello::Repository::Sync" tasks , get their results and then grep for the repo name and results printed for each. But I limit the output to 1000 only. 

The output after "json_reformat" can be parsed much better with Python script instead of shell hacks.

The above output is for Pulp 2, For Pulp 3, We do have results but It's a bit messy due to the way 

 "repository 'Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64 7Server'",  	 "Added Rpms: 30, Errata: 1\nTotal steps: 16234/16234\n--------------------------------\nAssociating Content: 598/598\nDownloading Artifacts: 0/0\nDownloading Metadata Files: 10/10\nParsed Advisories: 690/690\nParsed Comps: 0/0\nParsed Packages: 14369/14369\nSkipping Packages: 0/0\nUn-Associating Content: 567/567",

 "repository 'Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64'",            	 "No content added.\nTotal steps: 1/1\n--------------------------------\nSkipping Sync (no change from previous sync): 1/1",


If we use jq utility instead of json_reformat, we can get this for Pulp3 specific satellites

curl -ksu admin:RedHat1! "https://`hostname -f`/foreman_tasks/api/tasks?search=label=Actions::Katello::Repository::Sync&&per_page=1000" | jq '.results | .[] | [.input.repository.name,.humanized.output]'


[
  "Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64 7Server",
  "Added Rpms: 30, Errata: 1\nTotal steps: 16234/16234\n--------------------------------\nAssociating Content: 598/598\nDownloading Artifacts: 0/0\nDownloading Metadata Files: 10/10\nParsed Advisories: 690/690\nParsed Comps: 0/0\nParsed Packages: 14369/14369\nSkipping Packages: 0/0\nUn-Associating Content: 567/567"
]
[
  "Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64",
  "No content added.\nTotal steps: 1/1\n--------------------------------\nSkipping Sync (no change from previous sync): 1/1"
]

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days