Description of problem:
When trying to launch an instance with a big image (3.7gb), openstack-swift-proxy went to inactive or failed state - everytime. This did not happen as frequently for smaller images - although it often did.
Steps to Reproduce:
1. Deploy Overcloud
2. Check if openstack-swift-proxy is up
3. Upload image with glance (preferably an image with more than 1gb)
4. Start instance launch with image from #3
Instance goes to Error state and openstack-swift-proxy service is down
Instance is launched successfully and openstack-swift-proxy service is still up.
For me, what solved this issue was to remove proxy-logging from the pipeline in swift's proxy-server.conf
pipeline = catch_errors healthcheck cache ratelimit tempurl formpost authtoken keystone staticweb proxy-logging proxy-server
pipeline = catch_errors healthcheck cache ratelimit tempurl formpost authtoken keystone staticweb proxy-server
Bug was addressed and fixed upstream - backported to mitaka and liberty
This bug was reportedly fixed in master; moving to POST state rather than NEW, as it will automatically be included in RHOS 10.
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.