Skip to content

Commit

Permalink
Merge branch 'master' into QA-add-service-catalog-retirement
Browse files Browse the repository at this point in the history
  • Loading branch information
qahmed1998 authored Dec 10, 2024
2 parents 9fd00ee + 5d057a6 commit e117c1c
Show file tree
Hide file tree
Showing 4 changed files with 55 additions and 4 deletions.
2 changes: 1 addition & 1 deletion _data/product.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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
5 changes: 2 additions & 3 deletions managing_providers/_topics/automation_management_providers.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -565,5 +565,4 @@ Use the following steps to set a retirement day and time for a service instance:
1. From **Time Delay**, specify a retirement time in the form of the number of months, weeks, days, or hours in the using the arrows.

5. Select a **Retirement Warning** if needed.
6. Click **Save**.

6. Click **Save**.
51 changes: 51 additions & 0 deletions troubleshooting/_topics/providers.md
Original file line number Diff line number Diff line change
@@ -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.
1 change: 1 addition & 0 deletions troubleshooting/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,4 @@
# Troubleshooting

{% include_relative _topics/logging.md %}
{% include_relative _topics/providers.md %}

0 comments on commit e117c1c

Please sign in to comment.