Bug 1549227 – OpenDaylight binds to default port, even when alternate REST port specified

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1549227 - OpenDaylight binds to default port, even when alternate REST port specified

Summary:	OpenDaylight binds to default port, even when alternate REST port specified

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	puppet-opendaylight (Show other bugs)
Sub Component:
Version:	13.0 (Queens)
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	beta
Target Release:	13.0 (Queens)
Assigned To:	Tim Rozet
QA Contact:	Tomas Jamrisko
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-02-26 13:36 EST by Tim Rozet
Modified:	2018-10-18 03:22 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	puppet-opendaylight-7.0.0-0.20180216174117
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:	N/A
Last Closed:	2018-06-27 09:45:51 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
OpenDaylight Bug	INTPAK-140	None	None	None	2018-02-26 13:38 EST
OpenDaylight gerrit	68776	None	None	None	2018-02-26 13:39 EST
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:46 EDT

Groups: None (edit)

Description Tim Rozet 2018-02-26 13:36:17 EST

Description of problem:
When ODL is configured to bind to a specific port (for example 8081 in TripleO), the Pax web server is also still configured to listen on 8181 (default port).

Comment 11 errata-xmlrpc 2018-06-27 09:45:51 EDT

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-2018:2086

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