Bug 2359260 - snapd-2.68.3-0.el8.x86_64 on RHEL 8.10 blocked by selinux
Summary: snapd-2.68.3-0.el8.x86_64 on RHEL 8.10 blocked by selinux
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: snapd
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Zygmunt Krynicki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-13 00:19 UTC by Louis van Dyk
Modified: 2025-04-13 00:19 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Louis van Dyk 2025-04-13 00:19:03 UTC
Description of problem:
snapd-2.68.3 installed on RHEL 8.10 with SELinux enforcing fails to perform any actions, resulting in timeouts.  If SELinux is set to permissive mode, and snapd is restarted, then it works as expected.  snapd-2.67 is also affected.  Downgrading to snapd-2.65.1-0.el8.x86_64 works with SELinux in enforcing mode.

Version-Release number of selected component (if applicable):
snapd-selinux-2.68.3-0.el8.noarch                                                                                                                                                                                    snap-confine-2.68.3-0.el8.x86_64                                                                                                                                                                                     snapd-2.68.3-0.el8.x86_64                                  

How reproducible:
Always

Steps to Reproduce:
1. Install or upgrade the above three packages to 2.68.3 (or 2.67 which is also affected).
2. Run a snap command.
3. Wait as the server times out.  
4. setenforce 0
5. Restart snapd (it will take a long time to stop)
6. Run the snap command again, and it will succeed.
7. Downgrade snapd to 2.65.1.
8. setenforce 1
9. Restart snapd
10.  Run the snap command, and it will success with SELinux enforcing.

Actual results:
As above

Expected results:
It should work in enforcing mode with 2.68.3 which is the current release.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.