Skip to content

CMP-3405: adding SPO 0.9.0 bugs to release notes #97856

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

CMP-3405: adding SPO 0.9.0 bugs to release notes #97856

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions security/security_profiles_operator/spo-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,23 @@ These release notes track the development of the Security Profiles Operator in {

For an overview of the Security Profiles Operator, see xref:../../security/security_profiles_operator/spo-overview.adoc#spo-overview[Security Profiles Operator Overview].

[id="spo-release-notes-0-9-0"]
== Security Profiles Operator 0.9.0

The following advisory is available for the Security Profiles Operator 0.9.0:
link:https://access.redhat.com/errata/RHBA-2024:XXXX[RHBA-2024:XXXX - OpenShift Security Profiles Operator update]

[id="spo-0-9-0-bug-fixes"]
=== Bug fixes

* Previously, when using the log enricher to record a SelinuxProfile, the process would fail to create the profile because it was incorrectly identified as a seccomp profile. With this update, the log enricher correctly identifies the profile type and creates the SelinuxProfile as expected. (link:https://issues.redhat.com/browse/OCPBUGS-60139[*OCPBUGS-60139*])

* Previously, when you created a ProfileRecording object, the associated workloads could fail to start and would get stuck in an `Init:CreateContainerError` state. This was caused by an incorrect file path to the seccomp profile. With this update, the file path is corrected, and workloads now start as expected. (link:https://issues.redhat.com/browse/OCPBUGS-60048[*OCPBUGS-60048*])

* Previously, the spod pods could fail to start, entering a CrashLoopBackOff state due to an error parsing semanage configuration file. This issue was caused by an error in the SELinux configuration files. With this update, the configuration files have been corrected, and the spod pods now start successfully. (link:https://issues.redhat.com/browse/OCPBUGS-55829[*OCPBUGS-55829*])

* Previously, the Security Profiles Operator would fail to apply a RawSelinuxProfile to newly added nodes due to a reconciler type mismatch error. With this update, the operator now correctly handles RawSelinuxProfile objects, ensuring that policies are applied to all nodes as expected. (link:https://issues.redhat.com/browse/OCPBUGS-33718[*OCPBUGS-33718*])

[id="spo-release-notes-0-8-6"]
== Security Profiles Operator 0.8.6

Expand Down