Bug 1826682

Summary: Cannot validate bitbucket repository
Product: OpenShift Container Platform Reporter: Vikram Raj <viraj>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:30:08 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
bitbucket repo is validated none

Description Vikram Raj 2020-04-22 10:23:58 UTC 
Description of problem:
on Git url validation it shows repository not reachable even though it actually exists

Note: This appears to be a case-sensitive check problem.

have attached screenshots for the same

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


How reproducible:


Steps to Reproduce:
1. Navigate to import from git page.
2. Enter the Bitbucket repository URL in Git repo URL field(Repository name should be in camelCase and public). 
3. On blur, you will see the error message "Git repository is not reachable."

Actual results:
Getting "Git repository is not reachable" error message even if repository exits and public URL.

Expected results:
The repository should get validated without an error message "Git repository is not reachable"
Comment 3 Gajanan More 2020-04-27 11:07:39 UTC 
Created attachment 1682128 [details]
bitbucket repo is validated
Comment 4 Gajanan More 2020-04-27 11:08:11 UTC 
I have validated the bugzilla on the
Build: 4.5.0-0.ci-2020-04-26-162607
Browser: Google Chrome Version 78.0.3904.108
Marking this as verified.
Comment 5 errata-xmlrpc 2020-07-13 17:30:08 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.

https://access.redhat.com/errata/RHBA-2020:2409