The %postun step gets run at the end of an upgrade (confusing, I know).
If a user has an existing BWC system on CentOS/RHEL, and upgrades, we remove the st2-auth-ldap module. The correct approach is to check how many packages will be left on the system after this operation, and only run the removal step if this is the removal of the final version of st2-auth-ldap.
As a workaround, users can either remove/re-install the package with this:
The
%postun
step gets run at the end of an upgrade (confusing, I know).If a user has an existing BWC system on CentOS/RHEL, and upgrades, we remove the st2-auth-ldap module. The correct approach is to check how many packages will be left on the system after this operation, and only run the removal step if this is the removal of the final version of st2-auth-ldap.
As a workaround, users can either remove/re-install the package with this:
Or they can just re-run the
%postinst
step:Related issues: https://github.com/StackStorm/st2/issues/3213 and https://github.com/StackStorm/st2-packages/issues/418