all-in-one overcloud with Glance + RBD: image upload hangs forever

Bug #1621467 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Emilien Macchi

Bug Description

I'm currently adding Ceph to tripleo/scenario001 CI job and configure Nova, Glance and Gnocchi to use RBD backend.
The pingtest fails to upload an image to Glance: it hangs forever and timeout (at the time of the HAproxy value, 1 minute by default). I tried to increase the HAproxy timeout to 1h30 but it doesn't help, I've got same results where it timeouts after 1h30.

I can see the image upload in Glance logs and I see zero error in logs.

This is the client trying to upload an image and timeout:
http://logs.openstack.org/12/366812/3/check/gate-tripleo-ci-centos-7-scenario001-multinode-nv/ed56d11/console.html#_2016-09-08_05_26_44_159354

Glance API logs:
http://logs.openstack.org/12/366812/3/check/gate-tripleo-ci-centos-7-scenario001-multinode-nv/ed56d11/logs/subnode-2/var/log/glance/api.txt.gz#_2016-09-08_03_56_28_747

Glance Registry logs:
http://logs.openstack.org/12/366812/3/check/gate-tripleo-ci-centos-7-scenario001-multinode-nv/ed56d11/logs/subnode-2/var/log/glance/registry.txt.gz#_2016-09-08_03_56_44_506

I compared Glance, Ceph and HAproxy configurations between OVB (that also test Ceph + RBD backend) and scenario001 jobs, and they are the same, so there is something else that prevent the upload to happen.

I thought it could be the CPU load somehow, but 1h30 of timeout for a cirros image would be really too much and I don't see anything in Glance logs.

Changed in tripleo:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Emilien Macchi (emilienm)
milestone: none → newton-rc1
Changed in tripleo:
milestone: newton-rc1 → ocata-1
Steven Hardy (shardy)
Changed in tripleo:
milestone: ocata-1 → ocata-2
Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.