Coverage increased (+0.008%) to 77.639% when pulling 4e9c420 on kayrus:token-domain-scope into c1ae5ed on gophercloud:master.

@kayrus Thanks!

Can you include a unit test with a domain-scoped fixture? Please don't copy and paste from the API docs, though - it should be a new fixture generated from a running OpenStack environment or devstack.

Build failed.

• gophercloud-unittest : SUCCESS in 2m 51s
• gophercloud-acceptance-test : FAILURE in 1h 05m 39s
• gophercloud-acceptance-test-ironic : SUCCESS in 27m 29s

@jtopjian I issued the token response from my environment as a base, then I copy-pasted the catalog and userids from the initial fixtures. I hope it is fine.

Build failed.

• gophercloud-unittest : SUCCESS in 3m 21s
• gophercloud-acceptance-test : FAILURE in 2h 28m 54s
• gophercloud-acceptance-test-ironic : FAILURE in 3m 14s

@jtopjian @huangtianhua looks like the OS_SUBNET_ID environment variable disappeared from the openlab landscape:

2019-09-18 12:02:26.714328 | ubuntu-xenial | +++ openrc:source:117                        :   export OS_SUBNET_ID=
2019-09-18 12:02:26.717761 | ubuntu-xenial | +++ openrc:source:117                        :   OS_SUBNET_ID=

Good find. I think this test has made more progress than previous ones - prior test failures haven't gotten to the point of running any tests.

There might be an issue with devstack creating the subnet:

2019-09-18 19:13:50.869488 | ubuntu-xenial | +++ ./script/stackenv:source:10              :   openstack subnet show private_subnet -c id -f value
2019-09-18 19:13:54.007126 | ubuntu-xenial | No Subnet found for private_subnet