Live migration's assigned ports conflicts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Invalid
|
High
|
Oleksii | ||
7.0.x |
Invalid
|
High
|
MOS Nova |
Bug Description
It looks like during live migration some generated port to use for live migration didn't checked for being already used and/or didn't have a re-get new port if the old one got occupied by someone else.
Here is an example of this behavior in nova-compute log files from the source compute node:
2015-09-
2015-09-
Resumed (Lifecycle Event)
2015-09-
2015-09-
2015-09-
2015-09-
Some env description:
root@node-169:~# nova-compute --version
2015.1.1
root@node-169:~# dpkg -l |grep 'nova-compute '|awk '{print $3}'
1:2015.
Steps to reproduce:
Actually this happens during rally testing of pretty big env (~200 nodes) one per 200 iterations so chances for getting that on scale are pretty big. So it should be easily reproduced under following circumastances:
1. Very high rate of migrations.
2. A lot of running VMs/other services with large amount of used TCP ports.
Both of these statements will lead to the higher chances of getting collision for qemu migration port allocation procedure.
Diagnostic Snapshot: http://
affects: | nova → mos |
no longer affects: | nova |
description: | updated |
Changed in mos: | |
assignee: | nobody → MOS Nova (mos-nova) |
milestone: | none → 8.0 |
Changed in mos: | |
status: | Invalid → Confirmed |
This requires more investigation so changing to Incomplete. Please set back to New when you have clear problem statement and steps to reproduce.