Bug 2007322 - Devfile/Dockerfile import does not work for unsupported git host
Summary: Devfile/Dockerfile import does not work for unsupported git host
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: divgupta
QA Contact: Debsmita Santra
Depends On:
Blocks: 2013253
TreeView+ depends on / blocked
Reported: 2021-09-23 14:44 UTC by Mohammed Saud
Modified: 2022-03-10 16:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:12:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
Dockerfile import with unsupported git host (1.11 MB, video/mp4)
2021-09-23 14:44 UTC, Mohammed Saud
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10182 0 None open Bug 2007322: Fix to let the user create the application even if dockerfile is not detected 2021-10-05 13:27:46 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:13:13 UTC

Description Mohammed Saud 2021-09-23 14:44:35 UTC
Created attachment 1825680 [details]
Dockerfile import with unsupported git host

Description of problem:
Git import using Devfile/Dockerfile does not allow creating the application when the git host type is unreachable / unsupported.

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

How reproducible:

Steps to Reproduce:
1. Navigate to git import page
2. Attempt to start a git import using dockerfile/devfile with an unsupported git host (ex. https://code.videolan.org/rist/librist)

Actual results:
The create button stays disabled.

Expected results:
User should be able to create application even if the repository is unreachable / unsupported.

Comment 4 Debsmita Santra 2021-10-28 15:58:04 UTC
verified on 4.10.0-0.nightly-2021-10-27-230233

Comment 9 errata-xmlrpc 2022-03-10 16:12:52 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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

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


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