Comment 1 for bug 1938644

This seems to be an order of operations issue: looks like inserting the module after the container starts is the problem here. A fresh boot of a compute node loads the module via udev prior to the container starting (which works fine), inserting the module while the container is running produces the effect described, and stopping then starting the container also resolves it after loading the module.

I think the only actual bug here is the lack of correct log output/collection by the logging stack, and possibly some weirdness with ubuntu (the host os).

So if anyone else does this in their setup, you need to first load the kernel modules involved and udev rule to set hwrng to 0666, and only then run the `kolla-ansible reconfigure --tags nova` piece which should perform container restarts in the right order. If it still doesn't work, my "fix" may have been the piece of fully stopping the container then starting it back up.