Wrong network is used for keystone endpoint

Bug #1441855 reported by Mike Scherbakov
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Aleksandr Didenko

Bug Description

Fuel 6.1 (master), ISO build around ~233

keystone endpoint-list:

 bc40e7c959be42eeb43135b971293d92 | RegionOne | | | | 903c65eb6fcb4abdb18eb4f369dcb695

You can see here, that both internal & admin IPs are from public network, not from internal. It has to be here.

It was originally discovered by Alex Shaposhnikov on the scale lab, so I'm opening this bug on his behalf.

Changed in fuel:
status: New → Triaged
importance: Undecided → Critical
assignee: Fuel Library Team (fuel-library) → Aleksandr Didenko (adidenko)
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

Here's output from ISO "build_number": "255"

root@node-6:~# keystone endpoint-list | grep 5000
| 3cf3cc1fc1a6428690ad09820c6fbbb6 | RegionOne | | | | 3e1cc6ac16934f5c9a1f883de4821ac0 |

I've checked manifests, in current master we use management_vip for admin and internal addresses in endpoint configuration.

Changed in fuel:
status: Triaged → Invalid
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Thanks Alex, I've passed it to Alex S. to take a look.

Revision history for this message
Aleksandr Shaposhnikov (alashai8) wrote :

Thanks guys for investigation but it was our scripts fault, we changed endpoint in prepare job to be able to manipulate keystone objects from outside which isn't correct way of doing that. Since keystone/haproxy/iptables got fixed in new releases this way finaly lead as to dead end :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers