This means there won't be a fallback to look for the OOPS in the filesystem.
The view will try to find the OOPS in the database, and if it's not there,
it'll show a message saying the the OOPS can't be found.
The cowboyed code can be removed once the permissions in the source directories are fixed and errorlog.py is patched to set the permission in the error_dir and oops file to world readable.
Today this happened again. I cowboyed the following to the production /pastebin. canonical. com/38351/
oops-tools instance: https:/
This means there won't be a fallback to look for the OOPS in the filesystem.
The view will try to find the OOPS in the database, and if it's not there,
it'll show a message saying the the OOPS can't be found.
The cowboyed code can be removed once the permissions in the source directories are fixed and errorlog.py is patched to set the permission in the error_dir and oops file to world readable.