Bug 1695302
| Summary: | New nuxwdog fails to start as expected | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Dinesh Prasanth <dmoluguw> |
| Component: | pki-core | Assignee: | Dinesh Prasanth <dmoluguw> |
| Status: | CLOSED ERRATA | QA Contact: | Asha Akkiangady <aakkiang> |
| Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
| Priority: | unspecified | ||
| Version: | 8.1 | CC: | dpunia, edewata, mharmsen |
| Target Milestone: | rc | Keywords: | TestCaseProvided |
| Target Release: | 8.1 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pki-core-10.6-8010020190613214740.8ba0ffbe | Doc Type: | Bug Fix |
| Doc Text: |
.The `Nuxwdog` service no longer fails to start the PKI server in HSM environments
Previously, due to bugs, the `keyutils` package was not installed as a dependency of the `pki-core` package. Additionally, the `Nuxwdog` watchdog service failed to start the public key infrastructure (PKI) server in environments that use a hardware security module (HSM). These problems have been fixed. As a result, the required `keyutils` package is now installed automatically as a dependency, and `Nuxwdog` starts the PKI server as expected in environments with HSM.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-05 21:06:55 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: | 1652269 | ||
|
Comment 5
Dinesh Prasanth
2019-06-24 14:41:27 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3416 |