M/N upgrades - Ceph will break after the convergence step if the image uses ext4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Giulio Fidente |
Bug Description
After the M/N convergence step, if the image is using ext4 ceph jewel will refuse to start:
[root@overcloud
cluster 03168daa-
health HEALTH_ERR
root@overcloud-
2016-09-29 09:04:16.406971 7f98ee6fd800 -1 journal FileJournal::_open: disabling aio for non-block journal. Use journal_force_aio to force use of aio anyway
2016-09-29 09:04:16.406976 7f98ee6fd800 1 journal _open /var/lib/
2016-09-29 09:04:16.407155 7f98ee6fd800 1 journal _open /var/lib/
2016-09-29 09:04:16.407769 7f98ee6fd800 1 filestore(
2016-09-29 09:04:16.408062 7f98ee6fd800 -1 osd.2 0 backend (filestore) is unable to support max object name[space] len
2016-09-29 09:04:16.408075 7f98ee6fd800 -1 osd.2 0 osd max object name len = 2048
2016-09-29 09:04:16.408077 7f98ee6fd800 -1 osd.2 0 osd max object namespace len = 256
2016-09-29 09:04:16.408079 7f98ee6fd800 -1 osd.2 0 (36) File name too long
2016-09-29 09:04:16.409545 7f98ee6fd800 1 journal close /var/lib/
2016-09-29 09:04:16.410254 7f98ee6fd800 -1 ** ERROR: osd init failed: (36) File name too long
This happened even though we had the following parameters set in puppet:
/etc/puppet/
/etc/puppet/
The conf file already had the settings:
osd_max_
osd_max_
The issue is that the convergence step will not restart the osd's (which is a good thing), but the new settings won't be applied then and so Ceph in Newton (Jewel) will fail to start
Changed in tripleo: | |
milestone: | none → ocata-1 |
tags: | added: newton-backport-potential newton-rc-potential |
Changed in tripleo: | |
milestone: | ocata-1 → newton-rc3 |
Fix proposed to branch: master /review. openstack. org/379401
Review: https:/