Tempest NetworkBasicOps tests cannot ping from within instances
Bug #1425255 reported by
Nolan Brubaker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Undecided
|
Unassigned | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned | ||
Juno |
Fix Released
|
Low
|
Kevin Carter | ||
Trunk |
Won't Fix
|
Wishlist
|
Evan Callicoat |
Bug Description
The_check_
The invocation was as follows:
root@aio1_
tempest.
root@aio1_
description: | updated |
Changed in openstack-ansible: | |
assignee: | nobody → Nolan Brubaker (nolan-brubaker) |
status: | New → In Progress |
importance: | Undecided → Medium |
milestone: | none → 11.0.0 |
Changed in openstack-ansible: | |
status: | Fix Committed → In Progress |
Changed in openstack-ansible: | |
status: | In Progress → Won't Fix |
importance: | Critical → Wishlist |
milestone: | 11.0.0 → next |
milestone: | next → none |
no longer affects: | openstack-ansible |
Changed in openstack-ansible: | |
status: | New → Fix Released |
To post a comment you must log in.
This has 2 causes:
1 - the VMs can't reach the gateway on AIOs; we can fix this by adding the appropriate address to the br-vlan. This will be addressed in a separate bug.
2 - Packet checksums are not present on packets sent from containers on the AIO, since there is no physical NIC. The utility container will need to have some iptables rules set to mangle the checksums, but I'm not sure if we want to limit this to just tempest runs, or on all utility containers.