[glance][openstack-ansible] Snapshots disappear during saving

Oliver Wenz oliver.wenz at dhbw-mannheim.de
Mon Mar 22 09:21:32 UTC 2021


Hi Dmitriy,
thanks for your answer! Yes, we do use swift and its use as glance backend is
intentional.

I got the following from the swift-proxy-server logs in the swift container on
the infra host after taking a snapshot:

Mar 22 08:43:43 infra1-swift-proxy-container-27169fa7 proxy-server[87]: Client
disconnected without sending last chunk (txn:
txa7c64547baf0450eb0034-006058588b) (client_ip: 192.168.110.
106)
Mar 22 08:43:43 infra1-swift-proxy-container-27169fa7 proxy-server[87]:
192.168.110.106 192.168.110.211 22/Mar/2021/08/43/43 PUT
/v1/AUTH_024cc551782f41e395d3c9f13582ef7d/glance_images/3ec63ec2-aa3b-4c3b-a904-b55d1a6ec878
-00001 HTTP/1.0 499 - python-swiftclient-3.10.1 gAAAAABgWFiKMz9R... 204800000 89
- txa7c64547baf0450eb0034-006058588b - 52.2991 - - 1616402571.623875856
1616402623.922997952 0

On the swift host some services logs contain errors. E.g. the
swift-container-updater service:

Mar 22 08:42:19 bc1bl12 systemd[1]: swift-container-updater.service: Main
process exited, code=exited, status=1/FAILURE
Mar 22 08:42:19 bc1bl12 systemd[1]: swift-container-updater.service: Failed with
result 'exit-code'.
Mar 22 08:42:21 bc1bl12 systemd[1]: swift-container-updater.service: Scheduled
restart job, restart counter is at 162982.
Mar 22 08:42:21 bc1bl12 systemd[1]: Stopped swift-container-updater service.
Mar 22 08:42:21 bc1bl12 systemd[1]: Started swift-container-updater service.
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: Traceback (most recent
call last):
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:   File
"/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py",
line 803, in config_fallocate_value
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:     reserve_value =
float(reserve_value[:-1])
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: ValueError: could not
convert string to float: '1%'
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: During handling of the
above exception, another exception occurred:
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: Traceback (most recent
call last):
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:   File
"/openstack/venvs/swift-22.1.0/bin/swift-container-updater", line 23, in
<module>
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:
    run_daemon(ContainerUpdater, conf_file, **options)
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:   File
"/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/daemon.py",
line 304, in run_daemon
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:
    utils.config_fallocate_value(conf.get('fallocate_reserve', '1%'))
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:   File
"/openstack/venvs/swift-22.1.0/lib/python3.8/site-packages/swift/common/utils.py",
line 809, in config_fallocate_value
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]:     raise
ValueError('Error: %s is an invalid value for fallocate'
Mar 22 08:42:22 bc1bl12 swift-container-updater[50699]: ValueError: Error: 1%%
is an invalid value for fallocate_reserve.

The same exit-code and traceback shows in the logs of swift-container-auditor,
swift-account-auditor and swift-account-reaper services. Does this tell you
anything useful?

We didn't experience any problems when uploading files to containers, only when
taking snapshots of instances.

Kind regards,
Oliver


> ------------------------------
> 
> Message: 4
> Date: Thu, 18 Mar 2021 12:44:47 +0200
> From: Dmitriy Rabotyagov <noonedeadpunk at ya.ru>
> To: "openstack-discuss at lists.openstack.org"
> 	<openstack-discuss at lists.openstack.org>
> Subject: Re: [glance][openstack-ansible] Snapshots disappear during
> 	saving
> Message-ID: <374941616064157 at mail.yandex.ru>
> Content-Type: text/plain; charset=utf-8
> 
> Hi Olver,
> 
> Am I right that you're also using OpenStack Swift and it's intentional to
> store images there?
> Since the issue is related to the upload process into the Swift. So also
> checking Swift logs
> be usefull as well.
> 



More information about the openstack-discuss mailing list