FWIW we've been experiencing this bug with our new Openstack cloud, and when I upgrade to 1.17.2, the error message goes away.
Do we have any idea on a release timeframe for this bug into a stable release? Ie, either when will 1.18 be out, or will there be a backport to 1.16? This is a critical issue for our new production cloud to be able to go live.
FWIW we've been experiencing this bug with our new Openstack cloud, and when I upgrade to 1.17.2, the error message goes away.
Do we have any idea on a release timeframe for this bug into a stable release? Ie, either when will 1.18 be out, or will there be a backport to 1.16? This is a critical issue for our new production cloud to be able to go live.