I marked this an invalid as it wasn't a current bug in Keystone. The problem was a Debian specific patch that looks to be a fix for an issue we may have had in the past.
I marked this an invalid as it wasn't a current bug in Keystone. The problem was a Debian specific patch that looks to be a fix for an issue we may have had in the past.