bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

[traceback] UndefinedError: 'get_announcements' is undefined

RESOLVED FIXED in 2013Q3

Status

support.mozilla.org
General
P1
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: willkg, Assigned: mythmon)

Tracking

unspecified
2013Q3

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=user c=general p=1 s=2013.18)

I'm seeing a ton of these in Sentry since Thursday of last week.

Internal Server Error: /en-US/get-involved

Stacktrace (most recent call last):

  File "django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "mobility/decorators.py", line 23, in wrapper
    return f(request, *args, **kw)
  File "kitsune/landings/views.py", line 41, in get_involved
    return render(request, template)
  File "django/shortcuts/__init__.py", line 44, in render
    return HttpResponse(loader.render_to_string(*args, **kwargs),
  File "django/template/loader.py", line 176, in render_to_string
    return t.render(context_instance)
  File "jingo/__init__.py", line 193, in render
    return super(Template, self).render(context_dict)
  File "newrelic/api/object_wrapper.py", line 216, in __call__
    self._nr_instance, args, kwargs)
  File "newrelic/api/function_trace.py", line 40, in dynamic_wrapper
    return wrapped(*args, **kwargs)
  File "jinja2/environment.py", line 891, in render
    return self.environment.handle_exception(exc_info, True)
  File "/data/www/support.mozilla.org/kitsune/kitsune/landings/templates/landings/get-involved.html", line 4, in top-level template code
    {% set styles = ('landings/get-involved',) %}
  File "/data/www/support.mozilla.org/kitsune/kitsune/sumo/templates/base.html", line 120, in top-level template code
    {% for announ in get_announcements() %}

UndefinedError: 'get_announcements' is undefined


It's under a few different urls, so it's spread out across a bunch of reports:

https://errormill.mozilla.org/support/support/group/98769/
https://errormill.mozilla.org/support/support/group/99399/
https://errormill.mozilla.org/support/support/group/98761/
https://errormill.mozilla.org/support/support/group/98935/
etc.
I haven't looked into it, but at first glance, it looks bad. Making it a P1 and putting it into this sprint to at least look into. If it turns out not to be so bad, we can brush it off.
Priority: -- → P1
Whiteboard: u=user c=general p= s=2013.17
Target Milestone: --- → 2013Q3
Moving to next sprint.
Whiteboard: u=user c=general p= s=2013.17 → u=user c=general p= s=2013.18
This looks like it might be related to bug 911760. Making this a 1pt assuming that fixing one will make it easy to fix the other.
Whiteboard: u=user c=general p= s=2013.18 → u=user c=general p=1 s=2013.18
(Assignee)

Updated

5 years ago
Assignee: nobody → mcooper
I haven't seen the error since those commits were deployed \o/

Thanks to mythmon, willkg, r1cky!
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.