This is seen for all the services. "The option "configkey" in conf is not known to auth_token" is seen specifically only for Panko and Gnocchi.
The logging happens at https://github.com/openstack/keystonemiddleware/blob/stable/pike/keystonemiddleware/_common/config.py#L57 where all the key-values in the global variables list is looped through. Every middleware/filter in the paste pipeline can update this information.
For eg. the configkey referred to above comes from https://github.com/openstack/panko/blob/stable/pike/panko/api/app.py#L80
and for Gnocchi from here >> https://github.com/gnocchixyz/gnocchi/blob/master/gnocchi/rest/app.py#L118
So, there are always going to be some values that are not relevant from the authtoken middleware perspective and they will get logged. I am not sure where __file__ and here are coming from but those two seem to be common across all services.
This is seen for all the services. "The option "configkey" in conf is not known to auth_token" is seen specifically only for Panko and Gnocchi.
The logging happens at https:/ /github. com/openstack/ keystonemiddlew are/blob/ stable/ pike/keystonemi ddleware/ _common/ config. py#L57 where all the key-values in the global variables list is looped through. Every middleware/filter in the paste pipeline can update this information.
For eg. the configkey referred to above comes from https:/ /github. com/openstack/ panko/blob/ stable/ pike/panko/ api/app. py#L80
and for Gnocchi from here >> https:/ /github. com/gnocchixyz/ gnocchi/ blob/master/ gnocchi/ rest/app. py#L118
So, there are always going to be some values that are not relevant from the authtoken middleware perspective and they will get logged. I am not sure where __file__ and here are coming from but those two seem to be common across all services.