Reviewed: https://review.opendev.org/704940
Committed:
https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=f2b60545a585169f4d17653c024320f499cc8026
Submitter: Zuul
Branch: master
commit f2b60545a585169f4d17653c024320f499cc8026
Author: Eduardo Olivares <eoliv...@redhat.com>
Date: Thu Jan 30 09:37:22 2020 +0100
Adding pattern to check_remote_connectivity function
Ping messages sent by this function will include a pattern of bytes
that are repeated until message size is completed.
Input format required is a string with hex digits.
This is useful when these messages are captured, in order to identify
and differentiate clearly messages from different tests.
It can be used to validate that traffic routing is not affected by
packet data as well.
Closes-Bug: #1861397
Change-Id: Ib94518597bdf3d9f3049643d3242db632769de6b
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1861397
Title:
Needed mechanism to differentiate pings sent in tempest tests
Status in neutron:
Fix Released
Bug description:
Tempest Neutron plugin includes function check_remote_connectivity. It sends
ping messages from VM instances to validate connectivity.
There could be problems to correctly identify/filter those messages when
several tests are running in parallel.
One simple way to be able to filter those messages is using ping
option "-p <pattern>". That pattern is included in the ping messages
and can be filtered out when packets are captured.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1861397/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
