Bug 963196

Summary: Trying to create Django Application fails multiple times
Product: OKD Reporter: Safwan Erooth <safwan>
Component: WebsiteAssignee: Clayton Coleman <ccoleman>
Status: CLOSED NOTABUG QA Contact: libra bugs <libra-bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 2.xCC: yujzhang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-16 08:57:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The Screenshots none

Description Safwan Erooth 2013-05-15 11:25:47 UTC
Created attachment 748199 [details]
The Screenshots

Description of problem:


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

How reproducible:
Try to create django app.

Steps to Reproduce:
1. Create Django app.
2. Choose python 2.6 and give all details like name and git.
3. Click on create buttton
  
Actual results:


Expected results:


Additional info:

Comment 1 Yujie Zhang 2013-05-16 07:00:29 UTC
Tried on PROD, created python2.6 with django git url, it can be created successfully, https://djabot-mongocon.rhcloud.com/

Could you please try it for one more time? Thanks!

Comment 2 Yujie Zhang 2013-05-16 07:05:31 UTC
Also tried scalable application of python2.6 with django git, it can be created successfully too, could you please specify your git url? Or any other details of your steps, thanks!

Comment 3 Yujie Zhang 2013-05-16 07:30:21 UTC
I can reproduce above issue when the git url is invalid, so could you please check if your git url is valid ? Thanks!

Comment 4 Safwan Erooth 2013-05-16 08:57:04 UTC
The problem was with Git url. I think a error message that specifies that git url is wrong will be more helpful.

Comment 5 Yujie Zhang 2013-05-16 10:04:04 UTC
(In reply to comment #4)
You are right, we have bug 963615 to track this issue, thanks!