RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
subscription-manager plugins currently has slots for a pre/post_product_id_install_hooks  It is being passed a conduit with a product_list.  A couple of requests:


1. These install hooks are also being called during a yum remove transaction with an empty product_list.  If the product_list is empty, there is no reason to call the pre/post_product_id_install_hooks.  Don't do it.

2. In case that product are about to be removed, we should build new slots for pre/post_product_id_revove and call the pre/post_product_id_revove_hooks when the removal list is non-empty.

3. All of the calls to pre/post_product_id_*_hooks should provided a mechanism for the plugins to alter the product_list.  It is conceivable that the plugin should be empowered to overrule/augment the install or removal of a product cert.

4. Currently the product_list is the only interesting data passed to the hooks.  Including the repo from which a product id cert is being installed may also be useful.  There may be other interesting values too. 


Version-Release number of selected component (if applicable):
[root@rhsm-accept-rhel6 ~]# rpm -q subscription-manager
subscription-manager-1.8.4-1.git.31.00b0b78.el6.x86_64

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

(In reply to John Sefler from comment #0)
> Description of problem:
> subscription-manager plugins currently has slots for a
> pre/post_product_id_install_hooks  It is being passed a conduit with a
> product_list.  A couple of requests:
> 
> 
> 1. These install hooks are also being called during a yum remove transaction
> with an empty product_list.  If the product_list is empty, there is no
> reason to call the pre/post_product_id_install_hooks.  Don't do it.

I think there may be some utility to this, especialy if #3/#4 are added. That would allow a plugin to install productids, that would not be selected for install otherwise (maybe a product that has no rpms in it's repo, for example).

Acking 7.1

This feature request was not implemented and delivered to QE by the rhel-7.1.0 Dev Freeze date of 10/27/2014.  Deferring for consideration in next release.