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.
Bug 1718201 - conflicts between "postgresql" module and PGDG repo packages
Summary: conflicts between "postgresql" module and PGDG repo packages
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.0
Hardware: x86_64
OS: Linux
Target Milestone: rc
: 8.0
Assignee: Jaroslav Mracek
QA Contact: BaseOS QE Security Team
Depends On:
TreeView+ depends on / blocked
Reported: 2019-06-07 08:47 UTC by ioguix
Modified: 2023-03-24 14:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-11 08:32:56 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4771961 0 None None None 2020-01-28 12:01:26 UTC

Description ioguix 2019-06-07 08:47:51 UTC
yum/dnf refuse to find/install many packages from PGDG repository on RHEL8

After installing the PGDG repository from yum.postgresql.org on RHEL8, I expect the following command to install PostgreSQL 11 and its dependencies:

  [root@localhost ~]# yum install postgresql11 postgresql11-server \
  Updating Subscription Management repositories. 
  Last metadata expiration check: 0:00:49 ago on Fri May 17 16:33:48 2019.
  No match for argument: postgresql11 
  No match for argument: postgresql11-server 
  No match for argument: postgresql11-contrib 
  Error: Unable to find a match 

The package exists from the repository, eg:

  [root@localhost ~]# yum --quiet repoquery --repo pgdg11 postgresql11-server*

Even searching for the package doesn't work:

  [root@localhost ~]# yum search postgresql11-server
  Updating Subscription Management repositories.
  Last metadata expiration check: 0:23:08 ago on Fri May 17 00:23:20 2019.
  No matches found.

A workaround to this issue is currently to disable the "postgresql" module from appstream:

  [root@localhost ~]# yum -qy module enable postgresql
  [root@localhost ~]# yum -q info postgresql11-server|grep ^Name
  Error: No matching Packages to list
  [root@localhost ~]# yum -qy module disable postgresql
  [root@localhost ~]# yum -q info postgresql11-server|grep ^Name
  Name         : postgresql11-server

The only dependency who match a package in appsteam is on "libpq.so.5". This lib provided by package "postgresql11-libs" from the PGDG repo.

Behavior is quite surprising. I suppose the package manager should provide a better error message /advice if there is some conflicts or dependency issues or if it is not able to make a choice between two packages.

Moreover, is it something to be fixed on "postgresql" module side or in PGDG repo side? How?


Comment 1 Jaroslav Mracek 2019-06-11 08:32:56 UTC
I believe that you experience of consequence of modular filtering (not a bug). Please see https://github.com/rpm-software-management/dnf/blob/master/doc/modularity.rst.

When module postgresql is enabled or default, all packages that has the same name with modular packages are excluded from all repositories. To disable modular filtering for certain repository, just add "module_hotfixes=true" into
 corresponding .repo file in /etc/yum.repos.d/.

Hope that it helps.

Comment 2 ioguix 2019-06-11 20:02:58 UTC

Thank you for the pointer. It works as expected. I'm not sure what package name they have in common though, as wall packages in PGDG repo avec suffixed with the major version, eg: postgresql11, postgresql11-server, etc. But anyway.

I supposed the best approach would be to add modules in the pgdg repository itself. It sounds the perfect fit to provide all supported PostgreSQL major version from one repo (PGDG provide one repo per version today). However, what happen when two repo provide same module name?

Thanks again anyway!

Comment 3 ioguix 2019-06-11 20:07:10 UTC
One additional note though. I suppose this modular filtering should appears somewhere as a warning or at least as a debug message.

Today, this is just black hole pretty hard to detect for newcomers in RHEL8 and/or modules and streams :/

Note You need to log in before you can comment on or make changes to this bug.