Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-140738

Automatically detect AAP user in containerised environments

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-8.10, rhel-9.2.0, rhel-9.6, rhel-10.0, rhel-10.1, rhel-9.7, rhel-9.8, rhel-10.2, rhel-9.4.0
    • sos
    • None
    • None
    • Moderate
    • rhel-sst-cee-supportability
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      Sos report needed to specify AAP user to collect anything in aap_contaierized plugin. Omitting this, no AAP specific data are collected at all.

      We should provide a heuristic for detecting the user based on running processes.

      In fact, we need to ensure sos #4150 works fine.

      What is the impact of this issue to you?

      Lack of important data in sosreport.

      Please provide the package NVR for which the bug is seen:

      sos-4.10.1 or older

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1. on a containerized deployment of AAP, run "sos report --batch"

      Expected results

      In 99% cases, aap_containerized plugin should be collected.

      Actual results

      Error "Username is mandatory to collect AAP containerized setup logs" hit. (since 4.10.2, the error is "Unable to determine AAP username, terminating plugin.").

              rhn-support-jjansky Jan Jansky
              rhn-support-pmoravec Pavel Moravec
              se cee-supportability se cee-supportability
              Pavel Moravec Pavel Moravec
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: