-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Labels
Description
Steps to reproduce:
List the minimal actions needed to reproduce the behaviour.
- download influxdb 1.11.8 and 1.12.2 rpm packages from https://repos.influxdata.com/packages/
- Install version 1.11.8 of influxDB on your choice of RHEL system (i.e. Rocky, CentOS, RHEL)
yum localinstall <influxdb1.11.8>.rpm
- Run
systemctl enable --now influxdb
- Verify influxdb is running
systemctl status influxdb
- Upgrade to version 1.12.2 using
yum localinstall <influxdb1.12.2>.rpm
- Run
systemctl daemon-reload
- Run
systemctl status influxdb
and see an error that there is no unit file
Expected behaviour:
InfluxDB upgrades from 1.11.8 to 1.12.2 successfully.
Actual behaviour:
During the upgrade process we see the following:
# yum install influxdb-1.11.8
...
# yum upgrade
...
(9/10): influxdb-1.12.2-1.x86_64.rpm
...
Running scriptlet: influxdb-1.12.2-1.x86_64 9/20
Upgrading : influxdb-1.12.2-1.x86_64 9/20
Running scriptlet: influxdb-1.12.2-1.x86_64 9/20
Synchronizing state of influxdb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable influxdb
Created symlink /etc/systemd/system/influxd.service → /usr/lib/systemd/system/influxdb.service.
Created symlink /etc/systemd/system/multi-user.target.wants/influxdb.service → /usr/lib/systemd/system/influxdb.service.
...
# systemctl enable influxdb.service
Failed to enable unit: Unit file influxdb.service does not exist.
If you take a look at the 1.11.8 vs 1.12.2 post install files you'll notice that we use sysV previously where we are now using systemd. This is currently where I hypothesize the issue stems from.
nicolargo