Bug 1394232 - Do not hard-require OvS as long as it crashes on old AMD servers
Summary: Do not hard-require OvS as long as it crashes on old AMD servers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.0.5
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ovirt-4.0.5-1
: ---
Assignee: Dan Kenigsberg
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On: 1391856
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-11 12:52 UTC by Francesco Romani
Modified: 2020-01-17 16:11 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1391856
Environment:
Last Closed: 2016-11-23 00:35:48 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2751391 0 None None None 2016-11-11 12:52:16 UTC
Red Hat Product Errata RHBA-2016:2818 0 normal SHIPPED_LIVE vdsm 4.0.5 bug fix and enhancement update 2016-11-23 05:35:22 UTC
oVirt gerrit 66100 0 None None None 2016-11-11 12:52:16 UTC

Description Francesco Romani 2016-11-11 12:52:17 UTC
+++ This bug was initially created as a clone of Bug #1391856 +++

Description of problem:
    Due to bugzilla Bug 1378501 openvswitch does not start for AMD hardware.

Version-Release number of selected component (if applicable):
    RHV 4.0.4

How reproducible:
    100%

Steps to Reproduce:
1.  # ovs-vswitchd --version 
2.
3.

Actual results:
ERROR: This system does not support "SSSE3".
Please check that RTE_MACHINE is set correctly.

Expected results:
ovs runs regardless of SSSE3 instruction set support.

Additional information
Fixed in openvswitch-2.5.0-17.git20160727.el7fdb

--- Additional comment from Dan Kenigsberg on 2016-11-04 08:07:32 EDT ---

Until fixed by pushing the request package into the fast-datapath channel, users can manually comment-out the line

    Requires=openvswitch

from their /usr/lib/systemd/system/vdsm-network-init.service

--- Additional comment from Dan Kenigsberg on 2016-11-06 02:05:39 EST ---

I'm taking this bug to Vdsm, since it might be long before an openvswitch fixed is rushed into the fast datapath channel.

Comment 2 Michael Burman 2016-11-13 10:04:07 UTC
Verified on - vdsm-4.18.15.3-1.el7ev.x86_64 on old AMD server that running openvswitch-2.5.0-10.git20160727.el7fdb.x86_64.

vdsm started successfully

Comment 4 errata-xmlrpc 2016-11-23 00:35:48 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://rhn.redhat.com/errata/RHBA-2016-2818.html


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