Bug #17434
closed
Removing puppet module causes content view to not show that unit within it
Added by Justin Sherrill about 8 years ago.
Updated about 3 years ago.
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.
- 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)
- 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
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.
- Target version changed from 140 to 147
- Assignee deleted (
Justin Sherrill)
- Translation missing: en.field_release set to 114
- Target version changed from 147 to 151
- Target version changed from 151 to 157
- Target version changed from 157 to 160
During backlog grooming I've confirmed that this is still an issue
- Status changed from New to Closed
Katello 4.0 has dropped pulp 2 and puppet content, so this issue is no longer relevant.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by