Before an upgrade the health check script checks if /elastifile/conf/elfs-params.conf file exists in the cluster.
To confirm if the file exists:
$ ls -la /elastifile/conf/elfs-params.conf
In case that a system has /elastifile/conf/elfs-params.conf the health check will fail if it does not have a copy of it named /elastifile/conf/elfs-params.conf.new in the same directory.
Health Check Status
$ python ecfs_health_check.py -p <ADMIN_PASSWORD>
System Configuration
====================
...
ELFS Params File: exist ERROR
Status
OK - elfs-params.conf does not exist
WARNING - both elfs-params.conf and elfs-params.conf.new exist.
In this case, please check with Elastifile Support team if the file indeed needed, and if the next version does not solve it without a manual conf file.
Send the following output:
$ cat /elastifile/conf/elfs-params.conf
$ cat /elastifile/conf/elfs-params.conf.new
FAIL - elfs-params.conf exist without a elfs-params.conf.new file in addition.
Send the Elastifile team the contents of the elfs-params.conf file to determine if the next version still requires the conf file.
One workaround for the upgrade is to recreate the config file:
$ cp /elastifile/conf/elfs-params.conf /elastifile/conf/elfs-params.conf.new
Rerun the health check script afterwards to make sure no issues before the upgrade.