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.

Created attachment 1717335 [details]
Demostration files

Description of problem:

Contrary to the documentation at https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#ordering, RPM runs the %postun script BEFORE the %triggerin script. This breaks systemd which incorrectly starts new service  versions using the old startup script.

orderupgrade.short inside the attached tarball is a text file offering concise documentation of what actually happens.


Version-Release number of selected component (if applicable):
rpm-4.14.2-37.el8.x86_64, rpm-4.15.1-3.fc32.1.x86_64, rpm-4.11.3-43.el7.x86_64

How reproducible:

Use build.sh in the supplied order.tar to build two subsequent versions of the order RPM. Install by pasting from install.sh line by line and observe that following the installation of version 1.1, "sleep" is restarted with the startup configuration from version 1.0.

Actual results:

%postun runs before %triggerin


Expected results:

%triggerin runs before %postun, as documented


Additional info:

There's no actual %triggerin scriptlet executing anywhere in that. All the %triggerfoo in the log are *file triggers* (%transfiletriggerin), it's just not differentiated in the debug output of rpm (see 'rpm -q --triggers systemd' vs 'rpm -q --filetriggers systemd'). 

The "regular" triggers run in the order they're documented, file triggers execution order doesn't seem to even be documented in any of these tables floating around, but see https://rpm.org/user_doc/file_triggers.html

We can consider the ambiguous diagnostics as a bug though.

Created attachment 1717439 [details]
Output sample with fixed diagnostics

Here's a sample output with the diagnostics fixed to show what's really going on.

https://github.com/rpm-software-management/rpm/pull/1376

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rpm bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1606