Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1279784 - System upgrade resets SElinux settings
Summary: System upgrade resets SElinux settings
Keywords:
Status: CLOSED DUPLICATE of bug 1279621
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-10 10:05 UTC by Illya
Modified: 2015-11-12 09:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-12 09:59:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Illya 2015-11-10 10:05:32 UTC 
Description of problem:
Upgrade from Fedora 22 to Fedora 23 with dnf-plugin-system-upgrade caused some SELinux settings to be changed to default.

Hier example with nginx. But the same situation is with pdns (pdns_can_network_connect_db)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install nginx on Fedora 22
2. Allow network connection to DB (setsebool -P httpd_can_network_connect_db 1)
3. Upgrade system as described hier: https://fedoraproject.org/wiki/DNF_system_upgrade

Actual results:
Nginx cannot connect DB:

getsebool httpd_can_network_connect_db
httpd_can_network_connect_db --> off



Expected results:
DB connection from web server still works after upgrade

Additional info:
Comment 1 Will Woods 2015-11-11 15:42:48 UTC 
As it says in the man page:

       Similarly, problems encountered on your system after the  upgrade  com‐
       pletes  should  be  reported  to the maintainers of the affected compo‐
       nents.  In other words: if (for example) KDE stops working,  it's  best
       if you report that to the KDE maintainers.

This is an SELinux policy problem, so I'm reassigning to selinux-policy.
Comment 2 Miroslav Grepl 2015-11-12 09:59:44 UTC 

*** This bug has been marked as a duplicate of bug 1279621 ***
Note You need to log in before you can comment on or make changes to this bug.