Bug 1561051
| Summary: | F27 Server doesn't boot up in FIPS mode. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | pasi.valminen | ||||
| Component: | systemd | Assignee: | systemd-maint | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | lnykryn, msekleta, nmavrogi, omosnace, orion, s, systemd-maint, tmraz, zbyszek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-05-28 18:58:01 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: | |||||||
| Attachments: |
|
||||||
Same with Fedora 28. Any chance you could boot with a debug console enabled and logging to the kernel buffer (see https://www.freedesktop.org/wiki/Software/systemd/Debugging/), and provide the actual error message ('journalctl -b' output should be enough)? It appears that F29 boots with fips=1. Haven't gone back yet to test F28 or F27. On F29 to invoke the system FIPS mode properly you need to use the fips-mode-setup --enable command. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. |
Created attachment 1413725 [details] Screenshot of systemd-journald failure during boot up. Description of problem: F27 Server doesn't boot up in FIPS mode. Version-Release number of selected component (if applicable): Fedora-Server-dvd-x86_64-27-1.6.iso How reproducible: Always Steps to Reproduce: 1. Get the Server ISO from getfedora.org 2. Create a new VM and use the downloaded ISO as an installation source 3. Append fips=1 argument to the kernel arguments Actual results: Anaconda doesn't start. systemd-journald fails to start in a loop. Expected results: Anaconda starts and can install a new VM. Additional info: Installing the dracut-fips{,-aesni} RPMs, recreating the initramfs, and adding fips=1 and boot=<partition of /boot> kernel arguments on a physical machine fails to boot in the same manner.