Bug 1821548

Summary:	schema validation fails
Product:	[Fedora] Fedora	Reporter:	Dennis Gilmore <dennis>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	32	CC:	awilliam, gmarr, mreynolds, robatino, spichugi, tbordaz, vashirov
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	RejectedBlocker
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:39:45 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:
Embargoed:

Description Dennis Gilmore 2020-04-07 03:45:07 UTC

Description of problem:
On my fedora 32 freeipa install when upgrading 389-ds-base to 389-ds-base-1.4.3.5-1.fc32 starting directory server 

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
Apr 07 03:21:27 chaka.ausil.us systemd[1]: Starting 389 Directory Server AUSIL-US....
Apr 07 03:21:27 chaka.ausil.us ns-slapd[1349]: [07/Apr/2020:03:21:27.826680650 +0000] - ERR - dse_read_one_file - The entry cn=schema in file /etc/dirsrv/slapd-AUSIL-US/schema/15rfc2307bis.ldif (lineno: 1) is invalid, error code 20 (Type>
Apr 07 03:21:27 chaka.ausil.us ns-slapd[1349]: [07/Apr/2020:03:21:27.847820252 +0000] - ERR - setup_internal_backends - Please edit the file to correct the reported problems and then restart the server.
Apr 07 03:21:27 chaka.ausil.us systemd[1]: dirsrv: Main process exited, code=exited, status=1/FAILURE
Apr 07 03:21:27 chaka.ausil.us systemd[1]: dirsrv: Failed with result 'exit-code'.


Expected results:


Additional info:
downgrading 389-ds-base enables everything to start again

Comment 1 Dennis Gilmore 2020-04-07 03:48:02 UTC

Proposing as a final blocker as freeipa server does not work with this bug present. there is a comment in the update that it also causes ipa installs to fail. see https://bugzilla.redhat.com/show_bug.cgi?id=1820176

Comment 2 Adam Williamson 2020-04-07 21:29:58 UTC

The update never reached stable and has been unpushed, so this can't really be a release blocker..

Comment 3 Geoffrey Marr 2020-04-13 19:31:29 UTC

Discussed during the 2020-04-13 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker" was made as the update that causes this bug never reached stable state and has been unpushed, so the bug is not really affecting F32 at all.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-04-13/f32-blocker-review.2020-04-13-16.04.txt

Comment 4 Viktor Ashirov 2020-10-27 12:39:45 UTC

Closing per comment #3.