Bug 1769331 - [OSP] Port conflict between coredns and CNO
Summary: [OSP] Port conflict between coredns and CNO
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.3.0
Assignee: Mike Fedosin
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks: 1764672
TreeView+ depends on / blocked
 
Reported: 2019-11-06 12:09 UTC by Mike Fedosin
Modified: 2020-01-23 11:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:11:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:11:34 UTC

Description Mike Fedosin 2019-11-06 12:09:51 UTC
Description of problem:
For OpenStack port 8080 is used by cluster-network-operator in 4.3, so we can't deploy a cluster because of the conflict with coredns:

error listening on :8080: listen tcp :8080: bind: address already in use

How reproducible:
Always


Steps to Reproduce:
1. Deploy a cluster as usual, wait for the error in CNO
2. oc get pods -т 


Actual results:
Cluster deployment fails.


Expected results:
Cluster deployment is completed successfully.

Comment 1 Mike Fedosin 2019-11-06 12:14:47 UTC
This bug was fixed a month ago, we need this BZ just to backport the fix to 4.2.z
https://github.com/openshift/machine-config-operator/pull/1164

Comment 3 errata-xmlrpc 2020-01-23 11:11:16 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/RHBA-2020:0062


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