vostok publication breaks everything if vostok is not configured
Bug #614062 reported by
Michael Hudson-Doyle
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Michael Hudson-Doyle | ||
Bug Description
Currently, a publication factory is always registered for the 'vostok' skin even if no hostname is configured for it. Unfortunately, VirtualHostRequ
Related branches
lp://qastaging/~mwhudson/launchpad/disable-vostok-when-not-configured
- Paul Hummer (community): Approve (code)
-
Diff: 35 lines (+14/-4)1 file modifiedlib/canonical/launchpad/webapp/metazcml.py (+14/-4)
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #2 |
| tags: | added: qa-needstesting |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The linked branch is in ec2 now.