Closed tectumopticum closed 7 months ago
I have tried to play around a little with this configuration and I can get the service path to contain a leading \
.
Does this happen on a regular basis by installing Icinga for Windows v.12.1 or v1.12.2 or does it appear random?
It is reproducible with IfW v1.12.2 (probably v1.12.1 too, but I didn't check this)
After an installation with framework 1.12.1 the output of "Icinga for Windows Service Path" contains a leading "\" in
"show-icinga"
-output when the cmdlet is called in the same ps-window directly after the kickstart-script has finished:As a result the info about the installed version for "service" keeps empty:
As a result the service couldn't be started by the installation-script.
If you open an new admin-ps-instance and call the same cmdlet again, everything seems to be ok again. Probably it is a result of a modification-process of a variable during the installation.
Tested it with Framework 1.11.1: no leading backslash. This means it is not a typo in our configuration and it has been introduced with framework >= 1.12.0.