[MXS-2969] maxscale service still not stopped / restarted on package upgrade Created: 2020-04-17  Updated: 2020-08-25  Resolved: 2020-04-23

Status: Closed
Project: MariaDB MaxScale
Component/s: Packaging
Affects Version/s: None
Fix Version/s: 2.3.19, 2.4.9

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: package

Issue Links:
Relates
relates to MXS-2810 maxscale process still running after ... Closed
relates to MXS-2931 MXS-2810 still unfixed in RHEL / Cent... Closed

 Description   

The POSTUN script starts with:

if [ "$1" = "0" ] || [ "$1" = "remove" ]

so all actions in it will actually only be executed on real package removal, not up package upgrade, where $1 – the number of package installations by this name being active after the RPM transaction has finished – will be 1, not 0

So on yum update:

  • no maxscale process restart, old version keeps running
  • no update of /etc/logrotate.d/maxscale_logrotate (as this is copied over from /usr/share, and not directly contained in the package files maintained by rpm itself. This would actually be a problem by itself anyway, as if the POSTUN script actually worked any manual edits to the file would simply be lost, instead of being preserved by rpm in a .rpmold file)
  • ... maybe more ...

Generated at Thu Feb 08 04:18:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.