Bug 1273945
| Summary: | System information services table doesn't respect region | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Martin Pavlásek <mpavlase> | ||||||||||||||
| Component: | python-django-horizon | Assignee: | Itxaka <iserrano> | ||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Ido Ovadia <iovadia> | ||||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||||
| Priority: | low | ||||||||||||||||
| Version: | 7.0 (Kilo) | CC: | aortega, athomas, iserrano, mpavlase, mrunge, obaranov, srevivo | ||||||||||||||
| Target Milestone: | --- | Keywords: | Triaged, ZStream | ||||||||||||||
| Target Release: | 7.0 (Kilo) | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2016-05-02 10:55:57 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Martin Pavlásek
2015-10-21 14:38:33 UTC
Created attachment 1085180 [details]
screenshot, not modified
Created attachment 1085181 [details]
keystone endpoint-list
Created attachment 1085182 [details]
keystone service-list
Created attachment 1085183 [details]
keystone service-get 1d219df84e8f47f6a531856996e612c7
Martin, I am unable to reproduce this on rhos7. I created several endpoints: keystone endpoint-create --region Regionone --service swift_s3 --publicurl http://google.com --adminurl http://google.com --internalurl http://google.com keystone endpoint-create --region waaaa --service swift_s3 --publicurl http://google.com --adminurl http://google.com --internalurl http://google.com keystone endpoint-create --region regionone --service swift_s3 --publicurl http://google.com --adminurl http://google.com --internalurl http://google.com keystone endpoint-list +----------------------------------+-----------+-------------------------------------------------+-------------------------------------------------+----------------------------------------------+----------------------------------+ | id | region | publicurl | internalurl | adminurl | service_id | +----------------------------------+-----------+-------------------------------------------------+-------------------------------------------------+----------------------------------------------+----------------------------------+ | 24d43b0a25304ffaab1c275b1b4f0847 | RegionOne | http://192.168.1.150:8776/v1/%(tenant_id)s | http://192.168.1.150:8776/v1/%(tenant_id)s | http://192.168.1.150:8776/v1/%(tenant_id)s | 10b89225067f4cb6be14565bbfeab089 | | 37d070410e3d44e38ead1c9e0bc87f33 | RegionOne | http://192.168.1.150:8779/v1.0/%(tenant_id)s | http://192.168.1.150:8779/v1.0/%(tenant_id)s | http://192.168.1.150:8779/v1.0/%(tenant_id)s | 40efc8fffaa547e3be0b19d494c76b62 | | 423733b63f3c4c6d89dceeb29ba1c618 | RegionOne | 192.168.1.150 | 192.168.1.150 | 192.168.1.150 | e792f93904cd4711812fd0198ed79e82 | | 51b808927a8b4eb4990873d5673e81c7 | RegionOne | http://127.0.0.1:8774/v3 | http://127.0.0.1:8774/v3 | http://127.0.0.1:8774/v3 | 18e50425443941c8a412c07638b8eb90 | | 5a1d5cd55670407fb55ae81a8220b099 | RegionOne | http://192.168.1.150:9292 | http://192.168.1.150:9292 | http://192.168.1.150:9292 | 75ec1b6cba0a4dbaa5fc53631fd80554 | | 5b4fe8673f4e48d8bfe9ff1a1ab159b5 | RegionOne | http://192.168.1.150:8773/services/Cloud | http://192.168.1.150:8773/services/Cloud | http://192.168.1.150:8773/services/Admin | 28736c9703304030b69649c32be6c473 | | 65a57a77ad6244e4838f2e37e3e702a9 | RegionOne | http://192.168.1.150:8777 | http://192.168.1.150:8777 | http://192.168.1.150:8777 | 6c27c312e50d41f181ee3ad62a3cea0c | | 6bb1e5e1985e4842a4acc8a181c89301 | Regionone | http://google.com | http://google.com | http://google.com | e31d04d5729e4cb985f48d411f441f62 | | 6e8b4cb8f3cf4061b6a6a6ed23320e31 | waaaa | http://google.com | http://google.com | http://google.com | e31d04d5729e4cb985f48d411f441f62 | | 75ff5798b77f435bac5c7f7d09f5153e | RegionOne | http://192.168.1.150:8776/v2/%(tenant_id)s | http://192.168.1.150:8776/v2/%(tenant_id)s | http://192.168.1.150:8776/v2/%(tenant_id)s | 314ee09dafc7476aaf552d4839b4265e | | 8988a16ecf234138bf4e83f7e31de06a | RegionOne | http://192.168.1.150:8080/v1/AUTH_%(tenant_id)s | http://192.168.1.150:8080/v1/AUTH_%(tenant_id)s | http://192.168.1.150:8080 | 077fd0fca9d64d1cba7e5a533aee9ff4 | | 99ef8e8dfcd24a1a8a1621b52af7b345 | RegionOne | http://192.168.1.150:5000/v2.0 | http://192.168.1.150:5000/v2.0 | http://192.168.1.150:35357/v2.0 | 434cb662e86c431385ac827f941cb1d7 | | b81692b11eb446a98ac14f7282c7ace8 | RegionOne | http://192.168.1.150:8004/v1/%(tenant_id)s | http://192.168.1.150:8004/v1/%(tenant_id)s | http://192.168.1.150:8004/v1/%(tenant_id)s | 4959f332483f4d6aa2ee22992f047b4e | | bbd7bb0a2c3f490599f97c391d7a2376 | RegionOne | http://192.168.1.150:8080 | http://192.168.1.150:8080 | http://192.168.1.150:8080 | e31d04d5729e4cb985f48d411f441f62 | | d51733c28f844d9eb9c2b8eb64496e1b | RegionOne | http://192.168.1.150:8774/v2/%(tenant_id)s | http://192.168.1.150:8774/v2/%(tenant_id)s | http://192.168.1.150:8774/v2/%(tenant_id)s | 2d505451cc8c4582b082e0cd1ff55cd5 | | dcafdafa943145e989bb9e85747638d5 | regionone | http://google.com | http://google.com | http://google.com | e31d04d5729e4cb985f48d411f441f62 | | fc31e644691c4b218db8e5843fa866aa | Regionone | http://google.com | http://google.com | http://google.com | 2d505451cc8c4582b082e0cd1ff55cd5 | | fe89106221c14eecb170d85585cce05a | RegionOne | http://192.168.1.150:9696 | http://192.168.1.150:9696 | http://192.168.1.150:9696 | 76df182f77c74fc0a993a6df1e478389 | +----------------------------------+-----------+-------------------------------------------------+-------------------------------------------------+----------------------------------------------+----------------------------------+ But instead of getting the modified ones in my list, I just get the proper ones and get extra regions for the other ones created. See attached image. Can you tell me how did you changed the name to the endpoint? Did you modify it in the database directly? Created attachment 1150405 [details]
extra endpoints
Im just thinking that if you modified from database directly then this is the expected output. What it shows on your attachements seems to be that there is a service on the services table called s3 (swift_s3) but it could not find an endpoint for that service in the current region. I can reproduce it if I change to one of the fake regions that I created which only have one endpoint, see attachement. From my pòint of view, this is not a bug, its the expected result, but I'll await Martin's comments on this before closing it. Created attachment 1150406 [details]
Endpoints missing, expected output
I didn't change name of service even touch database directly. The service was created by packstack. Martin, to me this seems the correct output. What it shows on your attachements seems to be that there is a service on the services table called s3 (swift_s3) but it could not find an endpoint for that service in the current region, thus it shows it as yellow and with no address. That it appears on the tables doesn't mean that it mistakenly used the wrongly named endpoint. It means that there is a service on the database for swift but on the current region there is no endpoint. The separation is so clear that it even allows you to change regions to the mistakenly named region in the region selector. Now, if the issue here is why that service was called differently then we should move that to packstack, but this is not a bug, is behaving properly. Please let me know if Im missing the point of the issue before I close it. Thanks! Hi Itxaka, thank you for your comment, now I understand it properly. I agree, this behavior from Horizon side is correct. Actually I think there is bug in packstack, because all services should belongs to same region (and not RegionOne/regionOne). What do you think, file a new bug, or just update this one? Martin, I think a new bug would be the proper way as to not have extra comments on it that have nothing to do with it, but I dont mind if you reuse this one. Cheers, Itxaka Sounds reasonable, I'll fill a new bug about it. Closing as not-a-bug. Thank you for cooperation, Martin |