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:

E.g. suppose I have a package 
  tst1234pkgA containing /usr/local/tst1234pkgA
and package
  tst1234pkgB containing /usr/local/tst1234pkgB

When I configure action as follows:

/usr/local/tst1234pkg*:any:/bin/echo $name $arch $ver $rel $epoch $repoid $state

and remove both packages only one action is executed (e.g. for package tst1234pkgB). The behavior is same also for install action (and probably also update action). 

Version-Release number of selected component (if applicable):
yum-utils-1.1.30-17.el6_5 and 1.1.30-23.el6

How reproducible:
always

Steps to Reproduce:
1. see above

Actual results:
configured action is executed just for the one package, in this case:
tst1234pkgB noarch 1.0 1 0 installed remove

Expected results:
action is executed for each package containing file matching the pattern
tst1234pkgA noarch 1.0 2 0 installed remove
tst1234pkgB noarch 1.0 1 0 installed remove


Additional info:
Proposed behavior would make it compliant with matching against package name. Currently package name pattern "tst1234pkg*" would result in:
tst1234pkgA noarch 1.0 2 0 installed remove
tst1234pkgB noarch 1.0 1 0 installed remove
Also, see bug 1045494 where the remove part was fixed.

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/