Bug 1017417

Summary:	389-base-ds incorrectly labled as core
Product:	Red Hat Enterprise Linux 6	Reporter:	John Priddy <jpriddy>
Component:	doc-Package_Manifest	Assignee:	Lenka Špačková <lkuprova>
Status:	CLOSED EOL	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	6.5	CC:	anthomas, dmach, nkinder, snagar
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1624874 (view as bug list)		Environment:
Last Closed:	2020-05-06 15:26:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1624874, 1624884

Description John Priddy 2013-10-09 20:28:10 UTC

Description of problem:

Package manifest labels 389-base-ds as core when it is (apparently) not core.


Steps to Reproduce:

A customer was asking about standing up an LDAP server in a supported fashion via the 389-base-ds package we ship and I told him that would not be supported and referenced this:

https://access.redhat.com/site/articles/65032

The package is *only* supported as a prereq of IDM and RHDS.  However, he looked up the package manifest and sure enough, that particular package is flagged as core:

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Package_Manifest/index.html

So either the kbase article is incorrect (unlikely since it was explictly created so that people didn't install 389 for full support) or the package manifest is incorrect.

Additional info:

There was more discussion on the internal mailing list about this here:

http://post-office.corp.redhat.com/archives/ldap-support-list/2013-October/msg00006.html

Comment 2 Eliska Slobodova 2013-10-10 07:49:50 UTC

Hi John,

The Package Manifest is generated by a script so there might be inconsistencies.
The kbase article is specific for 6.2; is it still valid for later RHEL versions as well? The problem is that for RHEL 6, there is only a single Package Manifest that is re-generated upon GAs of minor RHEL versions (the current one was created with RHEL 6.4).

If 389-ds-base is not a core package, I can correct the info and re-publish the book asap. And will check later when generating a new book for 6.5 to make sure the info is correct. Is it OK?

Comment 8 Petr Spacek 2015-10-15 08:55:05 UTC

BTW pki-* packages and probably new bind-pkcs11 package have the very
same problem, i.e. should be listed as "non-core".

Comment 10 Nathan Kinder 2015-10-15 18:36:00 UTC

We should be listing the following as non-core packages, as they are only supported for use as a part of ipa-server, Red Hat Directory Server, or Red Hat Certificate System:

  389-ds-base
  nuxwdog
  pki-ca

These are all incorrectly listed as "core" in the current RHEL 7 package manifest.  In addition, the following appear to be incorrect in the RHEL 6 package manifest:

  389-ds-base
  ipa-pki-ca-theme
  ipa-pki-common-theme
  nuxwdog
  pki-ca
  pki-silent

Comment 12 Petr Spacek 2015-11-18 12:38:42 UTC

While reviewing package manifest for RHEL 7.2, I just found out that following packages should also be listed as non-core packages:
bind-pkcs11
bind-pkcs11-utils

Comment 13 Lenka Špačková 2015-11-19 10:32:23 UTC

The requested changes have been made to the RHEL 7.2 version, now published at:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Package_Manifest/index.html

We are working on updating the 6.7 version.