Bug 1290987

Summary:	Problem with "--timeout" option
Product:	Red Hat Enterprise Linux 7	Reporter:	Pryanick <matrosik7>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	qe-baseos-daemons
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.0	CC:	matrosik7, psutter, todoleza
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-26 16:40:07 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 Pryanick 2015-12-12 13:13:24 UTC

Description of problem:

Hello!
The "timeout" option works different on physical host and VM.
On physical host "firewall-cmd --add-service=http --timeout=10" works fine.
But inside VM the same command does not count 10 seconds. It adds rule just on few seconds (2-3) and reset it...

Comment 2 Thomas Woerner 2016-01-12 12:19:03 UTC

Is the time in the VM synchronized?

Comment 3 Phil Sutter 2017-06-26 16:40:07 UTC

Hi,

(In reply to Pryanick from comment #0)
> Description of problem:
> 
> Hello!
> The "timeout" option works different on physical host and VM.
> On physical host "firewall-cmd --add-service=http --timeout=10" works fine.
> But inside VM the same command does not count 10 seconds. It adds rule just
> on few seconds (2-3) and reset it...

This ticket did not receive any update for a long time despite the needinfo flag. I therefore assume it was resolved externally and is no longer valid. In case my assumption is wrong, please feel free to reopen and provide further details.

Thanks, Phil

Comment 4 Red Hat Bugzilla 2023-09-14 03:14:41 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days