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.

Description of problem:

When called via a python script the new version of yum in 6.7
is returning incorrect pkgs.available some packages that are
in the repo are not returned as part of the list.


Version-Release number of selected component (if applicable):
yum-3.2.29-69

How reproducible:

from yum import YumBase
yumbase = YumBase()
yumbase.setCacheDir()
yumbase.doLock()
yumbase._getTs()
yumbase._getRpmDB()
yumbase._getRepos(doSetup=True)
yumbase._getSacks()
pkgs = yumbase.doPackageLists(patterns=[])
for pkg in sorted(pkgs.available):
    if pkg.name.startswith('openssh'):
        pkg.name


Steps to Reproduce:

Run the above python snippet in a python terminal.


Actual results:

'openssh-askpass'
'openssh-ldap'


Expected results:

'openssh'
'openssh-clients'
'openssh-server'
'openssh-askpass'
'openssh-ldap'


Additional info:

This will break any scripts that use the yum python modules
directly as the results being returned are incorrect.

Hello Andrew,
according to my testing the result is the same as for yum-3.2.29-60.el6.noarch from RHEL-6.6 and yum-3.2.29-40.el6.noarch from RHEL-6.5. Btw, it matches the output of the
  yum list available openssh\* 
command (there is a missing 'print' at the last line of the reproducer in #c0)

Could you please provide more evidence, e.g. yum version that was working the way you expected? Thank you.

We can't move forward on this report unless the requested information is provided, so I'm closing this.