[library] Deployment of new controllers causes services downtime
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Fuel QA Team |
Bug Description
Fuel version info: http://
Steps to reproduce:
1. Create new cluster (Ubuntu, HA, NovaFlatDHCP, Ceph for images, Sahara, Ceilometer)
2. Add 3 controller+mongo, 4 compute and 4 cinder+ceph nodes (I tested on hardware)
3. Deploy changes. Run long-time (at least concurrency * 100 requests) Rally benchmark test on deployed cloud. I used concurrency = 80, but it could be smaller or greater depending on hardware specifications (cluster should be able to handle all incoming requests without overload/errors).
4. During performance testing add 2 new controllers to the environment and deploy changes
Expected result:
- deployment is successful, Rally test ends with 100% success (all requests to nova for create/delete instance were handled)
Actual result:
- deployment is successful, but Rally got a lot of 504/502 errors from HAProxy (Nova-api) and test was aborted:
http://
As you can see during few minutes nova-api was unreachable and most of requests from Rally failed. Here you can find the part of syslog on primary controller (node-18):
http://
And the part of HAProxy stats:
http://
Link to the diagnostic snapshot: https:/
summary: |
- [library] Deploying of new controllers cause services downtime + [library] Deployment of new controllers causes services downtime |
Changed in fuel: | |
importance: | Undecided → Medium |
description: | updated |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: release-notes |
Changed in fuel: | |
milestone: | 6.0 → next |
Changed in fuel: | |
milestone: | next → 7.0 |
Should this be included into Release notes?
Is there any workaround?