Comment 1 for bug 1710123

I have since reconfigured and redeployed designate without hitting the above errors.

It seems this issue is not to do with designate per se, but rather something in my environment
(I cannot quite say what at the moment, I don't yet know the root cause)

Marking this bug as invalid.