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.

Problem Description:
Define tests, including gating tests, for virt-v2v.

Additional Information:
In RHEL-8 and in RHEL AV, the virt module contains the definition of tests to be run whenever any component in the module is changed. In RHEL-9 there is no virt module so the tests must now be defined for each of the individual components, of which virt-v2v is one. The definition must include both gating and non-gating tests.

The suggested approach to resolving this BZ is to copy the test setup for the virt module in RHEL AV-8.5, namely the file named 'gating.yaml' and the directory named 'tests'. Then modify the files to exclude tests and gating tests that are not relevant for virt-v2v.

Please work closely with QE! The test definitions in gating.yaml describe test jobs that run in QE's testing environment. The test jobs and/or the testing environment may need to be modified to work in RHEL-9, or perhaps brand new test jobs may need to be created.

Delegating for further assignment.

I don't expect maintainers to do all the work, but to help move things along.

Please work with the following:

* Yash - he knows how to create the test and gating files that OSCI reads to run tests. He also knows how the QE test systems work.

* lead engineer for the component (I'll help if you don't know who) - for reviewing what tests make sense to run for the component.

* QE assignee - for verifying that the jobs we run which execute on QE's infrastructure will run on RHEL-9 in a non-modular environment. I expect that some tests may need modification.

Moving to rjones as the maintainer of the virt-v2v package.

The case name should be 'libvirt-ci.v2v.brew-build.gating.x86_64.tier1.functional'.

Downstream test commit:

https://gitlab.com/redhat/centos-stream/rpms/virt-v2v/-/commit/024316f718536d6c9a96268f5a4815dfc500de61

OSCI tests dashboard:

https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/37423645

v2v gating result is PASS. This bug is fixed.
https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/37423645