Comment 5 for bug 1610138

I attempted to recreate this manually without success. I used the following process;

1.) create a new regions so there are two in the deployment
2.) create a new service of the same type as an existing service but different name `keystone1`
3.) create an endpoint an associate it to the new service and region
4.) get the catalog

Additional information below:

$ openstack region list -f yaml
- Description: ''
  Parent Region: null
  Region: RegionOne
- Description: ''
  Parent Region: null
  Region: RegionTwo
$ openstack service list -f yaml
- ID: 379688e0b3df4d87b36b9eb3bca62168
  Name: keystone
  Type: identity
- ID: 4b278a66df2a4ec18395c7b586b10747
  Name: keystone1
  Type: identity
$ openstack endpoint list -f yaml
- Enabled: true
  ID: 0af66ca7532c4bcea8d33c350dd004c6
  Interface: admin
  Region: RegionOne
  Service Name: keystone
  Service Type: identity
  URL: http://192.168.122.160:35357/
- Enabled: true
  ID: 383440e8128b4c669d3ef791bcecf401
  Interface: public
  Region: RegionTwo
  Service Name: keystone1
  Service Type: identity
  URL: http://192.168.122.160:35357/
- Enabled: true
  ID: e0eed76efd2d49879a4db2532161105c
  Interface: public
  Region: RegionOne
  Service Name: keystone
  Service Type: identity
  URL: http://192.168.122.160:35357/
$ openstack catalog list -f yaml
- Endpoints: "RegionOne\n admin: http://192.168.122.160:35357/\nRegionOne\n public:\
    \ http://192.168.122.160:35357/\n"
  Name: keystone
  Type: identity
- Endpoints: "RegionTwo\n public: http://192.168.122.160:35357/\n"
  Name: keystone1
  Type: identity