[ostf] Use proxy on primary controller for keystone client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Tatyanka | ||
5.1.x |
Fix Committed
|
Medium
|
Tatyanka | ||
6.0.x |
Fix Committed
|
Medium
|
Tatyanka |
Bug Description
In case of network connectivity problems on some controller other controller nodes in HA cluster mark it as offline, but if admin network works fine there, OSTF still uses proxy started on that node and returns 500 error:
AuthorizationFa
This issue can be reproduced in the following way:
1. Deploy HA environment with neutron
2. Login on controller which has the smallest id
3. Shut down management interface (emulate network connectivity failure e.g.: ovs-vsctl del-port br-mgmt br-mgmt--br-eth0)
4. Run health checks. All checks will fail with authorization failure
I propose to add an additional step there:
https:/
if len(self.
Changed in fuel: | |
milestone: | none → 5.1 |
Changed in fuel: | |
importance: | Undecided → High |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
importance: | High → Medium |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
tags: | added: release-notes |
Changed in fuel: | |
milestone: | none → 5.1.2 |
milestone: | 5.1.2 → 6.1 |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Undecided → Medium |
status: | New → Confirmed |
no longer affects: | fuel/6.1.x |
Changed in fuel: | |
milestone: | 6.0.1 → 6.1 |
I strongly disagree with provided approach..
Ostf should not go to each node and execute pcs status or any other shell command to find out primary controller.
If we need this kind of functionality lets register blueprint for 6.0, where we will provide a way for node
to report this kind of data to nailgun. And ostf will fetch this data from nailgun api.