Comment 3 for bug 1596638

Confirmed. This seems to be a regression in 9.20160110ubuntu0.1. I couldn't reproduce in a container that I'd already tested 9.20160110. Perhaps a compiled module got left behind on update? But it does affect new Xenial containers that have 9.20160110ubuntu0.1 installed fresh (not upgraded). This impacts server use cases where people deploy new cattle instead of upgrading pets.