Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32968 has been resolved.

Verified on 6.9.5 Snap2.

Verification points:

1- Check the hammer logging command and found the pulp3 entry there
# hammer admin logging --list

-----------|------------------------------------------|--------------------------------------------------
COMPONENT  | AUTO-DETECTED BY EXISTENCE OF            | DESTINATIONS                                     
-----------|------------------------------------------|--------------------------------------------------
.............................       
pulpcore   | /etc/pulp/settings.py                    | syslog                 
...............................

2- Check the verbosity of logging in the /etc/pulp/settings.py  and log_level was INFO

LOGGING = {
    "dynaconf_merge": True,
    "loggers": {
        '': {
            'handlers': ['console'],
            'level': 'INFO',
        }
    }
}


3- Increase the pulp3 log level

# hammer admin logging -c pulpcore -d
# foreman-maintain service restart


4- Check the verbosity of logging in the /etc/pulp/settings.py  and log_level was DEBUG

LOGGING = {
    "dynaconf_merge": True,
    "loggers": {
        '': {
            'handlers': ['console'],
            'level': 'DEBUG',
        }
    }
}

5- Reduce the pulp3 log level and it has changed to info

#hammer admin logging -c pulpcore --level-production

LOGGING = {
    "dynaconf_merge": True,
    "loggers": {
        '': {
            'handlers': ['console'],
            'level': 'INFO',
        }
    }
}

6- Verified fixed in version.

# rpm -qa|grep -e tfm-rubygem-hammer_cli_foreman_admin -e foreman-installer
foreman-installer-2.3.1.18-1.el7sat.noarch
....
tfm-rubygem-hammer_cli_foreman_admin-1.0.0-1.el7sat.noarch

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite Tools 6.9.5 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:3386