Bug 1198847
| Summary: | Docker Tags page shows all tags across all organizations | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | David Davis <daviddavis> |
| Component: | API | Assignee: | David Davis <daviddavis> |
| Status: | CLOSED ERRATA | QA Contact: | Stephen Benjamin <stbenjam> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | bbuckingham, bkearney, cwelton, daviddavis, stbenjam |
| Target Milestone: | Unspecified | Keywords: | ReleaseNotes, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/14056 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-27 08:49:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1190823 | ||
|
Description
David Davis
2015-03-04 22:48:56 UTC
Is this a valid release note? If so, please provide some suitable doc text. The issue seems plain enough but is there any workaround? Is a workaround required? thanks Yes, it is valid. Some doc text: "The Docker tags page shows tags across all organizations and locations." Is that good? There is no workaround at this time. Created redmine issue http://projects.theforeman.org/issues/14056 from this bug Moving to POST since upstream bug http://projects.theforeman.org/issues/14056 has been closed ------------- David Davis Applied in changeset commit:katello|cb3ab3a5a8be19ad05f1d8d284b57750a7d85a29. Verified. 1. Synced busybox repository to Default Organization 2. Docker tags page shows the tags 3. Visited another org - no tags shown Reset docs contact <> daobrien 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:1500 |