Bug #7388

Policy module isn't reloaded when upgrading RPM

Added by Dominic Cleal over 3 years ago. Updated over 3 years ago.

Status:Closed
Priority:Urgent
Assigned To:Dominic Cleal
Category:Packaging
Target version:Foreman - Sprint 29
Difficulty: Bugzilla link:
Found in release: Pull request:https://github.com/theforeman/foreman-selinux/pull/33
Story points-
Velocity based estimate-
Release1.6.1Release relationshipAuto

Description

The RPM postinstall scriptlet doesn't appear to reload the new module into the SELinux policy when the package is upgraded(!).

[root@localhost ~]# semodule -l | grep foreman
[root@localhost ~]# yum install foreman-selinux-1.6.0-0.1.RC1.el7 -y >/dev/null 2>&1; echo $?
0
[root@localhost ~]# semodule -l | grep foreman
foreman    1.6.0.0.1    
[root@localhost ~]# yum upgrade foreman-selinux-1.6.0-0.2.RC2.el7 -y >/dev/null 2>&1; echo $?
0
[root@localhost ~]# semodule -l | grep foreman
foreman    1.6.0.0.1    

This appears to have been introduced in #6780 for 1.6.


Related issues

Related to SELinux - Bug #6780: Unable to remove foreman-selinux Closed 07/25/2014

Associated revisions

Revision 2f345dec
Added by Dominic Cleal over 3 years ago

refs #7388 - make foreman-selinux-enable upgrade-safe

History

#1 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #6780: Unable to remove foreman-selinux added

#2 Updated by Dmitri Dolguikh over 3 years ago

  • Target version changed from Sprint 28 to Sprint 29

#3 Updated by Dominic Cleal over 3 years ago

  • Status changed from New to Assigned
  • Assigned To set to Dominic Cleal

#4 Updated by The Foreman Bot over 3 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-selinux/pull/33 added

#6 Updated by Dominic Cleal over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF