Actions
Bug #17399
closedPeriod commit that changes default_placement can cause RGWs to crash.
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
While testing for #17398, a change of default_placement caused my RGW instances to all exit after period update --commit
Old¶
Zonegroup:
...
"placement_targets": [
{
"name": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
...
Zone:
...
"placement_pools": [
{
"key": "default-placement",
"val": {
"index_pool": ".rgw.data.1",
"data_pool": ".rgw.data.1",
"data_extra_pool": ".rgw.data.1",
"index_type": 0
}
}
],
...
New¶
Zonegroup:
...
"placement_targets": [
{
"name": "",
"tags": []
}
],
"default_placement": "",
...
Zone:
...
"placement_pools": [
{
"key": "default-placement",
"val": {
"index_pool": ".rgw.data.1",
"data_pool": ".rgw.data.1",
"data_extra_pool": ".rgw.data.1",
"index_type": 0
}
},
{
"key": "",
"val": {
"index_pool": ".rgw.data.1",
"data_pool": ".rgw.data.1",
"data_extra_pool": ".rgw.data.1",
"index_type": 0
}
}
],
...
Updated by Yehuda Sadeh over 7 years ago
- Assignee set to Orit Wasserman
- Priority changed from Normal to High
Updated by Yehuda Sadeh over 7 years ago
old radosgw-admin was still [re]running, at created new default region objects. This triggered period conversion again that clobbered the valid period.
Actions