Bug 825246 - QuickStart Issue: BookMarks
Summary: QuickStart Issue: BookMarks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Templates
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Linqing Lu
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-25 12:49 UTC by Attila Nagy
Modified: 2015-05-15 01:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-08 17:59:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Server logs (7.43 KB, text/x-log)
2012-05-25 12:49 UTC, Attila Nagy
no flags Details

Description Attila Nagy 2012-05-25 12:49:13 UTC
Description of problem: QuickStart application BookMarks cannot be started.


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Follow instructions on https://github.com/openshift/BookMarks-openshift-quickstart
  

Actual results: 500 Internal Server Errror (Server logs are attached)


Expected results: The application must be accessible without any problems.


Additional info:

Comment 1 Attila Nagy 2012-05-25 12:49:45 UTC
Created attachment 586856 [details]
Server logs

Comment 2 Mrunal Patel 2012-05-25 21:36:46 UTC
The example needs to be updated for Django 1.4. There are a couple of issues:
1. These are deprecated and need to be removed from the settings.py file   'django.middleware.csrf.CsrfViewMiddleware'   'django.middleware.csrf.CsrfResponseMiddleware'
See here: https://docs.djangoproject.com/en/1.3/ref/contrib/csrf/#legacy-method

2. Engine should be specified as
'ENGINE': 'django.db.backends.mysql' instead of just mysql

Comment 3 Linqing Lu 2012-05-27 04:35:07 UTC
Fixed.

Available on https://github.com/lulinqing/BookMarks-openshift-quickstart
Will be updated into openshift group later.

Comment 4 Linqing Lu 2012-05-27 12:57:45 UTC
Updated to OpenShift repo.


Note You need to log in before you can comment on or make changes to this bug.