Back to bug 1340479
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jeff Nelson | 2016-05-27 17:05:28 UTC | CC | jen, jsuchane | |
| Assignee | libvirt-maint | jdenemar | ||
| Jaroslav Suchanek | 2016-05-27 17:54:55 UTC | Status | NEW | ASSIGNED |
| Christian Horn | 2016-05-29 23:58:54 UTC | Link ID | Red Hat Knowledge Base (Solution) 2338791 | |
| Jiri Denemark | 2016-06-02 11:04:21 UTC | Status | ASSIGNED | POST |
| Doc Text | Cause: When choosing a TCP port for incoming migration, libvirtd doesn't check whether the port is unused. Consequence: Migration will fail if another process uses the TCP port libvirtd chose. Fix: The code that selects a free port from a migration port range was backported. Another patch which allows system administrators to configure what port range libvirt should use for migration was backported too. Result: System administrators can select a custom migration port range in case the default one conflicts with another software running on the same host and libvirtd will make sure the port it chooses from this range is not used by another process. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Jiri Denemark | 2016-06-02 11:48:50 UTC | Status | POST | MODIFIED |
| Fixed In Version | libvirt-0.10.2-29.el6_5.14 | |||
| errata-xmlrpc | 2016-06-02 11:49:32 UTC | Status | MODIFIED | ON_QA |
| Fangge Jin | 2016-06-06 03:03:57 UTC | Status | ON_QA | VERIFIED |
| CC | fjin | |||
| Jiri Herrmann | 2016-06-20 17:17:46 UTC | CC | jherrman | |
| Doc Text | Cause: When choosing a TCP port for incoming migration, libvirtd doesn't check whether the port is unused. Consequence: Migration will fail if another process uses the TCP port libvirtd chose. Fix: The code that selects a free port from a migration port range was backported. Another patch which allows system administrators to configure what port range libvirt should use for migration was backported too. Result: System administrators can select a custom migration port range in case the default one conflicts with another software running on the same host and libvirtd will make sure the port it chooses from this range is not used by another process. | Prior to this update, migrating a virtual machine failed when the libvirtd service used a transmission control protocol (TCP) port that was already in use. Now, it is possible to predefine a custom migration TCP port range in case the default port is in use. In addition, libvirtd now ensures that the port it chooses from the custom range is not used by another process. | ||
| errata-xmlrpc | 2016-06-20 18:03:47 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-20 19:26:58 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-20 15:26:58 UTC |
Back to bug 1340479