Igor created IGNITE-26457:
-----------------------------
Summary: [DEB][RPM] Start after upgrade from 3.0.0 to 3.1.0 fails
due to missing ENV variable
Key: IGNITE-26457
URL: https://issues.apache.org/jira/browse/IGNITE-26457
Project: Ignite
Issue Type: Bug
Components: builds/deliveries ai3
Affects Versions: 3.1
Reporter: Igor
*Steps to reproduce:*
1. Start Cluster on version 3.0.0
2. Stop service(s).
3. Upgrade to 3.1.0:
in case *DEB* via command:
{code:java}
sudo DEBIAN_FRONTEND='noninteractive' apt-get -y -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install
--only-upgrade
/opt/pubagent/ignite3tests/tmp/deb/ignite3-db_3.1.0~SNAPSHOT_all-3.1.0-SNAPSHOT.deb{code}
in case *RPM* via command:
{code:java}
sudo dnf upgrade -y
/opt/pubagent/ignite3tests/tmp/rpm/ignite3-db-3.1.0~SNAPSHOT.noarch-3.1.0-SNAPSHOT.rpm{code}
4. Start service(s).
*Expected:*
Service(s) started.
*Actual:*
Service(s) is not started:
DEB:
{code:java}
sudo journalctl -u ignite3db.service
...
Sep 17 11:37:14 ip-192-168-209-232 systemd[1]: Started Apache Ignite Database
Service.
Sep 17 11:37:14 ip-192-168-209-232 start.sh[4443]: /usr/lib/ignite3db/start.sh:
20: .: cannot open /setup-java.sh: No such file
Sep 17 11:37:14 ip-192-168-209-232 systemd[1]: ignite3db.service: Main process
exited, code=exited, status=2/INVALIDARGUMENT
Sep 17 11:37:14 ip-192-168-209-232 systemd[1]: ignite3db.service: Failed with
result 'exit-code'.
Sep 17 11:37:19 ip-192-168-209-232 systemd[1]: ignite3db.service: Scheduled
restart job, restart counter is at 2.
Sep 17 11:37:19 ip-192-168-209-232 systemd[1]: Stopped Apache Ignite Database
Service.
...{code}
RPM:
{code:java}
sudo journalctl -u ignite3db.service
...
Sep 17 11:37:11 ip-192-168-208-51.us-east-2.compute.internal systemd[1]:
Started Apache Ignite Database Service.
Sep 17 11:37:11 ip-192-168-208-51.us-east-2.compute.internal start.sh[3421]:
/usr/lib/ignite3db/lib/bootstrap-functions.sh: line 20: /setup-java.sh: No such
file or directory
Sep 17 11:37:11 ip-192-168-208-51.us-east-2.compute.internal systemd[1]:
ignite3db.service: Main process exited, code=exited, status=1/FAILURE
Sep 17 11:37:11 ip-192-168-208-51.us-east-2.compute.internal systemd[1]:
ignite3db.service: Failed with result 'exit-code'.
Sep 17 11:37:17 ip-192-168-208-51.us-east-2.compute.internal systemd[1]:
ignite3db.service: Scheduled restart job, restart counter is at 3.
Sep 17 11:37:17 ip-192-168-208-51.us-east-2.compute.internal systemd[1]:
Stopped Apache Ignite Database Service.
... {code}
The problem is new variable appeared in `vars.env` of 3.1.0:
`LOG_DIR=/var/log/ignite3db`
*And during upgrade variables are not upgraded,* so this line
{code:java}
. ${LIBS_DIR}/setup-java.sh {code}
in `bootstrap-functions.sh` looks for `/setup-java.sh` instead of expected
`/var/log/ignite3db/setup-java.sh`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
