Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 internal server error on instance config page due to missing AppArmor rule #2827

Closed
redshiftzero opened this issue Jan 11, 2018 · 4 comments

Comments

@redshiftzero
Copy link
Contributor

Description

I went to the new "Instance Config" page and got a 500 internal server error due to a missing AppArmor rule.

Steps to Reproduce

  1. Install 0.5.1-rc1 on prod VMs
  2. Create an administrator account.
  3. Click on "Instance Config" in the admin interface:

screen shot 2018-01-10 at 6 41 26 pm

Expected Behavior

You go to the instance config page and all is merry and well.

Actual Behavior

screen shot 2018-01-10 at 6 42 11 pm

Comments

A peek at the logs reveals the culprit:

[Thu Jan 11 02:38:16.105986 2018] [:error] [pid 3754:tid 2943491983104] [remote 127.0.0.1:51806] IOError: [Errno 13] Permission denied: '/var/www/securedrop/journalist_templates/config.html'

Updating the AppArmor profile for Apache will fix this.

@redshiftzero
Copy link
Contributor Author

I'm surprised that CI didn't catch this, since there were unit and functional tests for this feature that will pass in the development environment due to the lack of AppArmor, but should fail in staging..

@ghost
Copy link

ghost commented Jan 11, 2018

I'm surprised that CI didn't catch this

Ouch, it means something is broken in the CI :-(

@kushaldas
Copy link
Contributor

I can also verify the bug.

@redshiftzero
Copy link
Contributor Author

redshiftzero commented Jan 11, 2018

Closed by #2828

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants