There was apost from the beta:
We don't know what caused the problem. Some part of the upgrade process. XG sllows two firmwares to be "installed" at the same time. If you flip back and forth between them then it is possible that something screwed up. If you are doing something, for example, to have one slot maintained as 17.5 while the other slot is EAP1, then EAP2, then EAP3. In order to do that you keep booting into 17.5 so you can install into your 18 slot. Potentially there is a problem there.
But if you are always installing to the non-active slot and always booting to a newer version and never back, I don't see how even theoretically this could happen.
Hopefully in the real world 17.5 MR9 -> 18.0 GA upgrade this will be a lot more straight forward upgrade and this won't occur.
If anyone else experiences this, please let me know.
Symptoms
AD SSO (NTLM, Kerberos) is not working.
/log/nasm.log complains about missing files
In any case, the solution is fairly easy:
service -ds nosync nasm:stop
rm -rf /content/nasm
service -ds nosync nasm:start
--> This also helps us after a upgrade frm 17.5.12 to 18 MR3
This thread was automatically locked due to age.
