500 internal error of bodhi?

2014-03-26 Thread Christopher Meng
Hi, Today when I submitted updates I met: 500 Internal error The server encountered an unexpected condition which prevented it from fulfilling the request. I've tried about 50 times but failed still. Can someone check it? Thanks. Yours sincerely, Christopher Meng Noob here.

Re: Scheduling an IRC meeting on our private cloud setup

2014-03-26 Thread Miroslav Suchý
On 03/25/2014 08:12 PM, Ralph Bean wrote: Meeting started by nirik at 18:00:03 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-classroom/2014-03-25/infrastructure-private-cloud-class.2014-03-25-18.00.log.html I promised to ask OpenStack guys two guestions. Here are

Plan for tomorrow's Fedora Infrastructure meeting (2014-03-27)

2014-03-26 Thread Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow, 2014-03-27 at 18:00 UTC in #fedora-meeting on the freenode network. (We are moving back one hour due to the daylight saving time changes. Hope that works for everyone). Suggested topics: #topic New folks introductions and

Re: 500 internal error of bodhi?

2014-03-26 Thread Luke Macken
On Wed, Mar 26, 2014 at 08:37:09PM +0800, Christopher Meng wrote: Hi, Today when I submitted updates I met: 500 Internal error The server encountered an unexpected condition which prevented it from fulfilling the request. I've tried about 50 times but failed still. Can someone

Re: 500 internal error of bodhi?

2014-03-26 Thread Christopher Meng
On 3/27/14, Luke Macken lmac...@redhat.com wrote: Can you clear the bugs field and try again? I'm seeing it submitted as u'1070207\u200e', which might be causing the issue. Ok. But I never try using special chars in the bug URL, not sure about the exact problem. Thank you.

Re: 500 internal error of bodhi?

2014-03-26 Thread Mathieu Bridon
On Thu, 2014-03-27 at 12:06 +0800, Christopher Meng wrote: On 3/27/14, Luke Macken lmac...@redhat.com wrote: Can you clear the bugs field and try again? I'm seeing it submitted as u'1070207\u200e', which might be causing the issue. Ok. But I never try using special chars in the bug URL,