Add notes on fixing broken ONL installs, and spelling fixes
Change-Id: I7ebe12fc579347e5f9aea706cc9f7ce029bcec5e
diff --git a/dict.txt b/dict.txt
index 91da925..4d21ab3 100644
--- a/dict.txt
+++ b/dict.txt
@@ -45,6 +45,7 @@
ethernet
gerrit
gNMI
+iface
iPXE
jjb
kubectl
@@ -58,10 +59,14 @@
nVME
omec
onos
+opencord
patchset
+pcap
+pcaps
pfcp
preseed
provisioner
+ptf
pxeboot
qsfp
rackmount
@@ -69,16 +74,20 @@
repo
repos
repository
+rscript
runtime
+spgw
subcomponent
subnet
tAC
telegraf
tfvars
tost
+udp
upf
virtualenv
vpn
+webhooks
webpage
webserver
yaml
diff --git a/edge_deployment/troubleshooting.rst b/edge_deployment/troubleshooting.rst
index b45c76f..6df4549 100644
--- a/edge_deployment/troubleshooting.rst
+++ b/edge_deployment/troubleshooting.rst
@@ -140,3 +140,18 @@
LINK CHASSIS ID SYSTEM NAME CAPS PORT ID PORT DESCRIPTION
eno1 10:4f:58:e7:d5:60 Aruba-2540-24…PP ..b........ 10 10
eno2 10:4f:58:e7:d5:60 Aruba-2540-24…PP ..b........ 1 1
+
+
+Problems with ONIE Installation
+-------------------------------
+
+Can't reboot into ONL, loops on ONIE installer mode
+---------------------------------------------------
+
+Sometimes an ONL installation is incomplete or problematic, and reinstalling it
+doesn't result in a working system.
+
+If this is the case, reboot into ONIE Rescue mode and use ``parted`` to delete
+all the ``ONL-`` prefixed partitions, then reinstall with an ``onie-installer``
+image.
+
diff --git a/testing/pdp_testing.rst b/testing/pdp_testing.rst
index d034ca2..10108a6 100644
--- a/testing/pdp_testing.rst
+++ b/testing/pdp_testing.rst
@@ -18,7 +18,7 @@
Test Scenarios
-------------------
-fabric-tna is a P4 program based on the Tofino Native Architracture(TNA). Currently 4 profiles are supported for
+fabric-tna is a P4 program based on the Tofino Native Architecture(TNA). Currently 4 profiles are supported for
compiling the fabric-tna P4 program.
1. fabric
diff --git a/testing/sdcore_testing.rst b/testing/sdcore_testing.rst
index 535a1ad..22b5f3a 100644
--- a/testing/sdcore_testing.rst
+++ b/testing/sdcore_testing.rst
@@ -138,7 +138,7 @@
1. `omec_deploy_dev`: this job executes the scalability test suite.
2. `robotframework-test_dev`: this job is similar to `ng40-test_dev` with the
exception that instead of directly executing NG40 commands it calls robot
- framework to exectue the test cases and publishes the test results using
+ framework to execute the test cases and publishes the test results using
`RobotPublisher` Jenkins plugin. The robot results will also be copied to
the upstream job and published there.
3. `archive-artifacts_dev`: this job collects and uploads k8s and container logs.