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.
(In reply to comment #3)
> Test this bug with :
> Client : libvirt-0.9.8-1.el6.x86_64
> Server: libvirt-0.9.3-2.el6.x86_64
>
>
> Client :
>
> # gcc -o foo foo.c -lvirt
>
>
> # ./foo qemu+ssh://10.66.5.12/system /tmp/
> root.5.12's password:
> libvir: RPC error : unknown procedure: 235
> success
>
The fact that the error message states "unknown procedure" instead of "this function is not supported by the connection driver" may mean that we have a regression in error reporting quality. The code in virterror.c for VIR_ERR_NO_SUPPORT should prefer the latter message, although I haven't tested whether older versions of libvirt (preferably both server and client older than 0.9.2, before our RPC rewrite) actually used this message on encountering an unknown RPC call. I'm reopening this, so that we can investigate whether there really is an issue in poor error message quality.
Eric & all,
what you are describing is not a bug IMHO. This API from the example was introduced in 0.9.4; So if we are talking to any previous daemon we have to receive "unknown procedure" as the procedure really not known. The VIR_ERR_NO_SUPPORT is used in cases where the procedure is known, however not implemented in driver yet. E.g. virDomainSaveImageGetXMLDesc is implemented only for qemu, so issuing this api against say virtual box or xen driver (and 0.9.4+ daemon of course) will gain VIR_ERR_NO_SUPPORT.
Server version:
v0.9.1 - success
v0.9.2 - success
v0.9.3 - success
v0.9.4 - error: libvir: QEMU error : operation failed: cannot read domain image
However, trying different driver (LXC):
libvir: error : this function is not supported by the connection driver: virDomainSaveImageGetXMLDesc
success
The question is not whether the error is tagged VIR_ERR_NO_SUPPORT, but whether the error message has regressed in quality. That is, if 0.8.0 talking to 0.7.0 and calling an unknown function reported "this function is not supported by the connection driver", while 0.9.4 talking to 0.9.2 gets "unknown procedure: NNN", we've made the reporting worse over time.
(In reply to comment #9)
> I still don't think this is a bug. We've fixed the error code; But even for
> older version we've always reported "unknown procedure: NNN".
Given that, I think we've confirmed that the behavior is unchanged, so I'm closing as NOTABUG.