Observation:
A notice appears as below when we run pkispawn:
"cmd": "pkispawn -s KRA -f /tmp/test_dir/kra.cfg", "delta": "0:00:52.418495", "end": "2018-05-15 08:31:27.685813", "rc": 0, "start": "2018-05-15 08:30:35.267318", "stderr": "Notice: Trust flag u is set automatically if the private key is present. The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified."
Build details:
[root@pki1 fedora]# rpm -qa | grep pki-* pki-base-java-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-console-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-kra-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-symkey-10.6.1-3.20180514020012.517dca6f.fc28.x86_64 pki-base-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-ca-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-tps-10.6.1-3.20180514020012.517dca6f.fc28.x86_64 python3-pki-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-server-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-tks-10.6.1-3.20180514020012.517dca6f.fc28.noarch dogtag-pki-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-tools-10.6.1-3.20180514020012.517dca6f.fc28.x86_64 dogtag-pki-console-theme-10.6.1-3.20180514020012.517dca6f.fc28.noarch pki-ocsp-10.6.1-3.20180514020012.517dca6f.fc28.noarch dogtag-pki-server-theme-10.6.1-3.20180514020012.517dca6f.fc28.noarch
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 type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
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/3139
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.