Bug 1311734 - unable to remove a repository from a content view
Summary: unable to remove a repository from a content view
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 20:56 UTC by Tom McKay
Modified: 2019-09-26 18:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 17:45:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Satellite 6.2: After clicking 'Remove Repositories' (80.61 KB, image/png)
2016-08-25 17:45 UTC, Brad Buckingham
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13891 0 None None None 2016-04-22 16:45:59 UTC

Description Tom McKay 2016-02-24 20:56:30 UTC
To reproduce in UI...

Enable repo "Red Hat Subscription Asset Manager for RHEL 6 Server RPMs x86_64 6Server"
Sync
Add repo to CV
Publish CV
Select repo and click "Remove Repositories"
Results: No error, repo still listed as belonging to CV

Comment 1 Tom McKay 2016-02-24 20:56:32 UTC
Created from redmine issue http://projects.theforeman.org/issues/13891

Comment 3 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 4 Bryan Kearney 2016-07-26 15:35:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 Brad Buckingham 2016-08-25 17:44:49 UTC
On Satellite 6.2, I am no longer seeing the behavior described.  Attached is a screenshot after clicking the 'Remove Repositories'.  Please feel free to re-open if the issue re-occurs.

Comment 7 Brad Buckingham 2016-08-25 17:45:22 UTC
Created attachment 1194071 [details]
Satellite 6.2: After clicking 'Remove Repositories'


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