yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #46860
[Bug 1549471] [NEW] Networks with an MTU of zero makes zero sense
Public bug reported:
vagrant@vagrant-ubuntu-wily-32:~/devstack$ neutron net-show a99a3d30-19a0-4e69-9e90-129d192e5948
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| availability_zone_hints | |
| availability_zones | nova |
| id | a99a3d30-19a0-4e69-9e90-129d192e5948 |
| is_default | False |
| mtu | 0 |
| name | public |
| port_security_enabled | True |
| provider:network_type | flat |
| provider:physical_network | default |
| provider:segmentation_id | |
| router:external | True |
| shared | False |
| status | ACTIVE |
| subnets | f83007e9-0907-488b-9a45-940984d1f4dc |
| | 2cb54543-2302-4142-8f3b-735fd5aa73fb |
| tenant_id | f8190c1517b7455a89dc952d43f890eb |
+---------------------------+--------------------------------------+
So yeah let's try and clean this up somehow. I imagine that part of it has to be the physical_network_mtus setting
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
Status: New
** Summary changed:
- Networks with an MTU of zero make zero sense
+ Networks with an MTU of zero makes zero sense
** Changed in: neutron
Assignee: (unassigned) => Sean M. Collins (scollins)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1549471
Title:
Networks with an MTU of zero makes zero sense
Status in neutron:
New
Bug description:
vagrant@vagrant-ubuntu-wily-32:~/devstack$ neutron net-show a99a3d30-19a0-4e69-9e90-129d192e5948
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| availability_zone_hints | |
| availability_zones | nova |
| id | a99a3d30-19a0-4e69-9e90-129d192e5948 |
| is_default | False |
| mtu | 0 |
| name | public |
| port_security_enabled | True |
| provider:network_type | flat |
| provider:physical_network | default |
| provider:segmentation_id | |
| router:external | True |
| shared | False |
| status | ACTIVE |
| subnets | f83007e9-0907-488b-9a45-940984d1f4dc |
| | 2cb54543-2302-4142-8f3b-735fd5aa73fb |
| tenant_id | f8190c1517b7455a89dc952d43f890eb |
+---------------------------+--------------------------------------+
So yeah let's try and clean this up somehow. I imagine that part of it has to be the physical_network_mtus setting
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1549471/+subscriptions
Follow ups