Bug 1700695

Summary:	smoke is failing for build https://review.gluster.org/#/c/glusterfs/+/22584/
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, dkhandel, gluster-infra, mscherer
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:	2019-04-17 08:27:48 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 Mohit Agrawal 2019-04-17 07:53:00 UTC

Description of problem:
Smoke is failing for build https://review.gluster.org/#/c/glusterfs/+/22584/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Deepshikha khandelwal 2019-04-17 08:27:48 UTC

Correct set of the firewall was not applied after reboot.

Misc fixed it.

Comment 2 M. Scherer 2019-04-17 09:37:09 UTC

yeah, freebsd was still using chrono, the test firewall (I did set it up for the migration to nftables). For some reason, that firewall (that I almost decomissioned yesterday) do not seems to route packet anymore. The rules are in place, the config is the same as the 2 prod firewall. 

We need also some better monitoring for that.