nova-scheduler received request from nova-conductor only after ~40 minutes
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Invalid
|
High
|
Leontii Istomin |
Bug Description
Detailed bug description:
during boot_attach_
uuid of the instance: http://
We have found that nova-conductor wait responce from nova-scheduller during 60 seconds: http://
But nova-sheduller received the request only after 40 minutes and processed the request during 5 seconds: http://
Steps to reproduce:
1. deploy Fuel 9.0-217
2. apply fixes for succsessfull deployment due the following bugs:
https:/
https:/
https:/
https:/
restart nailgun and receiverd
3. boot 201 nodes in bootstrap
4. deploy env with 3 controllers, 20 computes+Ceph, 168 computes
5. replace rabbitmq to zeromq (http://
6. perform rally tests
Expected results:
All vms will be booted successfully during the test
Actual result:
Some instances was failed to boot (43 from 1000)
Reproducibility:
didn't try to repro
Workaround:
not found yet
Impact:
Some instances can';t be started
Description of the environment:
- Operation system: ubuntu
- Versions of components: mos9.0
- Reference architecture: 3 controllers, 20 computes+Ceph, 168 computes
- Network model: vxlan+DVR
- Related projects installed: replaced rabbitmq by zeromq
Additional information:
Diagnostic snapshot: http://
description: | updated |
tags: | added: area-nova |
Changed in mos: | |
assignee: | nobody → MOS Nova (mos-nova) |
milestone: | none → 9.0 |
importance: | Undecided → High |
status: | New → Confirmed |
Need to reproduce the issue. We can use 20-nodes environment. New oslo-messaging package with zero driver with timestamping is ready https:/ /review. fuel-infra. org/#/c/ 19937/ (http:// perestroika- repo-tst. infra.mirantis. net/review/ CR-19937/ mos-repos/ ubuntu/ 9.0/) Need to go though a message chain and find where message stucks.