Starting node fails with iSCSI errors

[Rod Smith]

Until today, I was able to enlist, commision, and start nodes via my 14.04 MAAS server. Now it's begun to fail, as shown in the screen shot of an attempt to start a previously-commissioned node. This attempt was using the fast-path installer. The on-screen error messages seem to implicate iSCSI problems.

[Mark Brown (mstevenbrown)]

This is also being seen at initial PXE boot (trying to declare).

[Rod Smith (rodsmith)]

Additional information: After about half an hour, the system stops trying and gives me an "(initramfs)" prompt.

I've also now tested this with a fresh enlistment, and I get the same error. Switching to the d-i installer for a "Start" operation causes this problem to go away, but the kernel versions are out of sync at the moment, which is why I was using fast-path, so this doesn't really do me any good right now.

[Rod Smith (rodsmith)]

This may be a duplicate (resurrection?) of bug 1300026

[Mark Brown (mstevenbrown)]

A fresh import works.....until you reboot. Even if you changed nothing else in the configuration of the server or maas, enlistment will no longer work until you do another maas-import-pxe-files at which time things will work again.

[Mark Brown (mstevenbrown)]

I cannot find any sign that the tgt targets configuration is being saved anywhere -- it used to be saved in /var/lib/maas/ephemerals directory.

[Gavin Panella (allenap)]

Could this be related to bug 1300548?

[Mark Brown (mstevenbrown)]

Yes, this is directly related. Applying the symlink shown in the code diff for bug 1300548 solves this problem.