cinder-backup restore process ends unexpectedly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Confirmed
|
Medium
|
MOS Maintenance |
Bug Description
Performing volume restore from backup, cinder-backup unexpectedly got this:
>Exception during message handling: IncompleteRead(
with the following traceback:
Traceback (most recent call last):
File "/usr/lib/
incoming.
File "/usr/lib/
return self._do_
File "/usr/lib/
result = getattr(endpoint, method)(ctxt, **new_args)
File "/usr/lib/
return f(*args, **kwargs)
File "/usr/lib/
{'status': 'available'})
File "/usr/lib/
six.
File "/usr/lib/
backup_service)
File "/usr/lib/
return f(*args, **kwargs)
File "/usr/lib/
backup_
File "/usr/lib/
restore_
File "/usr/lib/
(resp, body) = self.conn.
File "/usr/lib/
response_
File "/usr/lib/
rv = func(self.url, self.token, *args, **kwargs)
File "/usr/lib/
object_body = resp.read()
File "/usr/lib/
data = self._fp.read()
File "/usr/lib/
Swift acts as cinder-backup backend, but to my surprise I didn't find anything related to errors or connection drop in swift-object-server and swift-proxy server service log. Network flaps were not noticed also, and no other services experienced connectivity issues.
If it's not cinder-backup's fault, I'd like to see as many details as possible from cinder in this situation.
Changed in mos: | |
status: | New → Incomplete |
Danil, could you please provide more data? Steps to reproduce, logs, anything? So for it doesn't look solvable.