this bug has had no traction, is this still the case with the KSA sessions? If so, please re0open against keystoneauth.
this bug has had no traction, is this still the case with the KSA sessions? If so, please re0open against keystoneauth.