** Description changed: - 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. + [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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255464 Title: radosgw init script missing from 0.64 onwards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1255464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
