Bug 1488728 - Open provider and keystone ports in firewalld
Summary: Open provider and keystone ports in firewalld
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider
Version: 1.0.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Leon Goldberg
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks: 1432354
TreeView+ depends on / blocked
 
Reported: 2017-09-06 06:38 UTC by Mor
Modified: 2017-12-20 10:55 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.2.0-0.0.master.20170912134930.gitc81ca84.el7.centos.noarch.rpm
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:55:15 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)

Description Mor 2017-09-06 06:38:35 UTC 
Description of problem:
To allow external clients, such as testing machine or CloudForms to interact with ovirt-provider-ovn that is usually installed on the oVirt engine, the ports 9696/tcp (provider) and 35357/tcp (Keystone) needs to be open in firewalld.

Version-Release number of selected component (if applicable):
Version 4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Install oVirt and OVN using engine-setup.

Actual results:
Ports 9696 and 35357 are not opened.

Expected results:
Should be opened.
Comment 1 Mor 2017-09-14 06:31:50 UTC 
Verified on:
ovirt-engine-4.2.0-0.0.master.20170912134930.gitc81ca84.el7.centos.noarch

Please do not forget to attach the relevant patch.
Comment 2 Sandro Bonazzola 2017-12-20 10:55:15 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.