Confirmed users
3,990
edits
ReleaseEngineering/OPSI: Difference between revisions
Jump to navigation
Jump to search
→Check the hostkey
| Line 185: | Line 185: | ||
*** ssh into staging-opsi and check /home/cltbld/opsi-package-sources/hostkey-generator/CLIENT_DATA/hostkey.ins to see what it does | *** ssh into staging-opsi and check /home/cltbld/opsi-package-sources/hostkey-generator/CLIENT_DATA/hostkey.ins to see what it does | ||
* If they do not match you have to remove the master's entry as documented in [[ReleaseEngineering/How_To/Set_Up_a_Freshly_Imaged_Slave#Windows_.28OPSI.29|here]] | * If they do not match you have to remove the master's entry as documented in [[ReleaseEngineering/How_To/Set_Up_a_Freshly_Imaged_Slave#Windows_.28OPSI.29|here]] | ||
* If you see squares or a blank file delete the file and reboot the slave | |||
** TODO: Check if we need to do anything else | |||
The file should have a format like this: | |||
[shareinfo] | |||
pckey = <alphanumeric value> | |||
This file is created upon reboot by a scheduled task that calls: | |||
D:\tools\buildfarm\opsi\regenerate-hostkey.py | |||
=== Check the opsiconfd log === | === Check the opsiconfd log === | ||