Bug 1771851

Summary: Console does not allow git repository with port defined
Product: OpenShift Container Platform Reporter: Jaspreet Kaur <jkaur>
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, mharri, nmukherj, spathak, wzheng
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Import from Git form used a regular expression to validate the Git URL. Unfortunately it was too restrictive and disallowed certain URLs which are actually valid. Consequence: The user could not enter what they considered to be a valid Git URL and complete the form. Fix: The Git URL regular expression used for validation has been updated. Result: All valid Git URLs are now accepted.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:12:28 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:
Bug Depends On:    
Bug Blocks: 1819112    

Description Jaspreet Kaur 2019-11-13 07:00:38 UTC
Description of problem:When trying to do a from git deployment in the console it does not allow any git repositories that contain a port number such as "https://example.com:3000/app.git". There is an error message "Invalid Git URL." displayed.

It works just fine through the CLI.

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

How reproducible:

Steps to Reproduce:

Actual results: Invalid git url

Expected results: should work if it is working with cli

Additional info:

Comment 4 cvogt 2019-11-16 01:06:36 UTC
Related to Partnerhttps://bugzilla.redhat.com/show_bug.cgi?id=1766350

There's issues with the git url validation regex.

Comment 5 cvogt 2019-11-19 15:02:23 UTC
PR: https://github.com/openshift/console/pull/3429

Comment 7 errata-xmlrpc 2020-01-23 11:12:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.