RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1414130 - Re-declaration of docker_t error when upgrade selinux-policy-targeted
Summary: Re-declaration of docker_t error when upgrade selinux-policy-targeted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
: 1427296 (view as bug list)
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2017-01-17 20:45 UTC by Marko Myllynen
Modified: 2021-08-30 11:54 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 15:20:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2916911 0 None None None 2017-02-09 12:53:02 UTC
Red Hat Product Errata RHBA-2017:1861 0 normal SHIPPED_LIVE selinux-policy bug fix update 2017-08-01 17:50:24 UTC

Description Marko Myllynen 2017-01-17 20:45:38 UTC 
Description of problem:
When updating RHEL 7 with container-selinux-1.10.3-59.el7 (but not docker-selinux nor docker-engine-selinux) installed, I see:

...
  Updating   : selinux-policy-targeted-3.13.1-102.el7_3.13.noarch
Re-declaration of type docker_t
Failed to create node
Bad type declaration at /etc/selinux/targeted/tmp/modules/100/docker/cil:1
/usr/sbin/semodule:  Failed!
...

Update was:

---> Package selinux-policy-targeted.noarch 0:3.13.1-102.el7_3.7 will be updated
---> Package selinux-policy-targeted.noarch 0:3.13.1-102.el7_3.13 will be an update

Thanks.
Comment 1 Daniel Walsh 2017-01-17 20:52:54 UTC 
This happened, I belive, because you had a former bad container-selinux package installed.

The latest container-selinux disables docker module, whereas a test version removed it.  Disabling it should not cause this issue, since selinux-policy-targeted will just update the disabled module.  Where as the older version of contianer-selinux which removed the docker module, the updated selinux-policy would re-add it causing this issue.

dnf remove container-selinux
dnf reinstall selinux-policy
dnf install container-selinux

Should fix the issue.
Comment 2 Marko Myllynen 2017-01-17 21:38:48 UTC 
(In reply to Daniel Walsh from comment #1)
> This happened, I belive, because you had a former bad container-selinux
> package installed.
> 
> The latest container-selinux disables docker module, whereas a test version
> removed it.  Disabling it should not cause this issue, since
> selinux-policy-targeted will just update the disabled module.  Where as the
> older version of contianer-selinux which removed the docker module, the
> updated selinux-policy would re-add it causing this issue.
> 
> dnf remove container-selinux
> dnf reinstall selinux-policy
> dnf install container-selinux
> 
> Should fix the issue.

Thanks, this it, these steps worked.
Comment 5 Milos Malik 2017-03-01 07:31:13 UTC 
I'm going to investigate if the same problem appears after application of the latest batch update.
Comment 7 Daniel Walsh 2017-03-01 13:18:24 UTC 
So this is happening if container-selinux is not installed?
Comment 8 Milos Malik 2017-03-01 13:31:18 UTC 
Yes, docker* or container* RPM packages were never installed on the machines, which I used for testing.
Comment 9 Daniel Walsh 2017-03-01 13:43:24 UTC 
Ok so I guess lukas has removed the docker.pp and replaced it with container.pp in the default install.  On update it seems like it is not removing docker.pp at the same time as it is adding container.pp?
Comment 12 Lukas Vrabec 2017-03-30 10:58:55 UTC 
*** Bug 1427296 has been marked as a duplicate of this bug. ***
Comment 15 errata-xmlrpc 2017-08-01 15:20:12 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1861
Note You need to log in before you can comment on or make changes to this bug.