Although pkispawn is successful and the instances are up and running, several AVCs appear when invoking a pkispawn of subsystems which uses a customized user (i. e. - non "pkiuser").
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1543042 - Custom field type adjusted to None - Custom field version adjusted to None
Per 10.5.x/10.6 Triage: 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Duplicate of: https://pagure.io/dogtagpki/issue/3161
Metadata Update from @cipherboy: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3045
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, and we apologize for any inconvenience.