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.
This looks to be more of an issue with the gluster server refusing the connection (most likely independent of the format type).
Did the qcow2 image actually get created? That looks to be a warning/error printed out by gfapi.
I am only able to replicate this in this manner:
let i=0
while [ 1 ]
do
let i=i+1
echo "creating test${i}.qcow2"
./qemu-img create -f qcow2 gluster://192.168.15.2/gv0/test${i}.qcow2 10M
echo $?
done
In that above scenario, I would get the same error message occasionally. However, despite the error/warning message, in each instance the numbered test image was actually created successfully on the server.
Re-assigning to gluster.
*** Bug 1151731 has been marked as a duplicate of this bug. ***
Comment 5Prasanna Kumar Kalever
2016-09-18 18:55:21 UTC
Looks like this is very old issue, came into my eyes.
Request to try out with the latest gluster releases and see if this is still reproducible. IMO this bug no more exist now.
But will wait for a couple of weeks before closing this BUG, to see if someone has any objections.
Comment 6Prasanna Kumar Kalever
2016-09-18 18:55:47 UTC
Looks like this is very old issue, came into my eyes.
Request to try out with the latest gluster releases and see if this is still reproducible. IMO this bug no more exist now.
But will wait for a couple of weeks before closing this BUG, to see if someone has any objections.
Comment 7Prasanna Kumar Kalever
2019-10-15 08:41:01 UTC