In this case, keystonemiddleware is upgraded to pulls in a newer oslo.serialization, but that offends stable/juno's oslo.serialization>=1.0.0,<=1.2.0 (which python-neutronclient 2.3.12 correctly includes in its requirements.txt)
TBH I dont' really remember the consensus on the overlaps. I thought we added those specifically to ensure grenade upgrades work with the client libraries held back, but looking at the current state of g-r it looks they are not consistent across all of the client libs.
I think this is a requirements bug not necessarily a neutronclient bug.
python- neutronclient has an overlapping range between juno and kilo:
stable/juno: python- neutronclient> =2.3.6, <2.4.0 neutronclient> =2.3.11, <2.5.0
stable/kilo: python-
In this case, keystonemiddleware is upgraded to pulls in a newer oslo.serialization, but that offends stable/juno's oslo.serializat ion>=1. 0.0,<=1. 2.0 (which python- neutronclient 2.3.12 correctly includes in its requirements.txt)
TBH I dont' really remember the consensus on the overlaps. I thought we added those specifically to ensure grenade upgrades work with the client libraries held back, but looking at the current state of g-r it looks they are not consistent across all of the client libs.