staging restore script creates invalid feature rule
Bug #726128 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Stuart Bishop | ||
Bug Description
the staging restore script currently sets this rule:
team:launchpad | 0 | profiling.enabled | NULL | 2011-02-27 01:24:27.928731
This isn't valid - empty strings are, but not NULL - NULL causes the webapp to OOPS on every page.
What it should be setting is
team:launchpad | 0 | profiling.enabled | 'on' | 2011-02-27 01:24:27.928731
| affects: | launchpad → lp-staging-scripts |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in lp-staging-scripts: | |
| status: | Triaged → In Progress |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Stuart Bishop (stub) |
| Changed in launchpad: | |
| status: | In Progress → Fix Released |
| Changed in lp-staging-scripts: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
lp-staging-scripts is ready for the losas.
I've opened a bugtask on Launchpad, as this should not caused the webapp to fail like this. I suspect NULL is no longer a valid value now because we have a web ui for editing feature flags and the fix is to add NOT NULL to the value column in the DB.