Bug #17434: Removing puppet module causes content view to not show that unit within it - Katello - Foreman

Actions

Copy link

Bug #17434

closed

Removing puppet module causes content view to not show that unit within it

Added by Justin Sherrill over 7 years ago. Updated over 2 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Repositories

Target version:

Katello Backlog

Difficulty:

easy

Triaged:

Yes

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Deleting a content unit from a repository seems to delete the record from our database for that content unit even if it is published in A content view (in which case it would still be available in that CV).

We should just remove it from the repository instead.

Actions

Copy link

Updated by Justin Sherrill over 7 years ago

Subject changed from Removing rpm/puppet module/other type delete db record even if published in a CV to Removing rpm/puppet module causes content view to not show that unit within it

Actually we aren't removing it from the table, but instead it seems that the queries are incorrect when trying to search for it (and are relying on it being in Library)

Actions

Copy link

Updated by Justin Sherrill over 7 years ago

Subject changed from Removing rpm/puppet module causes content view to not show that unit within it to Removing puppet module causes content view to not show that unit within it

Actions

Copy link

Updated by Justin Sherrill over 7 years ago

Steps to reproduce

1. Create a puppet repo
2. UPload a puppet module
3. Publish a CV with that module
4. From the repo details page, remove that puppet module from the repo
5. Visit the content view version details page
6. View the puppet modules in the content view version details
7. Observe that the module is not there.

Actions

Copy link