Bug 905825 - PamConfig schema not updated during upgrade
Ján Rusnačko 2013-01-30 04:12:13 EST
Description of problem: After upgrade from RHEL 6.3 to RHEL 6.4, upgrade script is not updating schema file for PamConfig objectClass. This means that new features for PAM like configuration of multiple instances and pamFilter attribute are not possible due to schema violation.
Version-Release number of selected component (if applicable): 389-ds-base-1.2.11.15-11
Steps to Reproduce: 1. Upgrade from 1.2.10.2-15 (RHEL 6.3) to 1.2.11.15-11 (RHEL 6.4) 2. Check the schema for pamConfig:
objectClasses: ( 2.16.840.1.113730.3.2.318 NAME 'pamConfig' DESC 'PAM plugin configuration' SUP top AUXILIARY MAY ( pamMissingSuffix $ pamExcludeSuffix $ pamIncludeSuffix $ pamIDAttr $ pamIDMapMethod $ pamFallback $ pamSecure $ pamService ) X-ORIGIN 'Red Hat Directory Server' )
Expected results: When 1.2.11.15-11 is installed, not upgraded, schema for pamConfig looks like this:
objectClasses: ( 2.16.840.1.113730.3.2.318 NAME 'pamConfig' DESC 'PAM plugin configuration' SUP top AUXILIARY MAY ( cn $ pamMissingSuffix $ pamExcludeSuffix $ pamIncludeSuffix $ pamIDAttr $ pamIDMapMethod $ pamFallback $ pamSecure $ pamService $ pamFilter ) X-ORIGIN 'Red Hat Directory Server' )
Note that cn and pamFilter attribute are missing after upgrade.
git patch file (master) 0001-Ticket-572-PamConfig-schema-not-updated-during-upgra.patch
Bug description: PAM passthrough schema was not upgraded in the upgrade from 389-ds-base-1.2.10.2 to 389-ds-base-1.2.11.15.
Fix description: This patch adds 60pam-plugin.ldif to the upgrade schema file list.
Reviewed by Nathan (Thank you!!)
Pushed to master: commit ac6b2c94bb32fc47870a56e8f7fc109ea81a3f47
Pushed to 389-ds-base-1.2.11: commit dbef082f71a15c0e2fa98833b822efab4771f8a3
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.19
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/572
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)