Hide Forgot
Steps to Reproduce: 1. Create a product 2. Create a repository w/ feed URL 3. Sync the repository 4. Click 'Manage Packages' on the repository details 5. Select all packages listed 6. Click 'Remove Packages' 7. Wait until removal is done 8. Go back to repository details page; note the package count is zero and browsing to HTTP link shows no packages 9. Click 'Sync Repository' 10. Wait till sync is complete Actual results: The repository shows 0 packages and browsing to the repository HTTP link in the browser shows no pages. Expected results: Repository should have updated package counts and the http repository should show packages in it. Additional info:
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Moving 6.2 bugs out to sat-backlog.
Moving to POST as fix is available upstream.
available in pulp 2.8.5 or later.
Build : Satellite 6.3 snap 6 Verification steps: 1. Created a product , with custom repository 2. Synced the repository , 32 packages 3. Deleted the packages from the repository 4. Package count 0 , no packages in manage packages page , 5. Re-synced the repo , re-visited the repository details page, package count-32 6. Visited manage packages page , all 32 packages visible Moving it to verified.
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/RHSA-2018:0336