Actions
Bug #32601
closedrepo package upload & package remove doesn't trigger applicability regen for hosts
Description
it should
Actions
Added by Justin Sherrill almost 5 years ago. Updated over 4 years ago.
Description
it should
For example, repo applicability is run after a sync: https://github.com/Katello/katello/blob/master/app/lib/actions/katello/repository/sync.rb#L71
We should do the same thing after uploading content (https://github.com/Katello/katello/blob/master/app/lib/actions/katello/repository/upload_files.rb) and removing content (https://github.com/Katello/katello/blob/master/app/lib/actions/katello/repository/remove_content.rb)
To test:
1) Register a content host to your system (like the katello-client box in forklift)
2) Sync https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/
3) Install walrus-0.71 on your content host
4) Ensure that you see walrus-5.21 as applicable on the content host's page
5) Delete the walrus-5.21 rpm
6) Regenerate applicability by clicking "Recalculate" on the content host's "Errata" tab
-> This is part of the bug, it should be automatic with content deletion
7) Ensure that walrus-5.21 is no longer applicable
8) Download it from here: https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/walrus-5.21-1.noarch.rpm
9) Upload the downloaded RPM to your synced repo
10) See that walrus-5.21 won't be applicable until you click "Regenerate" again. This is the second part of the bug.
Applied in changeset katello|b2324123bb54562a4f21c88996eec8146a83346b.