Bug 1732963 - RHEL 8 Modularity: Remove module 'enable' and 'disable' from UI/hammer/CLI
Summary: RHEL 8 Modularity: Remove module 'enable' and 'disable' from UI/hammer/CLI
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Repositories
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: vijsingh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-24 20:55 UTC by Mike McCune
Modified: 2020-02-21 04:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Mike McCune 2019-07-24 20:55:46 UTC
Enabling and disabling dnf modules can lead to 'orphaned' packages that no longer receive updates or notices of applicable CVEs or Erratas.

Scenario:

1) dnf module install swig
.. installs swig ..

2) dnf module disable swig

3) At this point swig RPMs are still installed

4) Errata is released for critical CVE for swig

5) host does not show CVE as applicable because the module is 'disabled'

The only way for the user to know that there is an applicable swig errata is to go back in and run:

* dnf module enable swig

As far as we can tell, there is little to no use to use dnf's 'enable/disable' module feature since you are able to install and remove directly without ever enabling and disabling, eg this works fine:

* dnf module install swig
* dnf module remove swig

We should simplify and just stick to install and remove and not have customers confused as to why errata are no longer applicable on hosts that mistakenly disabled modules and left them in an orphaned state.


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