When FreeIPA container image is built, yum installation of pki-server reports
Installing : pki-server-10.2.5-6.el7.noarch 361/373 Failed to get D-Bus connection: Operation not permitted warning: %post(pki-server-10.2.5-6.el7.noarch) scriptlet failed, exit status 1 Non-fatal POSTIN scriptlet failure in rpm package pki-server-10.2.5-6.el7.noarch Installing : pki-kra-10.2.5-6.el7.noarch 362/373
No such error was shown on previous versions.
Additional info:
It seems in current versions, systemctl daemon-reload was added via https://fedorahosted.org/pki/ticket/1255 / 7b1d897ba4cf9de1459d2aad37e969ce9a93a05a. In general (already in previous versions), it seems strange that the post scriptlet which is only meant for upgrade scenarios is not limited to situations when rpm upgrade actually happened. The whole thing probably should be behind an [ $1 == 1 ] if.
Per discussions in the Dogtag 10.3 Triage meeting of 01/06/2016: priority medium
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets
Per CS Bug/Ticket Triage held 04/19/2016: 10.3.2
This will take some time to investigate. Moving to 10.4.
Per Offline Triage of 11/30/2016-12/01/2016: 10.4 - critical
Metadata Update from @jpazdziora: - Issue assigned to edewata - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue priority set to: 1 (was: 2)
Upgraded priority to coincide with associated Bugzilla Bug.
Checked into 'master':
5bcfd93bac70def54a1224f4a89c50ed7c11316a
fceca0ccfc8341d9255540e9a1c3c406373a9483
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.2 (was: 10.4)
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/2280
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.
Login to comment on this ticket.