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 2005897 - ipa-server-install command fails to install IPA server after install/uninstall some security packages [NEEDINFO]
Summary: ipa-server-install command fails to install IPA server after install/uninstal...
Keywords:
Status: CLOSED DUPLICATE of bug 1949136
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.9
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-20 12:46 UTC by Daniel Filho
Modified: 2024-12-20 21:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-22 18:13:47 UTC
Target Upstream Version:
Embargoed:
frenaud: needinfo?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-6859 0 None None None 2021-09-21 10:58:11 UTC
Red Hat Issue Tracker RHELPLAN-97635 0 None None None 2021-09-20 12:49:08 UTC

Comment 8 Florence Blanc-Renaud 2021-09-20 14:27:10 UTC 
According to the attached list of installed rpms:
389-ds-base-1.3.10.2-12.el7_9.x86_64 
pki-server-10.5.18-12.el7_9.noarch
ipa-server-4.6.8-5.el7_9.4.x86_64

The customer is hitting known issue Bug 1949136 - PKI instance creation failed with new 389-ds-base build [rhel-7.9.z] and should also apply pki (https://access.redhat.com/errata/RHBA-2021:2315) and ipa (https://access.redhat.com/errata/RHBA-2021:2324) updates.

As a general rule, please refer to https://access.redhat.com/articles/11258, especially the following sentence:
----- 8< -----
Applying package updates on Red Hat Enterprise Linux 7

Before installing an update, make sure all previously released errata relevant to the system have been applied.
----- >8 -----

Please let me know if it solves the issue, and I will close this BZ as a duplicate.
Comment 10 Florence Blanc-Renaud 2021-09-22 18:13:47 UTC 
> Customer question.
> -----
> If these new versions fix a broken version of 389-ds-base-1.3.10.2-12.el7_9.x86_64, but why these packages did not get downloaded when we used below command?
> 
>    yum --security update   --downloadonly --downloaddir=/tmp/security_rpms  
> 
> even though 389-ds-base-1.3.10.2-12.el7_9.x86_64 broken version of RPM gets downloaded via patch update.
> -----

"yum update --downloadonly" doesn't apply the updates but only downloads the rpms. Extract from the man page yum(8):
----- 8< -----
       --downloadonly
              Download the resolved package set without performing any rpm transaction (install/upgrade/erase).
----- >8 -----

If the command to apply the updates was focused on 389-ds packages only, the other packages would not get updated (for instance dnf update /tmp/security_rpms/389-ds-*.rpm).

I am closing this issue as a duplicate of BZ #1949136.

*** This bug has been marked as a duplicate of bug 1949136 ***
Note You need to log in before you can comment on or make changes to this bug.