Why does installing a RPM package fail to find a non-local user or group provided by the corporate directory?

Solution In Progress - Updated -

Issue

  • Why does installing a RPM package that relies on external users and/or groups fail to locate the user/group?
# rpm -iv custom-package.rpm
Verifying packages...
Preparing packages...
custom-package.x86_64
warning: group xxxxxx does not exist - using root
warning: group xxxxxx does not exist - using root
warning: group xxxxxx does not exist - using root
  • The same package is able to locate the external user/group and install successfully on earlier RHEL major releases.

Environment

  • Red Hat Eneterprise Linux 10.
  • RPM package relying on external users and/or groups.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content