Fail to establish connection to keystone in case if master node has big numbers of cpu
Bug #1602434 reported by
Andrey Grebennikov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Dmitry Ilyin | ||
7.0.x |
Fix Released
|
Medium
|
Anton Chevychalov | ||
8.0.x |
Fix Released
|
Medium
|
Anton Chevychalov | ||
Mitaka |
Fix Released
|
Medium
|
Alex Schultz |
Bug Description
MOS8
Fuel node has 48 vcpus. Keystone docker container configures Keystone to have the number of workers equal to the doubled number of vcpus (in my case is is 48+48=96).
At the same time Postgres DB allows 100 connections by default.
Eventually it comes to the point when neither of Fuel CLI commands work since it cannot connect to Postgres, as well as OSTF server cannot establish new connections because of the same reason.
It is necessary find a way to limit the number of workers for the Keystone on the Fuel node.
tags: | added: area-ostf |
Changed in fuel: | |
milestone: | none → 9.1 |
assignee: | nobody → Fuel QA Team (fuel-qa) |
importance: | Undecided → Medium |
tags: |
added: area-library removed: area-ostf |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 9.1 → 10.0 |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Alex Schultz (alex-schultz) |
tags: | added: on-verification |
Changed in fuel: | |
status: | In Progress → Fix Released |
tags: | added: on-verification |
To post a comment you must log in.
ostf does not configure keystone