OSDOCS-4564 renaming troubleshooting book and adding known issue

_topic_maps/_topic_map_ms.yml

@@ -149,7 +149,7 @@ Topics:
 #   File: TBD
 ---
 Name: Troubleshooting
-Dir: microshift_support
+Dir: microshift_troubleshooting
 Distros: microshift
 Topics:
 - Name: MicroShift Troubleshooting

microshift_troubleshooting/microshift-troubleshooting.adoc

@@ -1,12 +1,15 @@
 :_content-type: ASSEMBLY
 [id="microshift-troubleshooting"]
-= MicroShift Troubleshooting
+= Check your version and known issues
 include::_attributes/attributes-microshift.adoc[]
 :context: microshift-troubleshooting
 toc::[]
 
-Determine which version of {product-title} you have, find out about known issues, and troubleshoot common problems.
+Determine which version of {product-title} you have, find out about known issues, and troubleshoot problems.
 
 include::modules/microshift-version-cli.adoc[leveloffset=+1]
 
-include::modules/microshift-version-api.adoc[leveloffset=+1]
+include::modules/microshift-version-api.adoc[leveloffset=+1]
+
+include::modules/microshift-ki-cni-iptables-deleted.adoc[leveloffset=+1]
+

modules/microshift-k8s-apis.adoc

@@ -1,12 +1,12 @@
 // Module included in the following assemblies:
 //
-// * microshift_support/microshift-version.adoc
+// * microshift_troubleshooting/microshift-version.adoc
 
 :_content-type: CONCEPT
 [id="microshift-k8s-apis_{context}"]
-= MicroShift Kubernetes APIs
+= {product-title} Kubernetes APIs
 
- {product-title} supports the following standard Kubernetes APIs:
+{product-title} supports the following standard Kubernetes APIs:
 
 NOTE: TABLE IS FOR PLACEMENT ONLY (FPO)
 

modules/microshift-ki-cni-iptables-deleted.adoc

@@ -0,0 +1,80 @@
+// Module included in the following assemblies:
+//
+// * microshift_support/microshift-version.adoc
+
+[id="microshift-ki-cni-iptables-deleted_{context}"]
+= Reloading the firewall deletes iptable rules
+
+OVN-Kubernetes handles incoming NodePort traffic by using iptable rules. When you reload firewall rules with the `firewall-cmd --reload` command, the iptable rules are deleted. This stops the NodePort service traffic and any other host traffic that uses iptable rules.
+
+[id="microshift-ki-cni-iptables-deleted-workaround_{context}"]
+== Restarting the daemon set pod as a workaround
+To troubleshoot this issue, delete the ovnkube-master pod to restart the ovnkube daemon set pod. Restarting the ovnkube daemon set pod will trigger a reconciliation of the iptable rules.
+
+.Prerequisites
+
+* The OpenShift CLI (`oc`) is installed.
+* Access to the cluster as a user with the `cluster-admin` role.
+* A cluster installed on infrastructure configured with the OVN-Kubernetes CNI cluster network provider.
+* The KUBECONFIG environment variable is set.
+
+.Procedure
+
+Run the commands listed in each step that follows to restore the iptable rules.
+
+. Stop the ovn-master application:
++
+[source, terminal]
+----
+$ pod=$(oc get pods -n openshift-ovn-kubernetes | grep ovnkube-master | awk -F " " '{print $1}')
+----
+
+. Delete the ovnkube-master pod:
++
+[source, terminal]
+----
+$ oc -n openshift-ovn-kubernetes delete pod $pod
+----
++
+This command causes the daemon set pod to be automatically restarted, causing a reconciliation of the iptable rules.
+
+. Confirm that the iptables have reconciled by running the following command:
++
+[source, terminal]
+----
+$ sudo iptables-save | grep NODEPORT
+:OVN-KUBE-NODEPORT - [0:0]
+-A PREROUTING -j OVN-KUBE-NODEPORT
+-A OUTPUT -j OVN-KUBE-NODEPORT
+-A OVN-KUBE-NODEPORT -p tcp -m addrtype --dst-type LOCAL -m tcp --dport 30768 -j DNAT --to-destination 10.43.17.173:443
+-A OVN-KUBE-NODEPORT -p tcp -m addrtype --dst-type LOCAL -m tcp --dport 32122 -j DNAT --to-destination 10.43.17.173:80
+----
+
+You can also confirm that a new ovnkube-master pod has been started by running the following command:
+
+[source, terminal]
+----
+$ oc get pods -n openshift-ovn-kubernetes
+----
+The listing of the running pods shows a new ovnkube-master pod name and age. For example:
+
+[cols="5",options="header"]
+|===
+|NAME
+|READY
+|STATUS
+|RESTARTS
+|AGE
+
+|ovnkube-master-kg7ms
+|4/4
+|Running
+|0
+|11s
+
+|ovnkube-node-84gxn
+|1/1
+|Running
+|0
+|4d22h
+|===

modules/microshift-version-api.adoc

@@ -5,12 +5,12 @@
 :_content-type: CONCEPT
 [id="microshift-version-api_{context}"]
 
-= Checking the {product-title} Version via the API
+= Checking the {product-title} version using the API
 
 .Procedure
 
 * To get the version number using the OpenShift CLI (`oc`), view the `kube-public/microshift-version` config map by running the following command:
-
++
 [source,terminal]
 ----
 $ oc get configmap -n kube-public microshift-version -o yaml

modules/microshift-version-cli.adoc

@@ -3,12 +3,12 @@
 // * microshift_support/microshift-version.adoc
 
 [id="microshift-version-cli_{context}"]
-= Checking the {product-title} Version from the command-line
+= Checking the {product-title} version using the command-line interface
 
 .Procedure
 
 * Run the following command to check the version information:
-
++
 [source,terminal]
 ----
 $ microshift version