Bug 1456052

Summary: Large number of "ERR - cos-plugin - cos_cache_query_attr - cos attribute krbPwdPolicyReference failed schema check" errors during FreeIPA upgrade to Fedora 26
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 26CC: edewata, mreynolds, nhosoi, nkinder, rmeggins, vashirov
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 12:15:14 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:
Bug Depends On:    
Bug Blocks: 1456038    
Attachments:
Description Flags
journal file (use journalctl --file system.journal -b-1 to see messages from the upgrade boot)
none
journal file (use journalctl --file system.journal -b-1 to see messages from the upgrade boot) none

Description Adam Williamson 2017-05-26 21:51:07 UTC
I'm currently testing upgrades of Fedora 25 FreeIPA servers to Fedora 26, and noticing several problems. One is that there's a huge number of error messages along these lines in the system journal during the upgrade process:

May 26 11:42:21 ipa001.domain.local ns-slapd[16739]: [26/May/2017:14:42:21.014348077 -0400] - ERR - cos-plugin - cos_cache_query_attr - cos attribute krbPwdPolicyReference failed schema check on dn: ipk11UniqueID=428cdd50-4241-11e7-adcc-525400120019,cn=keys,cn=sec,cn=dns,dc=domain,dc=local

they all start the same way - "ERR - cos-plugin - cos_cache_query_attr - cos attribute krbPwdPolicyReference failed schema check on dn:" - but many different dns are referenced. There are 1,196 of the messages in total during the upgrade boot. I will attach the entire journal file for investigation.

I can't yet tell if there's any practical consequence of these errors.

Comment 1 Adam Williamson 2017-05-26 21:52:51 UTC
Created attachment 1282776 [details]
journal file (use journalctl --file system.journal -b-1 to see messages from the upgrade boot)

Comment 2 Adam Williamson 2017-05-26 21:53:24 UTC
Created attachment 1282777 [details]
journal file (use journalctl --file system.journal -b-1 to see messages from the upgrade boot)

Comment 3 Viktor Ashirov 2017-05-29 08:22:52 UTC
Hi Adam,

I believe it was fixed in 389-ds-base-1.3.6.6-1.fc26:
https://koji.fedoraproject.org/koji/buildinfo?buildID=897798

Upstream ticket: https://pagure.io/389-ds-base/issue/49249

What version of 389-ds-base are you using?


Thanks.

Comment 4 Adam Williamson 2017-06-02 21:06:19 UTC
Hi Viktor! The test would be using the 389-ds-base that's currently in F26 stable, so it wouldn't be using that version as it's only in updates-testing. I'll try to find a minute to modify the test to use that 389-ds-base and confirm that it fixes the problem.

Comment 5 Fedora End Of Life 2018-05-03 08:33:07 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2018-05-29 12:15:14 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.