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.

Description of problem:

QEMU added job-finalize and job-dismiss for jobs to allow libvirt more explicit control over when and how graphs get manipulated. However, this functionality was only exposed for the backup job.

Libvirt needs this for ALL jobs.

Version-Release number of selected component (if applicable):

2.12.0, 7.6's version


How reproducible:

100%; the options are not present in QAPI

Steps to Reproduce:
1. Try to use auto-dismiss or auto-finalize parameters for the mirror, commit, or stream jobs
2. Weep

Actual results:

Wailing, gnashing of teeth

Expected results:

auto-finalize = false should allow jobs to sit in the PENDING state until the job-finalize command is sent to instruct them to perform their graph changes.

auto-dismiss = false should allow jobs to sit in the CONCLUDED state until they are dismissed with the job-dismiss command, which allows libvirt a chance to query their completion state in case libvirt missed the completion event.

Additional info:

-

Pt 1/2 https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg06188.html
Pt 2/2 https://lists.gnu.org/archive/html/qemu-devel/2018-09/msg00647.html

Pt 1/2 staged https://git.xanclic.moe/XanClic/qemu/commits/branch/block
Pt 2/2 pending [...]

Fix included in qemu-kvm-rhev-2.12.0-15.el7

Created attachment 1483321 [details]
Test_logs_for_the_block_jobs-withAutoFinalizeDismiss-NewCommands-09142018

Verify the bug with both old and new block job related commands.

Created attachment 1483322 [details]
Test_logs_for_the_block_jobs-withAutoFinalizeDismiss-OldCommands-09142018

The qemu version for the verification is qemu-kvm-rhev-2.12.0-15.el7.x86_64.

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, 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-2018:3443