Some more investigation shows that issue appears as soon as admin_token plugin in keystoneauth1 is used. Before the mentioned commit, when using token_endpoint in osc, the token_endpoint plugin in openstackclient lib was used and worked fine, but his commit moves it to keystoneauth1.
If i force admin_token in os-client-config version 1.22.0 using --os-auth-type admin_token, i get the same issue:
# openstack domain list --quiet
+---------+---------+---------+--------------------+
| ID | Name | Enabled | Description |
+---------+---------+---------+--------------------+
| default | Default | True | The default domain |
+---------+---------+---------+--------------------+
# openstack --os-auth-type admin_token domain list --quiet
__init__() got an unexpected keyword argument 'project_domain_id'
Some more investigation shows that issue appears as soon as admin_token plugin in keystoneauth1 is used. Before the mentioned commit, when using token_endpoint in osc, the token_endpoint plugin in openstackclient lib was used and worked fine, but his commit moves it to keystoneauth1.
If i force admin_token in os-client-config version 1.22.0 using --os-auth-type admin_token, i get the same issue:
# openstack domain list --quiet ---+--- ------+ ------- --+---- ------- ------- --+ ---+--- ------+ ------- --+---- ------- ------- --+ ---+--- ------+ ------- --+---- ------- ------- --+
+------
| ID | Name | Enabled | Description |
+------
| default | Default | True | The default domain |
+------
# openstack --os-auth-type admin_token domain list --quiet
__init__() got an unexpected keyword argument 'project_domain_id'