Bug 2041774 - Failing git detection should not recommend Devfiles as import strategy
Summary: Failing git detection should not recommend Devfiles as import strategy
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Jaivardhan Kumar
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-18 09:27 UTC by Christoph Jerolimov
Modified: 2022-08-10 10:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:42:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
unexpected-default-import-strategy.png (63.80 KB, image/png)
2022-01-18 09:28 UTC, Christoph Jerolimov
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10966 0 None open Bug 2041774: defaulting to s2i if git type can't be figured out 2022-01-28 13:38:38 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:42:52 UTC

Description Christoph Jerolimov 2022-01-18 09:27:39 UTC
Description of problem:
As a user, I'm confused that the UI warns me that the import strategy could not be autodetected and should be selected by me, but that the UI preselects an (uncommon) strategy already.

Version-Release number of selected component (if applicable):
4.9 and 4.10 (master)

How reproducible:

Steps to Reproduce:
1. Open the dev console, navigate to Add > Import from Git
2. Enter a git URL which could not be autodetected, like https://git.mycompany.com
3. Check the reasons why you can not submit the form
   (Name is missing, and the Devfile name)

Actual results:
See a warning: Unable to detect import strategy
               Select from the options below.

Import strategy "Devfile" is already selected.

An input field "Devfile" is shown and marked as required.

Expected results:
The warning is fine!

Builder image strategy should be preselected if the type could not be detected.

Additional info:

Comment 1 Christoph Jerolimov 2022-01-18 09:28:01 UTC
Created attachment 1851540 [details]

Comment 9 errata-xmlrpc 2022-08-10 10:42:31 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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.