#4301 Unable to post comments
Closed: Invalid by wattersmt. Opened by wattersmt.

Users are no longer able to post comments after upgrading to pagure 5.3.1. The apache log shows a traceback as follows.

[Tue Feb 26 12:44:14.038850 2019] [:error] [pid 15635] [remote 10.201.64.11:28] mod_wsgi (pid=15635): Exception occurred processing WSGI script '/usr/share/pagure/pagure.wsgi'.
[Tue Feb 26 12:44:14.038965 2019] [:error] [pid 15635] [remote 10.201.64.11:28] Traceback (most recent call last):
[Tue Feb 26 12:44:14.038992 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1836, in __call__
[Tue Feb 26 12:44:14.039370 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     return self.wsgi_app(environ, start_response)
[Tue Feb 26 12:44:14.039389 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/pagure/proxy.py", line 74, in __call__
[Tue Feb 26 12:44:14.039450 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     return self.app(environ, start_response)
[Tue Feb 26 12:44:14.039467 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1820, in wsgi_app
[Tue Feb 26 12:44:14.039504 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     response = self.make_response(self.handle_exception(e))
[Tue Feb 26 12:44:14.039524 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1403, in handle_exception
[Tue Feb 26 12:44:14.039551 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     reraise(exc_type, exc_value, tb)
[Tue Feb 26 12:44:14.039566 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
[Tue Feb 26 12:44:14.039592 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     response = self.full_dispatch_request()
[Tue Feb 26 12:44:14.039607 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
[Tue Feb 26 12:44:14.039632 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     rv = self.handle_user_exception(e)
[Tue Feb 26 12:44:14.039646 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
[Tue Feb 26 12:44:14.039671 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     reraise(exc_type, exc_value, tb)
[Tue Feb 26 12:44:14.039686 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
[Tue Feb 26 12:44:14.039710 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     rv = self.dispatch_request()
[Tue Feb 26 12:44:14.039751 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
[Tue Feb 26 12:44:14.039787 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     return self.view_functions[rule.endpoint](**req.view_args)
[Tue Feb 26 12:44:14.039803 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/pagure/api/__init__.py", line 189, in wrapper
[Tue Feb 26 12:44:14.039880 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     result = function(*args, **kwargs)
[Tue Feb 26 12:44:14.039898 2019] [:error] [pid 15635] [remote 10.201.64.11:28]   File "/usr/lib/python2.7/site-packages/pagure/api/ci/jenkins.py", line 71, in jenkins_ci_notification
[Tue Feb 26 12:44:14.039946 2019] [:error] [pid 15635] [remote 10.201.64.11:28]     to_bytes(pagure_ci_token), to_bytes(project.ci_hook.pagure_ci_token)
[Tue Feb 26 12:44:14.039979 2019] [:error] [pid 15635] [remote 10.201.64.11:28] AttributeError: 'Project' object has no attribute 'ci_hook'

Updates were done via yum on a server running CentOS 7.

Name        : pagure
Version     : 5.3
Release     : 1.el7

Any idea how to fix this?


I have resolved the hook error although some projects are still unable to post or delete comments on an open issue. Clicking the delete button does not actually delete the comment and posting a comment simply results in a page refresh with no new data appearing.

Metadata Update from @wattersmt:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Metadata