Radosgw backends is in down state after deployment with errors related to keyring in rados.log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Tatyanka |
Bug Description
Steps:
1. Deploy ceph cluster with radosgw
2. When cluster ready - run ostf test for haproxy back-ends or run bellow command on controller
haproxy-status.sh | egrep -v "BACKEND|FRONTEND"
radosgw node-5 Status: DOWN/L4CON Sessions: 0 Rate: 0
radosgw node-6 Status: DOWN/L4CON Sessions: 0 Rate: 0
radosgw node-1 Status: DOWN/L4CON Sessions: 0 Rate: 0
radosgw logs looks like
2015-11-04 16:30:52.729338 7f90de2f7700 -1 failed to list objects pool_iterate returned r=-2
2015-11-04 16:30:52.729367 7f90de2f7700 0 ERROR: lists_keys_next(): ret=-2
2015-11-04 16:30:52.729470 7f90de2f7700 0 ERROR: sync_all_users() returned ret=-2
We add ostf tests with expectation that in neutron env all haproxy backens are running, so bvt became red (https:/
Changed in fuel: | |
assignee: | nobody → Tatyanka (tatyana-leontovich) |
tags: | added: area-qa |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/241783
Review: https:/