Actions
Issue #1831
closedsync of non-existing repo does not report an error
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Docker:
2.0.0
Platform Release:
2.8.5
Target Release - Docker:
2.0.2
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 1
Quarter:
Description
You can sync a repository that doesn't exist, and pulp will not report any errors.
$ pulp-admin docker repo create --repo-id=m --feed=https://registry-1.docker.io --upstream-name=sdjhflkjdshf
$ pulp-admin docker repo sync run --repo-id=m
+----------------------------------------------------------------------+
Synchronizing Repository [m]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Downloading manifests
[-]
... completed
Copying units already in pulp
[-]
... completed
Copying units already in pulp
[-]
... completed
Downloading remote files
[-]
... completed
Saving Manifests and Blobs
[-]
... completed
Saving Tags
[-]
... completed
Task Succeeded
Task Succeeded
Files
Updated by mhrivnak about 8 years ago
- File sync_status.txt sync_status.txt added
Updated by mhrivnak about 8 years ago
- Priority changed from Normal to High
- Platform Release set to 2.8.3
- Target Release - Docker set to 2.0.1
- Triaged changed from No to Yes
Updated by mhrivnak about 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to mhrivnak
Updated by mhrivnak about 8 years ago
- Status changed from ASSIGNED to POST
Updated by semyers about 8 years ago
- Platform Release changed from 2.8.3 to 2.8.4
Updated by semyers almost 8 years ago
- Target Release - Docker changed from 2.0.1 to 2.0.2
Added by mhrivnak almost 8 years ago
Added by mhrivnak almost 8 years ago
Revision 24267861 | View on GitHub
When a sync cannot get tags from a v2 API, it will fail with a reasonable message.
https://pulp.plan.io/issues/1831
fixes #1831
Added by mhrivnak almost 8 years ago
Revision 24267861 | View on GitHub
When a sync cannot get tags from a v2 API, it will fail with a reasonable message.
https://pulp.plan.io/issues/1831
fixes #1831
Added by mhrivnak almost 8 years ago
Revision 24267861 | View on GitHub
When a sync cannot get tags from a v2 API, it will fail with a reasonable message.
https://pulp.plan.io/issues/1831
fixes #1831
Updated by mhrivnak almost 8 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 24267861451df0c34f813569d83216b4ee93daba.
Updated by semyers almost 8 years ago
- Platform Release changed from 2.8.4 to 2.8.5
Updated by semyers almost 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
When a sync cannot get tags from a v2 API, it will fail with a reasonable message.
https://pulp.plan.io/issues/1831
fixes #1831