Project

Profile

Help

Issue #574

closed

docker repo sync complains that repo does not exist

Added by ipanova@redhat.com about 9 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version - Docker:
master
Platform Release:
Target Release - Docker:
1.0.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Description of problem:

After docker repo creation, sync fails with the error that repo does not exist.

  1. pulp-admin docker repo create --repo-id synctest --feed=https://index.docker.io --upstream-name=busybox
    Repository [synctest] successfully created

[root@ec2-54-220-83-236 ~]# pulp-admin docker repo sync run --repo-id synctest
--------------------------------------------------------------------
Synchronizing Repository [synctest]
--------------------------------------------------------------------

This command may be exited via ctrl+c without affecting the request.

Task Failed

Missing resource(s): resource_id=synctest

[root@ec2-54-220-83-236 ~]# pulp-admin -u admin -p admin docker repo list
----------------------------------------------------------------------
Docker Repositories
--------------------------------------------------------------------

Id: myrepo
Display Name: myrepo
Description: None
Content Unit Counts:

Id: busybox
Display Name: busybox
Description: None
Content Unit Counts:

Id: synctest
Display Name: synctest
Description: None
Content Unit Counts:

[root@ec2-54-220-83-236 ~]# pulp-admin docker repo sync run --repo-id synctest
--------------------------------------------------------------------
Synchronizing Repository [synctest]
--------------------------------------------------------------------

This command may be exited via ctrl+c without affecting the request.

Task Failed

Missing resource(s): resource_id=synctest

Version-Release number of selected component (if applicable):
docker-0.2.1-0.2.beta
pulp-2.5.0-0.7.beta

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

+ This bug was cloned from Bugzilla Bug #1151029 +

Also available in: Atom PDF