Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Goal:
* Define tests, including gating tests, for virt-p2v
Additional Information:
Some components have tests defined in RHEL8 but those tests are not present in RHEL9
The definition must include both gating and non-gating tests.
The suggested approach to resolving this BZ is:
1) check if this component is still present in RHEL9;
* [http://file.rdu.redhat.com/~asamalik/content-set/rhel8-vs-rhel9-components.html]
2) check if there are already any test case for this individual component on RHEL9;
3) If not, check if the test is present in RHEL8 and copy `gating.yaml` file and `tests directory` to RHEL9 repo;
* [https://gitlab.com/redhat/centos-stream/rpms/virt-p2v]
4) If not present, create some tests (including gating) for this component.
Please work closely with QE (but keep in mind that they might be busy with the mass migration) or any other team that is maintaining those tests. The test definitions in `gating.yaml` describe test jobs that run in a CI 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.
For more information watch [Alexandra's presentation|https://drive.google.com/file/d/1p9OAfUIbYONFQJeRoX9FoCf-0X-FnHVl/view] on this topic (after min 13).
If you have any questions here, please ask me or @yash.
Comment 1Klaus Heinrich Kiwi
2021-08-24 18:19:08 UTC
Any updates here?
Comment 2Richard W.M. Jones
2021-08-24 20:00:58 UTC
virt-p2v isn't a package as such in RHEL. It's an ISO. From RHEL 9
we decided that it was so troublesome to get EXD to make this package
that we'd just distribute it ourselves from the upstream site.
However I haven't built it yet.
As such we don't care much about gating tests, but also I want to
keep this bug around because we may need the virt-p2v package in
RHEL (or may not, unclear).
Comment 5Richard W.M. Jones
2021-09-01 08:41:19 UTC
As a general rule of thumb, unless a bug is so serious
that it causes something to completely fail, we should
move any RHEL 9 Beta bug to RHEL 9.
In this case it's a gating test, and for a package that
we don't really ship yet (we will eventually ship it
separately from RHN), so I've moved it to RHEL 9.
Comment 7Richard W.M. Jones
2022-01-12 16:03:50 UTC
Moving to 9.1 because we're still not in a position to release virt-p2v
in RHEL 9.
Comment 9Richard W.M. Jones
2022-05-19 07:46:03 UTC
Putting this on the backlog.
We don't need virt-p2v in RHEL 9 right at the moment, because we're
building and shipping the package ourselves. But once we switch to
using Image Builder (which requires some other work to be done first)
we'll use this package again. We can worry about gating tests then.
We've made progress on bug 2038105, but we haven't decided on the delivery method yet. Marking this one as "Devel Cond-NAK: Design" for the time being.
(BTW, "docs/p2v-hacking.pod" names a local test that I think is non-interactive, and therefore could be used as a gating test:
$ make run-virt-p2v-non-gui-conversion
)
Comment 11Richard W.M. Jones
2022-05-27 07:54:12 UTC
FYI here is the gating test used for virt-v2v (mainly to show how this gating
test thing is done):
https://gitlab.com/redhat/centos-stream/rpms/virt-v2v/-/blob/c9s/gating.yamlhttps://gitlab.com/redhat/centos-stream/rpms/virt-v2v/-/tree/c9s/tests
(Yes, it uses its own dialect of yaml. No, they told us they won't fix that)
I think the bigger problem here (and a good reason to defer fixing this for
now) is that we don't have a good understanding of what the packaging
of virt-p2v needs to look like in RHEL. Will we have a "virt-p2v" package at all?
Should it have a different name? If so, will it be in BuildRoot or CRB? How will
we stop customers from trying to run it directly and point them at the ISO /
Image Builder?
All of these answers will change when we eventually switch to using Image Builder.
Comment 12Klaus Heinrich Kiwi
2022-08-03 13:32:12 UTC
(In reply to Laszlo Ersek from comment #10)
> We've made progress on bug 2038105, but we haven't decided on the delivery
> method yet. Marking this one as "Devel Cond-NAK: Design" for the time being.
>
> (BTW, "docs/p2v-hacking.pod" names a local test that I think is
> non-interactive, and therefore could be used as a gating test:
>
> $ make run-virt-p2v-non-gui-conversion
> )
Hi Laszlo,
are we maybe closer to moving this out of our backlog and start planning around it?
Comment 19Richard W.M. Jones
2022-08-03 16:42:01 UTC
Remove TestOnly temporarily for reasons.
Comment 20Richard W.M. Jones
2022-08-03 16:51:01 UTC
Re-add TestOnly for reasons.
Comment 24Richard W.M. Jones
2022-08-03 17:18:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (virt-p2v bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:8228