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:
The virsh command domjobinfo returns 1 on success if there is no job.

Version-Release number of selected component (if applicable):
upstream, libvirt-1.1.1-4.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. virsh start domain
2. virsh domjobinfo domain

Actual results:
Job type:         None

echo $? -> 1

Expected results:
Job type:         None

echo $? -> 0

Fixed upstream by v1.1.2-107-gf084caa:

commit f084caae7c5db8ae03e7fafce164c73f65681843
Author: Jiri Denemark <jdenemar>
Date:   Wed Sep 11 15:49:48 2013 +0200

    virsh domjobinfo: Do not return 1 if job is NONE
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1006864
    
    Commit 38ab1225 changed the default value of ret from true to false but
    forgot to set ret = true when job is NONE. Thus, virsh domjobinfo
    returned 1 when there was no job running for a domain but it used to
    (and should) return 0 in this case.

This patch is VERIFIED.

Package used:
libvirt-1.1.1-5.el7.x86_64

Verifying steps:

# virsh domjobinfo <domain>
Job type:         None        
# echo $?
0

In comparison with returning value 1 in
libvirt-1.1.1-4.el7.x86_64

So consider this VERIFIED.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.