Actions
tickets #39932
closedupdating issues on status.o.o does not work, causes internal server error
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-08-17
Due date:
% Done:
100%
Estimated time:
Description
Observation¶
[17 Aug 2018 16:12:35] good that I always tend to copy-paste textfield entries before submitting them. Trying to update the incident entry on status.opensuse.org for o3 gave me a 500 internal error :D
[17 Aug 2018 16:13:13] anyone wants to check the remote side on status.opensuse.org for error code cc9f5a7f-58b8-4b88-b8fe-6f1017d10173 ?
[17 Aug 2018 16:15:39] reproducible and can not seem to be able to update it with any content.
Was reproduced by tampakrap and confirmed by cboltz
Editing an incident works. Also announcements to subscribers are sent out even though the update ends up with a 500
Workaround¶
It is suggested to still try to "update" the incident to send update announcements and then "edit" the incident instead.
Updated by okurz over 5 years ago
- Related to action #39743: [o3][tools] o3 unusable, often responds with 504 Gateway Time-out added
Updated by lrupp over 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Works now.
Actions