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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
<?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 general issues and limitations 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>
<listitem>
<para><remark>ELCCR-119</remark>Multiple uCPE devices behind a firewall
or a gateway connecting with Call-Home are not supported.</para>
</listitem>
<listitem>
<para><remark>ELCCR-319</remark>After a successful installation or
upgrade, it takes about 2 minutes until the device is accessible from
the uCPE Manager.</para>
</listitem>
<listitem>
<para><remark>ELCCR-349</remark>If 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.</para>
</listitem>
<listitem>
<para><remark>ELCCR-349</remark>Recovery in case of a failed uCPE Manager
uninstallation is not implemented. In case of a failure the resources have to
be removed manually.</para>
</listitem>
<listitem>
<para><remark>ELCCR-454</remark>Only the default database is supported,
any requests for alternative databases are custom adaptations not tested
by Enea.</para>
</listitem>
<listitem>
<para><remark>ELCCR-474</remark>Deleting VNF instances with flows
configured on the OVS bridges can be done only after removing the
flows.</para>
</listitem>
<listitem>
<para><remark>ELCCR-527</remark>Cancelling a file upload in the uCPE
Manager will require the user to close and reopen the upload window for
the next upload to work.</para>
</listitem>
<listitem>
<para><remark>ELCCR-572</remark>Sometimes when selecting and deleting
more than one VNF instance simultaneously, an error message might be
triggered, even if the delete operation succeeds.</para>
</listitem>
<listitem>
<para><remark>LXCR-????</remark>The Call Home functionality does not
support having multiple interfaces/routes that go from the device to the
uCPE Manager.</para>
</listitem>
<listitem>
<para><remark>LXCR-9799</remark>NFV Access can boot from the wrong
partition if two HDDs are attached to the same device, this must be
avoided.</para>
</listitem>
<listitem>
<para><remark>LXCR-9853</remark>The WAN interface of uCPE device needs
to be connected to a network with at least a router/gateway installed
for next-hop communication.</para>
</listitem>
<listitem>
<para><remark>LXCR-9853</remark>When configuring a VNF with WAN and
Management access on different interfaces, the user has to ensure VNF's
virtual interfaces are configured so that proper routes are used for
traffic egress-ing the VNF.</para>
</listitem>
<listitem>
<para><remark>LXCR-9904</remark>NFV Access cannot be installed on USB
storage devices.</para>
</listitem>
<listitem condition="hidden">
<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>
|
