[6.14.z] Test CV incremental update & publish time

[Satellite-QE]

Cherrypick of PR: #14749

Problem Statement

Implement backlogged desired coverage - PR #9991 , authored by @latran

Solution

• Automation for incremental update duration coverage, for BZ 2117760 and BZ 1829266

• Steps:

  • On an existing CV with decent amount of content, perform incremental update with only one errata.
  • Publish the entire content view.
  • Expect: The duration of the incremental update should almost always be shorter than the CV publish. To cover the BZs fully, if the update does take longer, check that it was close, that update did not take significantly longer.

• Original issue raised in BZs: CV publish would only take a few minutes as expected, but incremental update with one or a couple errata was taking over an hour.

• timeout (to catch any future performance degradation) - for incr. update is 20 seconds,
  for publish of CV timeout is 30 seconds, based on prt performance.
  Includes logging duration for both incr. update and cv publish.

PRT case

trigger: test-robottelo
pytest: tests/foreman/longrun/test_inc_updates.py::test_positive_incremental_update_time

[Satellite-QE]

trigger: test-robottelo
pytest: tests/foreman/longrun/test_inc_updates.py::test_positive_incremental_update_time

[Satellite-QE]

PRT Result

Build Number: 6567
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/longrun/test_inc_updates.py::test_positive_incremental_update_time --external-logging
Test Result : ================= 1 passed, 14 warnings in 1020.55s (0:17:00) ==================