Bug 1353188
| Summary: | ssh is not working from undercloud to created VM because of different MTU values | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | GenadiC <gcheresh> |
| Component: | openstack-neutron | Assignee: | Brent Eagles <beagles> |
| Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 (Mitaka) | CC: | amuller, beagles, chrisw, gcheresh, nyechiel, oblaut, sclewis, srevivo |
| Target Milestone: | async | Keywords: | ZStream |
| Target Release: | 9.0 (Mitaka) | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-neutron-8.1.2-3.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-24 12:56:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
GenadiC
2016-07-06 12:58:55 UTC
There are some known inconsistencies with how OSPd configures MTU that we are working on resolving (see https://review.openstack.org/#/c/333333/). Given your description, I'm going to guess that the default template parameters for NeutronDnsmasqOptions and NeutronTenantMtu were used and you are using tunneling is being used? If my assumption is correct, you can try altering NeutronTenantMtu to increase the MTU for the network. Due to some unfortunate mappings of parameters, it can be a little difficult to optimize everything, but if you set NeutronTenantMtu to 1500 the network should be lifted to 1450 (1500 - 50 bytes for tunneling overhead) and the MTU being passed to the guest via DHCP will be 1400. You could also try setting the NeutronDnsmasqOptions to fit more nicely - e.g: dhcp-option-force=26,1450. Let me know if the above assumptions were correct and whether the suggested changes help. We set NeutronTenantMtu to 1450 (the default was 1400) and created setup again. Indeed the network MTU was lifted to 1400 (was 1350 by default), but the MTU of the VM was lifted too - to 1450, so we got to the exactly same problem as before. I am not sure if it is related but looking on qrouter on compute node we see that qr has mtu of 1400 and rfp has mtu of 1450 Can you check the NeutronDnsmasqOptions to see if it is passing the MTU to the VMs via DHCP? If it is "dhcp-option-force=26,%MTU%" in the heat templates, you need to change it to 'disconnect' it from NeutronTenantMtu and set it lower than NeutronTenantMtu by 50 bytes or more. For example: if NeutronTenantMtu = 1500 change NeutronDnsmasqOptions to "dhcp-option-force=26,1450" Indeed after your proposed change of NeutronDnsmasqOptions I get the same MTU values on the network and on the VM Verified on latest version openstack-neutron-8.1.2-4.el7ost.noarch
MTU on both, network and VM is 1450
VM:
$ ifconfig
eth0 Link encap:Ethernet HWaddr FA:16:3E:8F:ED:53
inet addr:12.12.12.6 Bcast:12.12.12.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:fe8f:ed53/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1
RX packets:162 errors:0 dropped:0 overruns:0 frame:0
TX packets:183 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23322 (22.7 KiB) TX bytes:18374 (17.9 KiB)
NETWORK:
neutron net-show 15a1b5e2-6113-457d-94fd-07c71a7dd2b8
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| availability_zone_hints | |
| availability_zones | nova |
| created_at | 2016-08-23T18:18:52 |
| description | |
| id | 15a1b5e2-6113-457d-94fd-07c71a7dd2b8 |
| ipv4_address_scope | |
| ipv6_address_scope | |
| mtu | 1450
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1759.html |