blob: f51fe11c6134bff6953662d39f5e8e7a28bdce19 (
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
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<chapter id="troubleshooting_guide">
<title>Troubleshooting Guide</title>
<para>The following are best practices and possible solutions to problems
that may occur during operation:</para>
<itemizedlist>
<listitem>
<para>All the Playbooks have to be run from the root directory of the
Test Harness (TH) to avoid failures such as "File not found!", since the
paths to the required configuration files are hardcoded into the
Playbooks.</para>
</listitem>
<listitem>
<para>If the <literal>setup_env.sh</literal> fails, for debugging remove
<literal>&> /dev/null</literal> from the failed command. The
output of the command will be printed, and will not be redirected to
<literal>/dev/null</literal> anymore.</para>
</listitem>
<listitem>
<para>When setting up the uCPE Manager to be used by the TH through the
<literal>setupuCPEManager.yml</literal> Playbook, if the uCPE
username/password/host are incorrect or are missing, all the Sample test
cases will fail. If the FTP username/password/port are wrong or are
missing, the tests that require file transfer to the uCPE Manager will
fail.</para>
</listitem>
<listitem>
<para>Ansible logs are not written into the
<literal>log/ansible.log</literal> file when the
<literal>stdout_callback</literal> is set to
<literal>selective</literal> in the <literal>ansible.cfg</literal> file.
For debugging, check the python logs from the
<literal>log/debug.log</literal> file or change the
<literal>stdout_callback</literal> to <literal>debug</literal> and rerun
the test.</para>
</listitem>
</itemizedlist>
</chapter>
|
