[CompEval] API modifications for errata-management

[damoore044]

Problem Statement

API errata has several outdated tests to be modified, combined, or removed for component evaluation.
8-12 consistent failures in 6.15.0 CI, most in setup of hosts, errata/packages, or necessary components.

Solution

• Updated hosts to register with global registration.

• rhel8 hosts using rh repos and packages for rhel8, setup_content fixture now using the same.

• Combine the following view, sort, and filter scenarios per comp-eval, into just test_positive_list_sorted_filtered:
  test_positive_list - test_positive_list_updated - test_positive_sorted_issue_date_and_filter_by_cve

• Helper method to api publish & promote a content-view,
  wait for task(s) after content-view.publish()

• Fix api_factory method wait_for_errata_applicability_task, which was using an old search format to find applicability tasks.

• Propose marking the following as an End-to-End test, as it touches all components needed for errata,
  and performs a common and critical customer use-case; of installing errata to hosts in host collection:
  test_positive_install_in_hc[rhel params for 7, 8, 9]

• test_apply_modular_errata_using_default_content_view: Removed this outdated test case-
  as the DefaultCV cannot be edited, published, promoted etc. A follow up introduction could cover this
  with a test_negative scenario.

Prior Failures - Resolved

• test_errata_installation_with_swidtags : Unsure if we can use some other module_repos_collection ,
  that does not touch module_entitlement_manifest_org? output below :
  Passing, I made a new fixture: function_repos_collection_with_manifest in fixtures>repository.py, using function_sca_manifest_org.

PRT Case

trigger: test-robottelo
pytest: tests/foreman/api/test_errata.py

[damoore044]

Last Build [5430] vs 6.15.0 CI - Jan 18, 2024, 2:17 PM

Pass: 12 [+6]
Skip: 0
Fail: 0 [-9]

Total: 12 vs 15 (3 sorting tests were merged intotest_positive_list_sorted_filtered)

• Removed outdated test scenario test_apply_modular_errata_using_default_content_view .

[JacobCallahan]

Just a few other things

[vijaysawant]

Few suggestions only, no blocker.

[jyejare]

@damoore044 If the test failure is due to product changes, feel free to remove it and for the negative test that you wanted to do, add a new test for it!

This way in reporting tools new test will be removed and new tests would be added with unique id!

Also, the change is applicable for all zstream versions ? if yes, please raise a separate PR for this change and we will merge this PR with single failure :)

[damoore044]

@jyejare From discussing with the QE team, we can remove this outdated test test_apply_modular_errata_using_default_content_view , and supporting fixtures in this module,
I will circle back for a new test_negative scenario as part of continuous improvements.
Would that be appropriate to satisfy requirements here?

[damoore044]

@jyejare From local testing, this MR will be good to cherry-pick into 6.15.z, 6.14.z.
Can we try auto-CP with prt run for each ystream mr?

[jyejare]

@damoore044 agree with merging this PR with removing that test case.

Also add cherrypick labels for branches and a cherrypick label itself for auto CP.

[vsedmik]

Looks good, in PRT all tests passed. Left just one non-blocking nitpick comment but I think we are good to merge.

Good work @damoore044!

[damoore044]

trigger: test-robottelo
pytest: tests/foreman/api/test_errata.py