|
Bugzilla – Full Text Bug Listing |
| Summary: | fips pattern not found | ||
|---|---|---|---|
| Product: | [openSUSE] PUBLIC SUSE Linux Enterprise Micro 6.0 | Reporter: | Martin Loviska <mloviska> |
| Component: | Patterns | Assignee: | Marcus Meissner <meissner> |
| Status: | RESOLVED FIXED | QA Contact: | Jose Lausuch <jalausuch> |
| Severity: | Normal | ||
| Priority: | P1 - Urgent | CC: | felix.niederwanger, giacomo.leidi, jsrain, meissner, tjyrinki |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | zypper.log | ||
|
Description
Martin Loviska
2024-02-27 08:17:47 UTC
As a sidenote the alp_fips pattern itself is functional (see fips_setup at https://openqa.suse.de/tests/13619286). I'm not sure what should be done about transactional-update's setup-fips feature, maybe it should at least have a useful error message? Notably SLE 15-SP4 and newer obtained crypto-policies-scripts recently which contain a "fips-mode-setup" script that is now used, so there are multiple ways. That has not been available in SLE Micro 6.0 packages however. fix submitted subnmitted |