Bug 997107 - nova image-create doesn't exit with nonzero when failed to upload to swift
Summary: nova image-create doesn't exit with nonzero when failed to upload to swift
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-novaclient
Version: 3.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: 6.0 (Juno)
Assignee: Jakub Ruzicka
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-14 16:59 UTC by Jaroslav Henner
Modified: 2019-09-09 13:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-16 15:06:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Henner 2013-08-14 16:59:17 UTC
Created attachment 786618 [details]
client debug

Description of problem:
When snapshot creation fails somewhere in the middle of creating the snapshot, glance 4 polling mode exits with status 0.

Version-Release number of selected component (if applicable):
openstack-glance-2013.1.2-1.el6ost.noarch

How reproducible:
1/10

Steps to Reproduce:
It is not easy to reproduce, what I did was:

1. nova --debug image-create --poll '4b1317d3-71b5-4f4a-8ea5-b2e2f529da43' 'mirage_rhel-6.4-preinstalled'
2. There was some error when glance was saving data to swift.
3.

Actual results:
echo $?
0

Expected results:
echo $?
non-zero

Additional info:

Comment 4 Jaroslav Henner 2014-04-22 09:58:26 UTC
The problem when saving trough glance to swift should probably be reproducible by changing the node_timeout in /etc/swift/proxy-server.conf to some low value, like 1.

Comment 5 Flavio Percoco 2014-05-23 05:45:55 UTC
This sounds more like a novaclient error than a glanceclient error (assuming glanceclient is raising an exception)

Comment 6 Jaroslav Henner 2014-05-23 06:02:29 UTC
Yeah maybe I was mistaken by seeing the word "glance" in the traceback.

Comment 7 Sahid Ferdjaoui 2015-12-16 15:06:13 UTC
This issue has been reported on a EOL version of OSP and do not get any activities. Please feel fre to reopen whether that issue is still happening on current releases.

Thanks,
s.


Note You need to log in before you can comment on or make changes to this bug.