file descriptor limit alarm set in
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Confirmed
|
High
|
Kostiantyn Danylov | ||
| 6.0.x |
Confirmed
|
High
|
Kostiantyn Danylov | ||
| 6.1.x |
Confirmed
|
High
|
Kostiantyn Danylov | ||
Bug Description
api: '1.0'
astute_sha: c3e7c7a18528cf9
auth_required: true
build_id: 2014-10-16_19-59-04
build_number: '72'
feature_groups:
- mirantis
fuellib_sha: 677c2809bd602ed
fuelmain_sha: 5cf06aac43ccb4a
nailgun_sha: b83eaf18cbcc363
ostf_sha: de177931b53fbe9
production: docker
release: '6.0'
Steps to reproduce:
1. From Fuel deploy cluster with 3 controllers in HA and 97 computes+cinder on Juno on Ubuntu 12.04.4
2. Run deploy and tempest.
a lot of "file descriptor limit alarm set" founds in rabbitmq logs
On the main controller
root@node-28:~# su rabbitmq -s /bin/sh -c 'ulimit -n'
1024
because /var/log has 23G size I can't attach full snapshot but rabbitmq logs from active controller attached
| Sergey Galkin (sgalkin) wrote | #1 |
| Changed in mos: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → MOS Linux (mos-linux) |
| milestone: | none → 6.0 |
| tags: | added: mos-linux |
| Changed in mos: | |
| assignee: | MOS Linux (mos-linux) → Kostiantyn Danylov (kdanylov) |
| Changed in mos: | |
| milestone: | 6.0 → 6.1 |
