Description of problem: I was trying to check ostree info via hammer and found that content-count is missing: ~]# hammer -u admin -p changeme repository info --id 29 --organization-id 1 ID: 29 Name: Red Hat Enterprise Linux Atomic Host Trees Label: Red_Hat_Enterprise_Linux_Atomic_Host_Trees Organization: Default Organization Red Hat Repository: yes Content Type: ostree URL: https://cdn.redhat.com/content/dist/rhel/atomic/7/7Server/x86_64/ostree/repo Publish Via HTTP: no Published At: https://ibm-redhat.com/pulp/repos/Default_Organization/Library/content/dist/rhel/atomic/7/7Server/x86_64/ostree/repo Relative Path: Default_Organization/Library/content/dist/rhel/atomic/7/7Server/x86_64/ostree/repo Download Policy: Product: ID: 57 Name: Red Hat Enterprise Linux Atomic Host GPG Key: Sync: Status: Success Last Sync Date: about 22 hours Created: 2016/03/15 09:50:26 Updated: 2016/03/15 09:50:26 Content Counts: Version-Release number of selected component (if applicable): sat6.2 snap3 How reproducible: Steps to Reproduce: 1. create a ostree repo 2. sync the repo 3. check its info via hammer Actual results: ostree repository info shows "content counts" empty Expected results: should have branch count Additional info:
Verified with sat6.2 snap6. I can see ostree Branches under content-count. ~]# hammer -u admin -p changeme repository info --organization-id 1 --id 8 --product ostree ID: 8 Name: f23_ostree Label: f23_ostree Organization: Default Organization Red Hat Repository: no Content Type: ostree URL: https://dl.fedoraproject.org/pub/fedora/linux/atomic/23/ Publish Via HTTP: no Published At: https://cloud-qe-15.idmqe.lab.eng.bos.redhat.com/pulp/ostree/web/Default_Organization-ostree-f23_ostree Relative Path: Default_Organization/Library/custom/ostree/f23_ostree Product: ID: 7 Name: ostree GPG Key: Sync: Status: Success Last Sync Date: 21 minutes Created: 2016/03/31 08:13:53 Updated: 2016/03/31 08:13:55 Content Counts: OSTree Branches: 2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501