Bug 1509000

Summary:	Ansible can't deploy on the active firewall from inside the internal vlan
Product:	[Community] GlusterFS	Reporter:	M. Scherer <mscherer>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-27 11:42:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description M. Scherer 2017-11-02 16:18:31 UTC

Description of problem:

since moving ansible bastion to the internal vlan, ansible can't connect to either masa or mune, depending on which is the active firewall at the time.

I suspect the firewall rules or something network related is broken, but no time to investigate right now, hence a ticket

Comment 1 M. Scherer 2017-11-02 16:40:58 UTC

In the mean time, I switched to 172.24.1.254 (IT gateway) for now.

Comment 2 M. Scherer 2018-06-28 13:08:18 UTC

seems to be solved.