X-Git-Url: https://gerrit.fd.io/r/gitweb?p=csit.git;a=blobdiff_plain;f=docs%2Freport%2Fvpp_functional_tests%2Fcsit_release_notes.rst;h=25aef29f626bbfc2d5bb318829a8fd5242842d32;hp=25ca27c03f45719b28f5dbfc0856976e6ec20bdb;hb=7e4f0d535fff543b9ec1ef550f3d6bb6068a8160;hpb=f6c04897464c868c034237729bfe738a95d43b25 diff --git a/docs/report/vpp_functional_tests/csit_release_notes.rst b/docs/report/vpp_functional_tests/csit_release_notes.rst index 25ca27c03f..25aef29f62 100644 --- a/docs/report/vpp_functional_tests/csit_release_notes.rst +++ b/docs/report/vpp_functional_tests/csit_release_notes.rst @@ -4,70 +4,41 @@ CSIT Release Notes Changes in CSIT |release| ------------------------- -#. VPP functional test environment changes +#. Optimizations in CSIT functional framework: - - Implemented VAT command history collection for every test case as part of teardown. - - Introduction of Centos7 tests in VIRL environment. + - *VPP install test* - VPP installation has been moved to a separate test in + test suite setup phase to better identify any issues with VPP installation. -#. VPP functional test framework changes - - - Added VAT command history collection for every test case as part of teardown. - -#. Added VPP functional tests - - - IPv4 routed-forwarding with dot1q VLAN sub-interfaces. - - L2BD switched-forwarding with dot1q VLAN sub-interfaces and vhost-user to VM. - - IPv4 routed-forwarding with vhost-user interfaces to VM. - - Vhost-user interface re-connect tests. + - *VPP verify test* - test to check VPP health after installation. Known Issues ------------ -Here is the list of known issues in CSIT |release| for VPP functional tests in VIRL: +List of known issues in CSIT |release| for VPP functional tests in VIRL: +---+-------------------------------------------------+----------+------------------------------------------------------+ -| # | Issue | Jira ID | Description | -+---+-------------------------------------------------+----------+------------------------------------------------------+ +| # | .. centered:: Issue | Jira ID | .. centered:: Description | ++===+=================================================+==========+======================================================+ | 1 | DHCPv4 client: Client responses to DHCPv4 OFFER | CSIT-129 | Client replies with DHCPv4 REQUEST message when | -| | sent with different XID | | received DHCPv4 OFFER message with different (wrong) | +| | sent with different XID. | VPP-99 | received DHCPv4 OFFER message with different (wrong) | | | | | XID. | +---+-------------------------------------------------+----------+------------------------------------------------------+ | 2 | Softwire - MAP-E: Incorrect calculation of IPv6 | CSIT-398 | IPv6 destination address is wrongly calculated in | -| | destination address when IPv4 prefix is 0 | | case that IPv4 prefix is equal to 0 and IPv6 prefix | +| | destination address when IPv4 prefix is 0. | VPP-380 | case that IPv4 prefix is equal to 0 and IPv6 prefix | | | | | is less than 40. | +---+-------------------------------------------------+----------+------------------------------------------------------+ | 3 | Softwire - MAP-E: Map domain is created when | CSIT-399 | Map domain is created in case that the sum of suffix | -| | incorrect parameters provided | | length of IPv4 prefix and PSID length is greater | +| | incorrect parameters provided. | VPP-435 | length of IPv4 prefix and PSID length is greater | | | | | than EA bits length. IPv6 destination address | | | | | contains bits writen with PSID over the EA-bit | | | | | length when IPv4 packet is sent. | +---+-------------------------------------------------+----------+------------------------------------------------------+ | 4 | IPv6 RA: Incorrect IPv6 destination address in | CSIT-409 | Wrong IPv6 destination address (ff02::1) is used in | -| | response to ICMPv6 Router Solicitation | | ICMPv6 Router Advertisement packet sent as a | +| | response to ICMPv6 Router Solicitation. | VPP-406 | ICMPv6 Router Advertisement packet sent as a | | | | | response to received ICMPv6 Router Solicitation | | | | | packet. | +---+-------------------------------------------------+----------+------------------------------------------------------+ -| 5 | IPFIX: IPv6_src key name reported instead of | CSIT-402 | The report contains IPv6_src key name instead of | -| | IPv6_dst | | IPv6_dst when classify session is configured with | -| | | | IPv6 destination address. Anyhow the correct IPv6 | -| | | | destination address is reported. | -+---+-------------------------------------------------+----------+------------------------------------------------------+ -| 6 | IPv4 + VLAN: Processing of tagged frame doesn't | CSIT-564 | Dot1q tagged packets are thrown away in case of IPv4 | -| | work with virtio driver | | routing on interface binded to virtio driver. Issue | -| | | | with VIRL test simulation environment | -+---+-------------------------------------------------+----------+------------------------------------------------------+ -| 7 | Vhost-user: QEMU reconnect doesn't work | CSIT-565 | Using QEMU 2.5.0 that does not support vhost-user | -| | | | reconnect. It requires moving CSIT VIRL environment | +| 5 | Vhost-user: QEMU reconnect does not work. | CSIT-565 | Used QEMU 2.5.0 does not support vhost-user | +| | | | reconnect. Requires upgrading CSIT VIRL environment | | | | | to QEMU 2.7.0. | +---+-------------------------------------------------+----------+------------------------------------------------------+ -| 8 | Centos7: LISP and VXLAN sporadic test failures | CSIT-566 | Observing sporadic crashes of DUT1 VM during LISP | -| | | | and VXLAN test executions, what leads to failure of | -| | | | all other tests in the suite. NOTE: After upgrading | -| | | | one of the VIRL servers host from Ubuntu14.04 to | -| | | | 16.04, DUT1 VM stops crashing, but tests keep | -| | | | failing sporadically 1-in-100. Possible root cause | -| | | | identified - unexpected IPv6 RA packets upsetting | -| | | | some test component. Currently suspecting | -| | | | environment or CSIT issue, but can not exclude VPP, | -| | | | further troubleshooting in progress. | -+---+-------------------------------------------------+----------+------------------------------------------------------+