ceph radosgw needs mod-proxy-fcgi for apache 2.2

Bug #1422417 reported by Sage Weil on 2015-02-16
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Precise Backports
Undecided
Unassigned
apache2 (Ubuntu)
Undecided
Unassigned
Trusty
Undecided
Unassigned

Bug Description

In the past, upstream Ceph has provided a forked and self-packaged mod-fastcgi deb. Some potential license issues have been identified that prevent us from distributing this package going forward.

Unfortunately mod-proxy-fcgi is not available for apache 2.2 (shipped in precise). We have created a backport, available at

  https://github.com/ceph/mod-proxy-fcgi

Ideally this backport would be provided in the precise backports repository so that Ceph users can deploy Ceph radosgw without any additional repos.

Note that this isn't pulled from the development release because that ships Apache 2.4, which supports this module natively. 2.4 is not available for precise.

Please let us know if this is an acceptable use of backports before we do the (non-trivial) packaging. Thanks!

James Page (james-page) wrote :

After some discussion with Laney on irc, we'll also need to SRU a fix into the Apache2 package for 14.04 to allow upgrades with this new backport package to work correctly, as apache2-bin will need to Break/Replace libapach2-mod-proxy-fcgi.

Changed in apache2 (Ubuntu):
status: New → Invalid
Scott Kitterman (kitterman) wrote :

As long as 12.04 + backports -> 14.04 upgrades work, I think this is reasonable. I'd prefer someone other than me on the SRU team to make the call on the SRU piece of this though.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apache2 (Ubuntu Trusty):
status: New → Confirmed

Looking forward to this

We're going to remove support for FCGI in RGW: http://tracker.ceph.com/issues/16784, so we won't need this bug any more.

Robie Basak (racb) wrote :

Thanks. Let's close the bug then, so it's clear that nobody is expecting this to ever happen in Trusty. The bug is valid, so rather than Invalid I'll mark it Won't Fix (as we don't intend to fix it).

This isn't intended to exclude anyone else doing it. If you want to work on this, please raise it in this bug and we can reopen.

Robie Basak (racb) wrote :

(still subject to SRU team approval, etc)

Changed in apache2 (Ubuntu Trusty):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers