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 1541926 - [openvswitch-2.9.0-0.3] openvswitch service failed to start
Summary: [openvswitch-2.9.0-0.3] openvswitch service failed to start
Keywords:
Status: CLOSED DUPLICATE of bug 1482682
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-05 08:48 UTC by Gan Huang
Modified: 2018-02-06 09:36 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-05 11:20:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gan Huang 2018-02-05 08:48:18 UTC
Description of problem:
Trigger OCP installation on RHEL-7.4 with openvswitch-2.9.0-0.3. It resulted in that atomic-openshift-node failed to start during installation due to the openvswitch service failure.

Version-Release number of selected component (if applicable):
# rpm -q openvswitch
openvswitch-2.9.0-0.3.20180124git26cdc33.el7fdp.x86_64
# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.4 (Maipo)
# uname -r
3.10.0-693.17.1.el7.x86_64


How reproducible:
always

Steps to Reproduce:
1. Trigger OCP installation on RHEL-7.4 with openvswitch-2.9.0-0.3.20180124git26cdc33.el7fdp.x86_64
2.
3.

Actual results:
atomic-openshift-node failed to start, as well as the openvswitch service

Expected results:
# systemctl status openvswitch
● openvswitch.service - Open vSwitch
   Loaded: loaded (/usr/lib/systemd/system/openvswitch.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

Feb 05 03:06:40 host-192-168-100-16 systemd[1]: Dependency failed for Open vSwitch.
Feb 05 03:06:40 host-192-168-100-16 systemd[1]: Job openvswitch.service/start failed with result 'dependency'.
Feb 05 03:07:11 host-192-168-100-16 systemd[1]: Dependency failed for Open vSwitch.
Feb 05 03:07:11 host-192-168-100-16 systemd[1]: Job openvswitch.service/start failed with result 'dependency'.
Feb 05 03:39:38 host-192-168-100-16 systemd[1]: Dependency failed for Open vSwitch.
Feb 05 03:39:38 host-192-168-100-16 systemd[1]: Job openvswitch.service/start failed with result 'dependency'.


# journalctl -u ovsdb-server
Feb 05 03:39:39 host-192-168-100-16 systemd[1]: ovsdb-server.service holdoff time over, scheduling restart.
Feb 05 03:39:39 host-192-168-100-16 systemd[1]: Starting Open vSwitch Database Unit...
Feb 05 03:39:39 host-192-168-100-16 runuser[32620]: PAM audit_open() failed: Permission denied
Feb 05 03:39:39 host-192-168-100-16 ovs-ctl[32588]: runuser: System error
Feb 05 03:39:39 host-192-168-100-16 ovs-ctl[32588]: /etc/openvswitch/conf.db does not exist ... (warning).
Feb 05 03:39:39 host-192-168-100-16 ovs-ctl[32588]: Creating empty database /etc/openvswitch/conf.db runuser: System error
Feb 05 03:39:39 host-192-168-100-16 ovs-ctl[32588]: [FAILED]
Feb 05 03:39:39 host-192-168-100-16 systemd[1]: ovsdb-server.service: control process exited, code=exited status=1
Feb 05 03:39:39 host-192-168-100-16 systemd[1]: Failed to start Open vSwitch Database Unit.



Additional info:

Comment 2 Gan Huang 2018-02-05 08:49:53 UTC
atomic-openshift-node/openvswitch can get running once downgrading to openvswitch-2.7.3-2.git20171010.el7fdp.x86_64

Comment 3 Meng Bo 2018-02-05 09:56:48 UTC
The selinux version of the problem env is:
selinux-policy-3.13.1-166.el7_4.8.noarch
selinux-policy-targeted-3.13.1-166.el7_4.8.noarch


And with the same openvswitch build and different selinux version, the issue cannot be reproduced
Good env:
selinux-policy-3.13.1-183.el7.noarch
selinux-policy-targeted-3.13.1-183.el7.noarch

Comment 4 Timothy Redaelli 2018-02-05 11:20:42 UTC
You need to use a new selinux-policy

*** This bug has been marked as a duplicate of bug 1482682 ***


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