scenario001 and 004 fails when Glance with rbd backend is containerized but not Ceph
Bug #1710773 reported by
Emilien Macchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Giulio Fidente |
Bug Description
Scenario001 and Scenario004 have both Ceph deployed in non-containerized environment for now, there is some work in progress to enable it but this is not the problem here.
The problem is that when Glance API is containerized, it's impossible to upload an image into Glance:
I don't see any error in Glance API logs:
http://
Changed in tripleo: | |
assignee: | nobody → John Fulton (jfulton-org) |
To post a comment you must log in.
I. Two other ways to describe this issue:
- Why did Glance return an HTTP 503 [0] when asked to upload a ciros image?
- Glance upload fails and logs "since image size is zero we will be doing resize-before-write for each chunk which will be considerably slower than normal"
II. Q/A from CI logs: openstack. keyring on the subnode ? Yes [8]
- Glance logs show that the rbd scheme was enabled [1]
- Glance logs show Glance creating image with order 23 and size 0 [2] in rbd.py [3]
- There have been cases where the ceph config was the root cause of this error [4]
- Is the glance-api.conf correct? Yes [6] (but see open question A)
- Was the glance container image mounted with the ceph.conf ? Yes [7]
- Is a normal looking ceph.conf on the subnode (i.e. the container host?) ? Yes [8]
- Is ceph.client.
- Was a change made to support this? Yes, puppet-ceph still genereates the configs and glance container was changed to use them [9]
Two open questions:
A. In the glance conf, rbd_store_ceph_conf has been commented out but worked in the past (for default reasons) might this be affecting us now?
B. Are the permissions correct of the ceph keyring set so that the glance user can read it?
- CI logs do not confirm the 644 permissions, but they _should_ be correct...
- They have been 644 in the past [10] and need to be so that the container can read the key so why should this change?
Next Steps:
- Attempting to reproduce in my local environment
[0] http:// logs.openstack. org/29/ 490129/ 4/check/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 1d6c57a/ logs/undercloud /home/jenkins/ overcloud_ validate. log.txt. gz#_2017- 08-12_13_ 29_17 logs.openstack. org/29/ 490129/ 4/check/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 1d6c57a/ logs/subnode- 2/var/log/ containers/ glance/ api.log. txt.gz# _2017-08- 12_13_23_ 40_472 logs.openstack. org/29/ 490129/ 4/check/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 1d6c57a/ logs/subnode- 2/var/log/ containers/ glance/ api.log. txt.gz# _2017-08- 12_13_27_ 13_144 /github. com/openstack/ glance_ store/blob/ master/ glance_ store/_ drivers/ rbd.py# L460-L461 /ask.openstack. org/en/ question/ 78493/glance- image-create- ceph-problem/ logs.openstack. org/29/ 490129/ 4/check/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 1d6c57a/ logs/subnode- 2/var/log/ config- data/glance_ api/etc/ glance/ glance- api.conf. txt.gz pool=images user=openstack ceph_conf = /etc/ceph/ceph.conf # <--- this will default correctly to what's in comment direct_ url=True logs.openstack. org/29/ 490129/ 4/check/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 1d6c57a/ logs/subnode- 2/var/log/ extra/docker/ containers/ glance_ api/docker_ info.log. txt.gz (note the "/etc/ceph: /var/lib/ kolla/config_ files/src- ceph:ro" ) logs.openstack. org/29/ 490129/ 4/check/ gate-tripleo- ci-centos- 7-scenario001- multinode- oooq-container/ 1d6c57a/ logs/subnode- 2/etc/ceph/ /review. openstack. org/#/c/ 482500 /github. com/openstack/ puppet- ceph/blob/ 28e8f452...
[1] http://
[2] http://
[3] https:/
[4] https:/
[5] http://
[6] glance-api.conf.txt
"""
[glance_store]
stores=http,rbd
default_store=rbd
rbd_store_
rbd_store_
#rbd_store_
show_image_
"""
[7] http://
[8] http://
[9] https:/
[10] https:/