[SRU] radosgw init script missing from 0.64 onwards.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ceph (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
RADOS Gateway users upgrading from raring that rely on the init script to start the radosgw will be broken as the init script has been replaces by a non-equivalent upstart configuration
[Test Case]
sudo service radosgw start
(starts upstart configuration which is actually an instance type upstart config).
radosgw process is not started.
[Regression Potential]
The fix is to rename the radosgw upstart configuration to radosgw-instance so that both the upstart configurations and the init script get installed; the radosgw-instance upstart configuration is started by the radosgw event so should still work OK.
[Original Bug Report]
The radosgw upstart configurations started shipping in 13.10; however one namespace conflicts with the radosgw init script but does not do the same thing; so upgrades will break.
Changed in ceph (Ubuntu Saucy): | |
status: | New → In Progress |
importance: | Undecided → High |
description: | updated |
summary: |
- radosgw init script missing from 0.64 onwards. + [SRU] radosgw init script missing from 0.64 onwards. |
This bug was fixed in the package ceph - 0.72.1-3
---------------
ceph (0.72.1-3) unstable; urgency=low
* d/rules, ceph.install: Correct install paths for ceph-* helpers.
* d/p/modules: Mark libcls_kvs.so as module.
* d/rules: Rename radosgw upstart configuration to radosgw-instance to
avoid namespace conflict with init script which breaks backwards
compatibility (LP: #1255464).
-- James Page <email address hidden> Wed, 27 Nov 2013 10:52:48 +0000