Bug 1488728

Summary:	Open provider and keystone ports in firewalld
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Mor <mkalfon>
Component:	provider	Assignee:	Leon Goldberg <lgoldber>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mor <mkalfon>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.0.4	CC:	bugs, danken, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:55:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1432354

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.