| Summary: | [RFE]Ceph/RBD block driver for qemu-kvm : change error_setg() to error_setg_errno() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vikhyat Umrao <vumrao> | ||||||
| Component: | qemu-kvm-rhev | Assignee: | Jeff Cody <jcody> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | jingzhao <jinzhao> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.2 | CC: | chayang, huding, jcody, jdillama, jdurgin, jinzhao, juzhang, knoel, michen, mrezanin, sherold, virt-maint | ||||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | qemu-kvm-rhev-2.6.0-11.el7 | Doc Type: | Enhancement | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-11-07 21:05:28 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Vikhyat Umrao
2016-04-22 12:45:12 UTC
Created attachment 1149750 [details]
upstream patch in mater branch of qemu
(In reply to Vikhyat Umrao from comment #1) > Created attachment 1149750 [details] > upstream patch in mater branch of qemu I am planning to send this patch as given in comment#1. Please let me know your inputs. Created attachment 1149969 [details] upstream patch in master branch of qemu Got some feedback from my Ceph RBD team. Uploading new patch set. Please ignore comment#1 patch. Upstream Patch V2 : http://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg01071.html Fix included in qemu-kvm-rhev-2.6.0-11.el7 Hi jeff Could you share detailed steps with QE? Thanks Jing Zhao Hi Jing Zhao, Yes - the difference is in the error reporting. An easy way to reproduce is with an invalid qemu-img create: Prior to the patch: # qemu-img create -f qcow2 rbd:foo/bar 10M [...] qemu-img: rbd:foo/bar: error connecting After the patch: # qemu-img create -f qcow2 rbd:foo/bar 10M [...] qemu-img: rbd:foo/bar: error connecting: No such file or directory Hi Jeff
Following is the my test result. Could you help check.
[root@ibm-x3100m4-02 ceph]# ceph osd lspools
0 rbd,1 libvirt-pool,
[root@ibm-x3100m4-02 ceph]# service ceph status
=== mon.ibm-x3100m4-02 ===
mon.ibm-x3100m4-02: running {"version":"0.94.9"}
=== osd.0 ===
osd.0: running {"version":"0.94.9"}
=== osd.1 ===
osd.1: running {"version":"0.94.9"}
1.Reproduce on qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64
[root@localhost ~]# qemu-img create -f raw rbd:libvirt-pool1/1.qcow2:mon_host=10.66.144.26 1G
qemu-img: rbd:libvirt-pool1/1.qcow2:mon_host=10.66.144.26: Unknown protocol 'rbd'
[root@localhost ~]# qemu-img create -f qcow2 rbd:libvirt-pool/1.qcow2:mon_host=10.66.144.26 1G
qemu-img: rbd:libvirt-pool/1.qcow2:mon_host=10.66.144.26: Unknown protocol 'rbd'
2. Test it on qemu-kvm-rhev-2.6.0-22.el7.x86_64
[root@jinzhao bug]# qemu-img create -f raw rbd:libvirt-pool1/1.qcow2:mon_host=10.66.144.26 1G
Formatting 'rbd:libvirt-pool1/1.qcow2:mon_host=10.66.144.26', fmt=raw size=1073741824
qemu-img: rbd:libvirt-pool1/1.qcow2:mon_host=10.66.144.26: error opening pool libvirt-pool1: No such file or directory
[root@jinzhao bug]# qemu-img create -f qcow2 rbd:libvirt-pool/2.qcow2:mon_host=10.66.144.26 1G
Formatting 'rbd:libvirt-pool/2.qcow2:mon_host=10.66.144.26', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
qemu-img: rbd:libvirt-pool/2.qcow2:mon_host=10.66.144.26: Could not write qcow2 header: Invalid argument
Is it verified?
Thanks
Jing Zhao
Jeff, any comments for comment 13? Thanks Jing Zhao (In reply to jingzhao from comment #14) > Jeff, any comments for comment 13? > > Thanks > Jing Zhao Hi Jing, Yes, this looks verified to me. Thanks! 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://rhn.redhat.com/errata/RHBA-2016-2673.html |