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.
Bug 1452149 - Docker repository not immediately available on local registry after sync
Summary: Docker repository not immediately available on local registry after sync
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management - Content
Version: 6.2.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-18 12:37 UTC by Roman Plevka
Modified: 2018-04-26 19:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-26 19:18:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19982 0 None None None 2017-06-12 11:49:18 UTC

Description Roman Plevka 2017-05-18 12:37:45 UTC
Description of problem:
After syncing a docker repository using hammer:
`hammer repository synchronize --id="666"`
the `repository info` subcommand reports sync status as success and reports 
'published at: sat6.server.com:5000/foo-bar-baz,

however, if you try to pull the repo using docker: `docker pull sat6.server.com:5000/foo-bar-baz`, you'll get:

Using default tag: latest
Trying to pull repository sat6.server.com:5000/foo-bar-baz ... 
unknown: Not Found

satellite takes some time before the repo is really available.
I believe, the sync task should finish AFTER the repo is really available.

Version-Release number of selected component (if applicable):
6.2.9

How reproducible:
always on pulling the repo just after syncing it.

Steps to Reproduce:
1. hammer repository create --product-id="1" --docker-upstream-name="busybox" --name="foo" --publish-via-http="true" --url="https://registry-1.docker.io" --content-type="docker"
2. hammer repository synchronize --id=1
3. (on a docker host with katello consumer ca installed): docker pull sat6-server.com:5000/foo-bar-baz

Actual results:
unknown: Not Found

Expected results:
repo available and pull finishes successfully

Additional info:
workaround: give satellite some time to publish the repo.

Comment 4 Tom McKay 2017-06-12 11:49:16 UTC
Created redmine issue http://projects.theforeman.org/issues/19982 from this bug

Comment 6 Tom McKay 2017-06-14 12:34:25 UTC
Work around: https://github.com/pulp/crane/blob/master/docs/index.rst#configuration Change the data_dir_polling_interval to a value less than 60 seconds.


Note You need to log in before you can comment on or make changes to this bug.