RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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...

Is the time in the VM synchronized?

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

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