Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1308449 [details]
traceback

Description of problem:

Can't sync ostree repo   Red Hat Enterprise Linux Atomic Host Trees 

Version-Release number of selected component (if applicable):
6.3.0 snap 9

How reproducible:

easy

Steps to Reproduce:
1.Upload manifest
2.Enable Red Hat Enterprise Linux Atomic Host Trees
3.Sync repo

Actual results:
Task fails

Expected results:
Sync succeeds

Additional info:
tracebacks attached

So I have been unable to reproduce this specific issue. I tried it on the same box as the reporter and had to the refresh manifest. The sync worked seamlessly from there on. Moving this ot ON_QA. Kindly fail it if you hit the same issue as reported.

Tested on Sat6.3 snap 18. As neither me or Partha have been able to reproduce this, I am closing this as WORKSFORME (which should have happened even before setting this to ON_QA).

John, if you still think the problem exists, please, let us know.