ilorest doesn't start on CIS hardened system => --version

[Jose Guedez]

Affected version: 0b91633644ad3e53558218f5f6e4efe0c73431ce (edge channel, revision 19)

$ juju status | grep -m1 hw-health
hw-health active 36 hw-health edge 19 no ready

Essentially the same thing as LP#1935032, so this can be considered a regression.

It seems that a commit (2a026482a552a4fb389e5bf0abd2dfc17c9194b4) after the original bugfix introduced a second call to ilorest, without passing the TMP environment variable that fixed the issue:

$ /usr/sbin/ilorest --version
/usr/sbin/ilorest: error while loading shared libraries: libz.so.1: failed to map segment from shared object

$ export TMP="/var/lib/hw-health"
$ /usr/sbin/ilorest --version
RESTful Interface Tool 3.2.2

It is probably a good idea to define a helper for the call to ilorest, and then reuse it in the check to hopefully avoid the issue from surfacing again in the future. Also adding it to some documentation/comments for the people submitting patches to raise awareness about the issue

[Mert Kirpici (mertkirpici)]

Revision 27 that contains the fix is now released on channel edge.