docs: document the rhel fips known issue

docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/fips.md

@@ -103,6 +103,16 @@ image with.
 
 <TabItem label="Red Hat Enterprise Linux" value="rhel">
 
+:::warning
+
+When you create a cluster with an Edge host that operates the FIPS-compliant RHEL Operating System (OS), you may
+encounter an error where the `systemd-resolved.service` service enters the **failed** state. This prevents the
+nameserver from being configured, which will result in cluster deployment failure. Refer to
+[TroubleShooting](../../../../troubleshooting/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a
+workaround.
+
+:::
+
 5. Change into the **rhel-fips** directory.
 
 6. In the file **Dockerfile**, provide your RHEL subscription username and password.

docs/docs-content/release-notes/release-notes.md

@@ -101,6 +101,12 @@ features and improvements.
   successful. For more information about key enrollment, refer to
   [Enroll Trusted Boot Keys in Edge Host](../clusters/edge/trusted-boot/deployment-day2/install.md#enroll-secure-boot-keys-into-edge-device).
 
+- Edge hosts with FIPS-compliant RHEL Operating System (OS) distribution may encounter the error where the
+  `systemd-resolved.service` service enters the **failed** state. This prevents the nameserver from being configured,
+  which will result in cluster deployment failure. Refer to
+  [TroubleShooting](../../../../troubleshooting/edge.md#scenario---systemd-resolvedservice-enters-failed-state) for a
+  workaround.
+
 ### Edge
 
 #### Features

docs/docs-content/troubleshooting/edge.md

@@ -14,7 +14,7 @@ The following are common scenarios that you may encounter when using Edge.
 
 If you need to override or reconfigure the read-only file system, you can do so using the following steps.
 
-## Debug Steps
+### Debug Steps
 
 1. Power on the Edge host.
 
@@ -136,3 +136,25 @@ issues or not being available. Use the following steps to troubleshoot and resol
 
 7. If you continue to encounter issues, contact our support team by emailing
    [[email protected]](mailto:[email protected]) so that we can provide you with further guidance.
+
+## Scenario - systemd-resolved.service Enters Failed State
+
+When you create a cluster with an Edge host that operates the FIPS-compliant RHEL Operating System (OS), you may
+encounter an error where the `systemd-resolved.service` process enters the **failed** state. This prevents the
+nameserver from being configured, which will result in cluster deployment failure.
+
+### Debug Steps
+
+1. Establish an SSH connection to the Edge host. A
+
+   Alternatively, press the keys **Fn + Ctrl +Cmd + F1** on a keyboard that is connected to the Edge host to log in to
+   the terminal. If you are on Windows, press **Fn + Ctrl + Alt + F1**.
+
+2. Issue the following command.
+
+   ```shell
+   chmod a+rwxt /var/tmp
+   systemctl enable --now systemd-resolved.service
+   ```
+
+   This will start the `systemd-resolved.service` process and move the cluster creation process forward.