Bug 1550398
| Summary: | failed to start vhost interface after updating ovs to 2.9 in osp10 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | zenghui.shi <zshi> | ||||||
| Component: | openvswitch | Assignee: | Aaron Conole <aconole> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 10.0 (Newton) | CC: | aconole, amuller, apevec, atelang, chrisw, fbaudin, lhh, pliu, rhos-maint, skramaja, srevivo, yroblamo, zshi | ||||||
| Target Milestone: | --- | Keywords: | SELinux, Triaged, ZStream | ||||||
| Target Release: | 10.0 (Newton) | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | openstack-selinux-0.8.14, openvswitch-2.9.0-15 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-06-27 23:33:22 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
zenghui.shi
2018-03-01 08:05:22 UTC
This issue is in OSP10 with ovs2.9, which means the default vhost-user mode is dpdkvhostuser (ovs in the server mode). And the vhost sockets will be created on the /var/run/openvswitch/ directory. The config of --socket-mem looks odd '20482048', but I didn't configure or change it manually, is it auto-generated?
[root@overcloud-compute-0 log]# cat /etc/sysconfig/openvswitch
OPTIONS=""
DPDK_OPTIONS = "-l 4,6,20,22 -n 4 --socket-mem 20482048 -w 0000:06:00.1"
Getting other_config returns good value:
[root@overcloud-compute-0 log]# ovs-vsctl get Open_vSwitch . other_config
{dpdk-init="true", dpdk-lcore-mask="a800a8", dpdk-socket-mem="2048,2048", pmd-cpu-mask="500050"}
(In reply to zenghui.shi from comment #2) > The config of --socket-mem looks odd '20482048', but I didn't configure or > change it manually, is it auto-generated? > > [root@overcloud-compute-0 log]# cat /etc/sysconfig/openvswitch > OPTIONS="" > DPDK_OPTIONS = "-l 4,6,20,22 -n 4 --socket-mem 20482048 -w 0000:06:00.1" > DPDK_OPTIONS is not used from ovs2.6 onwards. other_config:dpdk-socket-mem is only used. There some mismatch in the puppet configuration because of changed parameter format, but you can ignore it as it is not used. Created attachment 1416255 [details]
audit-2018-4-2.log
type=USER_AVC msg=audit(1522670657.993:1217): pid=1282 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_call interface=org.freedesktop.login1.Manager member=Inhibit dest=org.freedesktop.login1 spid=242890 tpid=1293 scontext=system_u:system_r:virtlogd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:systemd_logind_t:s0 tclass=dbus exe=2F7573722F62696E2F646275732D6461656D6F6E3B3561633165373430202864656C6574656429 sauid=81 hostname=? addr=? terminal=?'
This looks like:
https://bugzilla.redhat.com/show_bug.cgi?id=1561729
Next update for OSP10 should have the fix for that USER_AVC (for now), which will be resolved in a different way by libvirt at a later time. 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/RHSA-2018:2102 |