From 1186fde221a8c0becec7dfbf8fdb51d67268cc4c Mon Sep 17 00:00:00 2001
From: Adam Grare <adam@grare.com>
Date: Wed, 4 Dec 2024 15:12:51 -0500
Subject: [PATCH 1/2] Add instructions on enabling VMware Request Debugging

---
 troubleshooting/_topics/providers.md | 51 ++++++++++++++++++++++++++++
 troubleshooting/index.md             |  1 +
 2 files changed, 52 insertions(+)
 create mode 100644 troubleshooting/_topics/providers.md

diff --git a/troubleshooting/_topics/providers.md b/troubleshooting/_topics/providers.md
new file mode 100644
index 000000000..97121ec0f
--- /dev/null
+++ b/troubleshooting/_topics/providers.md
@@ -0,0 +1,51 @@
+## Providers
+
+### VMware vCenter Provider
+
+If you are having issues with a VMware provider you can enable extensive debug
+logging which will log the raw XML payloads for all requests and responses between
+the vCenter and {{ site.data.product.title_short }}.
+
+There are two settings that you have to enable in Advanced Settings
+1. log.level_vim must be set to debug
+2. ems.ems_vmware.debug_vim_requests must be set to true
+
+With these two settings enabled you will see the full XML payloads in the vim log,
+here is a sample Login action:
+```
+[----] D, [2024-12-04T12:31:51.307304#554036:97f4] DEBUG -- vim: <?xml version='1.0' ?>
+<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
+  <env:Header />
+  <env:Body>
+    <n1:Login xmlns:n1="urn:vim25">
+      <n1:_this type="SessionManager">SessionManager</n1:_this>
+      <n1:userName>user</n1:userName>
+      <n1:password>pass</n1:password>
+    </n1:Login>
+  </env:Body>
+</env:Envelope>
+[----] D, [2024-12-04T12:31:51.308114#554036:97f4] DEBUG -- vim: <?xml version="1.0" encoding="UTF-8"?>
+<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns: xsi="http://www.w3.org/2001/XMLSchema-instance">
+  <soapenv:Body>
+    <LoginResponse xmlns="urn:vim25">
+      <returnval>
+        <key>53e7183f-4db3-4e02-b62d-840b9a47fc31</key>
+        <userName>user</userName>
+        <fullName>user</fullName>
+        <loginTime>2024-12-04T17:31:51.307621525Z</loginTime>
+        <lastActiveTime>2024-12-04T12:31:51.307628585-05:00</lastActiveTime>
+        <locale>en_US</locale>
+        <messageLocale>en_US</messageLocale>
+        <extensionSession>false</extensionSession>
+        <ipAddress>127.0.0.1</ipAddress>
+        <userAgent>HTTPClient/1.0 (2.8.3, ruby 3.3.5 (2024-09-03))</userAgent>
+        <callCount>1</callCount>
+      </returnval>
+    </LoginResponse>
+  </soapenv:Body>
+</soapenv:Envelope>
+
+```
+
+Depending on the payloads you are working with, they might overflow the journald `LineMax` and be cut off.
+If this is the case you can edit the `/etc/systemd/journald.conf` file and adjust the `LineMax` setting appropriately.
diff --git a/troubleshooting/index.md b/troubleshooting/index.md
index cda0bfdd6..0820a8e3e 100644
--- a/troubleshooting/index.md
+++ b/troubleshooting/index.md
@@ -4,3 +4,4 @@
 # Troubleshooting
 
 {% include_relative _topics/logging.md %}
+{% include_relative _topics/providers.md %}

From 065ce6b7a5fa3cc7b14d1120b194b02467c8f3cf Mon Sep 17 00:00:00 2001
From: Jason Frey <fryguy9@gmail.com>
Date: Tue, 10 Dec 2024 11:54:36 -0500
Subject: [PATCH 2/2] Fix issue with invalid yaml

The backtick is not a valid starting char in YAML, but also we shouldn't
use formatting in the YAML, because it won't be redenered properly
anyway.
---
 _data/product.yml                                             | 2 +-
 managing_providers/_topics/automation_management_providers.md | 3 +--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/_data/product.yml b/_data/product.yml
index 717f75fe8..f0a4e3ede 100644
--- a/_data/product.yml
+++ b/_data/product.yml
@@ -12,5 +12,5 @@ operator_directory: https://github.com/ManageIQ/manageiq-pods/tree/master/manage
 operator_namespace: manageiq.org
 workflow_service_account: manageiq-default
 import_opentofu: runuser --login manageiq --command 'podman --root=/var/www/miq/vmdb/data/containers/storage image load --input /tmp/<OpenTofu_image>'
-opentofu_image_name: `<OpenTofu_image>`
+opentofu_image_name: <OpenTofu_image>
 container_image: docker.io/manageiq/opentofu-runner:latest
diff --git a/managing_providers/_topics/automation_management_providers.md b/managing_providers/_topics/automation_management_providers.md
index a8aa72f9f..166590dee 100644
--- a/managing_providers/_topics/automation_management_providers.md
+++ b/managing_providers/_topics/automation_management_providers.md
@@ -384,7 +384,7 @@ Use the following command to import the OpenTofu image on your appliance server.
 {{ site.data.product.import_opentofu }}
 ```
 
-Where {{ site.data.product.opentofu_image_name }} is the name of your OpenTofu image.
+Where `{{ site.data.product.opentofu_image_name }}` is the name of your OpenTofu image.
 
 You also need to set the docker image name in advanced settings before enabling the server role. Navigate to the **Settings** > **Application Settings** in {{ site.data.product.title_short }} UI and set the value for `workers/worker_base/opentofu_worker/container_image` field.
 
@@ -538,4 +538,3 @@ Use the following steps to run the Terraform Template.
 {{ site.data.product.title_short }} takes you to the *Requests queue* page and displays the status of the job.
 
 The service item details can be viewed when you navigate to **Services** > **My Services in {{ site.data.product.title_short }}**.
-