Bug 1385740 - Fail due kmod is wrong and hardcoded.
Summary: Fail due kmod is wrong and hardcoded.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-puppet-modules
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: async
: 8.0 (Liberty)
Assignee: Jason Guiditta
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 15:38 UTC by Cyril Lopez
Modified: 2016-10-26 13:43 UTC (History)
7 users (show)

Fixed In Version: openstack-puppet-modules-7.1.4-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 13:43:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-cip/puppet-contrail/commit/c843dbbe645a9b4ecc89a3898c33c75f51cec512 0 None None None 2016-10-17 15:39:56 UTC
Red Hat Product Errata RHBA-2016:2111 0 normal SHIPPED_LIVE openstack-puppet-modules bug fix advisory 2016-10-26 17:41:57 UTC

Description Cyril Lopez 2016-10-17 15:38:38 UTC 
Description of problem:
kmod is hardcoded and in contrail 3.x and next not suppose called with full path.

It's breaking install and life-cycle.

Already fix here : 
https://github.com/redhat-cip/puppet-contrail/commit/c843dbbe645a9b4ecc89a3898c33c75f51cec512

Version-Release number of selected component (if applicable):
openstack-puppet-modules-7.0.19-1.el7ost.noarch
Comment 1 Jason Guiditta 2016-10-20 13:02:31 UTC 
Referenced commit is included in build for another BZ 1346002
Comment 4 errata-xmlrpc 2016-10-26 13:43:07 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-2111.html
Note You need to log in before you can comment on or make changes to this bug.