RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

repoquery claims that "glibc32" is required for any x86_64 package.

python3-dnf-plugins-core-4.0.2-1.el8.noarch
python3-libdnf-0.22.3-1.el8.x86_64
dnf-data-4.0.9-1.el8.noarch
dnf-4.0.9-1.el8.noarch
dnf-plugin-subscription-manager-1.23.8-2.el8.x86_64
dnf-utils-4.0.2-1.el8.noarch
python3-dnf-4.0.9-1.el8.noarch
dnf-plugins-core-4.0.2-1.el8.noarch
libdnf-0.22.3-1.el8.x86_64

How reproducible: always

Let's take package bc. It is binary and has very small number of dependencies.

# repoquery --requires  bc.x86_64
/bin/sh
/sbin/install-info
libc.so.6(GLIBC_2.14)(64bit)
libncurses.so.6()(64bit)
libreadline.so.7()(64bit)
libtinfo.so.6()(64bit)
rtld(GNU_HASH)

Now add:
--resolve
When used with --requires, resolve capabilities to originating packages.

# repoquery --requires --resolve  bc.x86_64
bash-0:4.4.19-6.el8.x86_64
glibc-0:2.28-34.el8.i686          <<<-------------- this
glibc-0:2.28-34.el8.x86_64
info-0:6.5-4.el8.x86_64
ncurses-libs-0:6.1-5.20180224.el8.x86_64
readline-0:7.0-10.el8.x86_64

# repoquery --requires --resolve --recursive  bc.x86_64 | grep i686
glibc-0:2.28-34.el8.i686
pcre2-0:10.31-11.el8.i686

It behaves according to expectations.
Some of the requires/provides are noarch.

You're also probably running tests in build environment.
AFAIK glibc32 is for build system / build roots only and should never appear in any test environment.