Bug 1434710

Summary: Disable the OpenDaylight upstream repository
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: openstack-tripleo-heat-templatesAssignee: Tim Rozet <trozet>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: urgent Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: mburns, nyechiel, rhel-osp-director-maint, trozet
Target Milestone: Upstream M3Keywords: Triaged, ZStream
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170721174554.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2017-12-13 21:20:39 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:
Bug Depends On: 1431992    
Bug Blocks:    

Description Itzik Brown 2017-03-22 08:35:56 UTC
Description of problem:
As described in https://bugzilla.redhat.com/show_bug.cgi?id=1431992 
By default puppet-opendaylight adds the upstream repository to the OpenDaylight controller node.
When using Redhat Openstack the repository that includes OpenDaylight is already set.
We need to disable the creation of the upstream repository

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-6.0.0-0.20170307170102.3134785.0rc2.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2017-03-22 08:38:12 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 4 Itzik Brown 2017-08-03 10:37:08 UTC
Verified with openstack-tripleo-heat-templates-7.0.0-0.20170721174554.el7ost.noarch.

Comment 7 errata-xmlrpc 2017-12-13 21:20:39 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/RHEA-2017:3462