[aap_containerized] Collect same commands like other AAP plugins

[pmoravec]

Let collect same command outputs from containerized deployments, likewise we do collect from RPM based deployments in all other aap_* plugins today.

Closes: #4168
Relevant-to: RHEL-129225

---

Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

• Is the commit message split over multiple lines and hard-wrapped at 72 characters?
• Is the subject and message clear and concise?
• Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
• Does the commit contain a Signed-off-by: First Lastname [email protected]?
• Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?
• Are all passwords or private data gathered by this PR obfuscated?

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo dnf install -y 'dnf*-command(copr)'
• dnf copr enable packit/sosreport-sos-4168
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[snagoor]

@pmoravec at first glance this looks perfect. I will test it on multi-host and single host deployment as well.

[snagoor]

Hello @pmoravec this works as expected. Only change is to mask the PASSWORD and SECRET collected with aap-gateway-manage print_settings command. Similar to https://github.com/sosreport/sos/blob/main/sos/report/plugins/aap_gateway.py#L60-L72

[pmoravec]

Good point. Obfuscation added, tested locally it works:

sos_commands/aap_containerized/automation-gateway/aap-gateway-manage_print_settings:

DATABASES                                = {'default': {'PASSWORD': '**********', 'ENGINE': 'django.db.backends.postgresql', 'NAME': 'gateway', ..}}
..
EMAIL_HOST_PASSWORD                      = '**********'
..
SECRET_KEY                               = b'**********'

[TurboTurtle]

We have probably discussed this in the past, but just for completeness sake, does runas not function here to avoid the embedded su calls?

[pmoravec]

I dont recall the original reason, but when I tried to use runas=username now, I am getting hung processes like:

aap       152503  0.0  0.0   3068  1664 pts/1    S    19:44   0:00 timeout 300s podman exec -it automation-controller-task bash -c awx-manage check_license --data
aap       152505  0.0  0.3 2023996 53964 pts/1   Sl   19:44   0:00 podman exec -it automation-controller-task bash -c awx-manage check_license --data
~~~

hung for minutes (while manual execution of the same takes a fraction of second).

[TurboTurtle]

LGTM up to the comment about runas vs su. I'm fine if it goes in as written if there are outstanding issues preventing the use of runas, which I believe there may be.

[pmoravec]

Worth commenting the need of su - approach as a comment in the code?

[TurboTurtle]

Couldn't hurt to add a comment or TODO on investigating how to get this working without the embedded su -.

[pmoravec]

I spent some time trying to identify the cause but without a luck. So I added just the explanation to the code.