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 1570833 - cockpit-dashboard must require selinux-policy-targeted in post section
Summary: cockpit-dashboard must require selinux-policy-targeted in post section
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: 7.5
Assignee: Martin Pitt
QA Contact: Leos Pol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-23 13:37 UTC by Sandro Bonazzola
Modified: 2018-06-26 18:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-26 18:38:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1563737 0 unspecified CLOSED Unable to connect via serial console to HE. /bin/sh: Permission denied. 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2018:2026 0 None None None 2018-06-26 18:38:59 UTC

Internal Links: 1563737

Description Sandro Bonazzola 2018-04-23 13:37:45 UTC
cockpit-dashboard uses semanage in %post section but doesn't require selinux-policy-targeted at %post section

This allow to install cockpit-dashboard before selinux-policy-targeted while building the RHV-M appliance with anaconda generating the following traceback extracted from https://bugzilla.redhat.com/show_bug.cgi?id=1563737

07:01:38,735 INFO packaging: cockpit-dashboard-160-3.el7.x86_64 (840/996)
07:01:38,735 INFO packaging: Applying workaround for broken SELinux policy: https://bugzilla.redhat.com/show_bug.cgi?id=1381331
07:01:38,736 INFO packaging: Traceback (most recent call last):
07:01:38,736 INFO packaging:   File "/sbin/semanage", line 32, in <module>
07:01:38,737 INFO packaging:     import seobject
07:01:38,737 INFO packaging:   File "/usr/lib64/python2.7/site-packages/seobject/__init__.py", line 36, in <module>
07:01:38,737 INFO packaging:     import sepolicy
07:01:38,738 INFO packaging:   File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 921, in <module>
07:01:38,738 INFO packaging:     raise e
07:01:38,739 INFO packaging: ValueError: No SELinux Policy installed
07:01:38,739 INFO packaging: No such file or directory

Comment 1 Martin Pitt 2018-04-24 06:52:13 UTC
Indeed this workaround is now obsolete for 7.5, so the whole %post can be dropped for cockpit-dashboard. It's too late for 7.5.1, but I'll do that for 7.5.2 (and of course 7.6).

Aside from that traceback (which isn't fatal) this should not have broken anything at runtime, right?

Comment 2 Sandro Bonazzola 2018-04-24 12:11:56 UTC
(In reply to Martin Pitt from comment #1)
> Indeed this workaround is now obsolete for 7.5, so the whole %post can be
> dropped for cockpit-dashboard. It's too late for 7.5.1, but I'll do that for
> 7.5.2 (and of course 7.6).
> 
> Aside from that traceback (which isn't fatal) this should not have broken
> anything at runtime, right?

I'm not aware of any other issue other than the traceback.

Comment 3 Martin Pitt 2018-05-29 12:00:49 UTC
The upstream fix (https://github.com/cockpit-project/cockpit/commit/f2134507aa0) landed in version 158. RHEL Extras 7.5.1 has cockpit-dashboard 160, so this is fixed there.

Comment 4 Martin Pitt 2018-05-30 11:43:06 UTC
Sorry, this wasn't in the downstream spec file yet. Reopening, and adding to the current extras rebase for 7.5.2 (#1582426)

Comment 6 Leos Pol 2018-06-17 08:31:59 UTC
$ rpm -q cockpit-dashboard
cockpit-dashboard-165-3.el7.x86_64

$ rpm -q --scripts cockpit-dashboard
postinstall scriptlet (using /bin/sh):
# HACK: Until policy changes make it downstream
echo "Applying workaround for broken SELinux policy: https://bugzilla.redhat.com/show_bug.cgi?id=1381331" >&2
if type semanage >/dev/null 2>&1; then
    semanage fcontext -a /usr/libexec/cockpit-ssh -t cockpit_ws_exec_t || true
    restorecon /usr/libexec/cockpit-ssh || true
else
    chcon -t cockpit_ws_exec_t /usr/libexec/cockpit-ssh || true
fi

# storaged on RHEL 7.4 and Fedora < 27, udisks on newer ones
# Recommends: not supported in RHEL < 8

$ rpm -q cockpit-dashboard
cockpit-dashboard-169-1.el7.x86_64
$ rpm -q --scripts cockpit-dashboard
$

Comment 8 errata-xmlrpc 2018-06-26 18:38:52 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-2018:2026


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