From 7edb6cd996ec6924d77af72a081f6de963f7a2af Mon Sep 17 00:00:00 2001 From: mrpa Date: Wed, 22 Jul 2020 21:02:49 +0200 Subject: Updated the Known Issues Chapter, reordering issues per component etc. Change-Id: Idd94904936583cbdffa2ae6491a881453a77e7e1 Signed-off-by: mrpa --- .../doc/known_bugs_and_limitations.xml | 107 ++++++++++----------- 1 file changed, 51 insertions(+), 56 deletions(-) (limited to 'doc') diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml index ef184d8..a46289e 100644 --- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml +++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml @@ -7,20 +7,10 @@ This chapter lists the known general issues and limitations that affect the current release. - The section further down is generated from JIRA with - gen_known_issues.py, but that script is HARDCODED with affectedversion - "EL7_3-virtualization" and needs to be adapted when a release info for - another ENFV Access version changes. - - CPDX-3292The Factory Reset button in the uCPE - Manager is experimental as of the 2.2.2 release. - - - - ELCCR-119Multiple uCPE devices behind a firewall - or a gateway connecting with Call-Home are not supported. + LXCR-9904NFV Access cannot be installed on USB + storage devices. @@ -29,30 +19,30 @@ the uCPE Manager. + + LXCR-9799NFV Access can boot from the wrong + partition if two HDDs are attached to the same device, this must be + avoided. + + ELCCR-349If the uCPE Manager has not been successfully installed originally or if the installed resources (files, users, services, databases, environment variables, etc.) have been - manually changed/removed, the uninstallation may fail and some resources will - have to be removed manually. - - - - ELCCR-349Recovery in case of a failed uCPE Manager - uninstallation is not implemented. In case of a failure the resources have to - be removed manually. + manually changed/removed, the uninstallation may fail and some resources + will have to be removed manually. - ELCCR-454Only the default database is supported, - any requests for alternative databases are custom adaptations not tested - by Enea. + ELCCR-349Recovery in case of a failed uCPE + Manager uninstallation is not implemented. In case of a failure the + resources have to be removed manually. - ELCCR-474Deleting VNF instances with flows - configured on the OVS bridges can be done only after removing the - flows. + ELCCR-454 For the uCPE Manager, only the default + database is supported, any requests for alternative databases are custom + adaptations not tested by Enea. @@ -61,6 +51,28 @@ the next upload to work. + + ELCCR-577If a uCPEM is restored from a backup + made on an older release version than 2.2.3, VNFs cannot be instantiated + from the GUI. + + + + CPDX-3292The Factory Reset button in the uCPE + Manager is experimental as of the 2.2.2 release. + + + + ELCCR-119Multiple uCPE devices behind a firewall + or a gateway connecting with Call-Home are not supported. + + + + ELCCR-474Deleting VNF instances with flows + configured on the OVS bridges can be done only after removing the + flows. + + ELCCR-572Sometimes when selecting and deleting more than one VNF instance simultaneously, an error message might be @@ -73,18 +85,12 @@ uCPE Manager. - - LXCR-9799NFV Access can boot from the wrong - partition if two HDDs are attached to the same device, this must be - avoided. - - LXCR-9853The WAN interface of uCPE device needs to be connected to a network with at least a router/gateway installed for next-hop communication. - + LXCR-9853When configuring a VNF with WAN and Management access on different interfaces, the user has to ensure VNF's @@ -92,32 +98,21 @@ traffic egress-ing the VNF. - - LXCR-9904NFV Access cannot be installed on USB - storage devices. - - - - ELCCR-577If a uCPEM is restored from a backup made - on an older release version than 2.2.3, VNFs cannot be instantiated from the GUI. - - - LXCR-9992Due to the way VFIO works, there are - certain limitations regarding which devices can be used with VFIO. Mainly, it - comes down to how IOMMU groups work. Any Virtual Function device can - be used with VFIO on its own, however, physical devices will require either - all ports to be bound to VFIO, or only some of them bound while others not - bound to anything at all. + certain limitations regarding which devices can be used with VFIO. + Mainly, it comes down to how IOMMU groups work. Any Virtual Function + device can be used with VFIO on its own, however, physical devices will + require either all ports to be bound to VFIO, or only some of them bound + while others not bound to anything at all. If UEFI secure boot is enabled, the Linux kernel may disallow the - use of UIO on the system. Therefore, devices intended for use by the DPDK should be - bound to the vfio-pci kernel module rather than the - igb_uio. - - - + use of UIO on the system. Therefore, devices intended for use by the + DPDK should be bound to the vfio-pci kernel module + rather than the igb_uio. + + + STCR-6224The Automation Framework and Test Harness do not support multiple custom scripts uploaded to the device at the same time. @@ -137,4 +132,4 @@ - + \ No newline at end of file -- cgit v1.2.3-54-g00ecf