For what it is worth, there isn't much that can be done for 2.6 unless the oslo.log developers can think of a way around this without having users patch their copy of 2.6. This also appears to be affecting 2.7 so I'm updating the title to be less misleading.
For what it is worth, there isn't much that can be done for 2.6 unless the oslo.log developers can think of a way around this without having users patch their copy of 2.6. This also appears to be affecting 2.7 so I'm updating the title to be less misleading.