Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oc cluster up dns will not work OOTB on firewalld-enabled fedora #11949

Closed
maci0 opened this issue Nov 17, 2016 · 1 comment
Closed

oc cluster up dns will not work OOTB on firewalld-enabled fedora #11949

maci0 opened this issue Nov 17, 2016 · 1 comment
Assignees
Labels
component/composition kind/bug Categorizes issue or PR as related to a bug. priority/P2

Comments

@maci0
Copy link

maci0 commented Nov 17, 2016

The internal service name resolution fails when using a cluster set up by
oc cluster up on a F25 system which is firewqalld-enabled

Happens with both origin 1.3.1 and OCP 3.1.3

If I stop firewalld and restart docker and recreate the oc cluster it will work fine.

@pweil- pweil- added component/composition kind/bug Categorizes issue or PR as related to a bug. priority/P2 labels Nov 17, 2016
@csrwng
Copy link
Contributor

csrwng commented Feb 6, 2017

Instructions have now been added to the doc for the rules you need for cluster up.
(step 3 here: https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#linux)

In addition, now cluster up performs a check on startup to see if this access is not allowed.

@csrwng csrwng closed this as completed Feb 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/composition kind/bug Categorizes issue or PR as related to a bug. priority/P2
Projects
None yet
Development

No branches or pull requests

3 participants