This seems to be reported rather consistently, and is not a case of a misconfigured crypttab: all users reporting this issue show a crypttab that correctly sets up their crypted swap, *and* swapon -s shows that the swap is enabled successfully after boot. But for some reason mountall thinks it hasn't been activated, which means the boot stalls. We should definitely get this fixed.
This seems to be reported rather consistently, and is not a case of a misconfigured crypttab: all users reporting this issue show a crypttab that correctly sets up their crypted swap, *and* swapon -s shows that the swap is enabled successfully after boot. But for some reason mountall thinks it hasn't been activated, which means the boot stalls. We should definitely get this fixed.