Bug 2041774

Summary: Failing git detection should not recommend Devfiles as import strategy
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: low Docs Contact:
Priority: low    
Version: 4.9CC: nmukherj
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 10:42:31 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
unexpected-default-import-strategy.png none

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:
Always

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:
None
Comment 1 Christoph Jerolimov 2022-01-18 09:28:01 UTC 
Created attachment 1851540 [details]
unexpected-default-import-strategy.png
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.

https://access.redhat.com/errata/RHSA-2022:5069