Project

General

Profile

Actions
Copy link

Feature #31628

closed

Change the default hammer timeout

Added by Dominik Matoulek over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Hammer core
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
1849232
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1849232

Description of problem:
With the default hammer timeout, some reports will fail once we are seeing huge environments.

How reproducible:
100%

Steps to Reproduce:
1. Create a huge # of content hosts
2. Generate some reports that consume more time, for example, "Applicable errata"
3.

Actual results:
If spend more the 2 min (120 seconds) will fail

Expected results:
no issue and result quickly

Additional info:

Actions
Copy link
 #1

Updated by Dominik Matoulek over 3 years ago

  • Subject changed from Change the default hammer timeout to Change the default hammer timeout
  • Category changed from Reporting to Hammer core
  • Triaged changed from No to Yes
Actions
Copy link
 #2

Updated by Oleh Fedorenko about 3 years ago

  • Status changed from New to Closed

Closing this one, please see BZ to get more info.

Actions
Copy link

Also available in: Atom PDF