summaryrefslogtreecommitdiffstats
path: root/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml
blob: e2d338e85e85b0e23ff56b5d83d90e80e9d5b954 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<chapter id="bugs-limitations">
  <title>Known Issues and Limitations in this Release</title>

  <para>This chapter lists the known issues that affect the current
  release.</para>

  <para><remark>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.</remark></para>

  <itemizedlist>
    <para><emphasis role="bold">Enea uCPE Manager</emphasis></para>

    <listitem>
      <para><remark>ELCCR-99</remark>The uCPE Manager fails to onboard renamed
      VNF bundles downloaded to the same repo.</para>
    </listitem>

    <listitem>
      <para><remark>ELCCR-119</remark>No support is provided for multiple uCPE
      devices behind a firewall or gateway connecting Call Home to the uCPE
      Manager (running outside the local network).</para>
    </listitem>

    <listitem>
      <para><remark>ELEMCR-1690</remark>There is no keep-alive mechanism in
      place for the Device Call Home Connection.</para>
    </listitem>

    <listitem>
      <para><remark>LXCR-9274</remark>The Call Home functionality does not support
       having multiple interfaces/routes that go from the device to the
       uCPE Manager. The IP/DNS address might need to be changed to the
       established socket IP.</para>
    </listitem>

    <listitem>
      <para><remark>ELCCR-256</remark>The uCPE Manager cannot manage VNFs which
      contain special characters in their name.</para>
    </listitem>

    <listitem>
      <para><remark>LXCR-9513</remark>When using In-Band Management on standard
      interfaces (DPDK disabled), stopping and restarting a VNF is not supported.
      To perform a VNF restart, it has to be deleted and reinstantiated.</para>
    </listitem>

    <listitem>
      <para><remark>ELCCR-276</remark>The uCPE Manager does not prevent a user 
        from creating multiple <literal>communication</literal> bridges assigned 
        to the same physical port. Although this is an invalid configuration and 
        OVS itself will not accept it, the configuration screens will incorrectly 
        show that such a configuration is in effect. The user should take care 
        while assigning a physical port to a communications bridge to ensure that 
        the port being assigned has not already been assigned to another bridge.</para>
    </listitem>
  </itemizedlist>

  <para><remark>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.</remark></para>

  <itemizedlist condition="hidden">
    <listitem>
      <para><emphasis role="bold">PDF navigation</emphasis>: When using links
      to open other PDFs, or jump to another place in the same PDF, jumping
      back sometimes fails. This has been observed when opening a PDF in Adobe
      Reader, inside a browser with PDF add-on, as well as when the browser is
      configured to open PDF files in an external PDF reader. As a workaround,
      open the HTML version of the document.<remark>LXCR-3283</remark></para>
    </listitem>
  </itemizedlist>

  <!-- The file with a section below is autocreated by make init  -->

  <!-- <xi:include href="jiraissues_generated.xml"
              xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
</chapter>