Bug 2033044

Summary: Unable to change import strategy if devfile is invalid
Product: OpenShift Container Platform Reporter: Mohammed Saud <msaud>
Component: Dev ConsoleAssignee: Mohammed Saud <msaud>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: aos-bugs, cjerolim, nmukherj, rorai
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:34:06 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:
Bug Depends On:    
Bug Blocks: 2036859    
Attachments:
Description Flags
no option.png none

Description Mohammed Saud 2021-12-15 18:35:48 UTC 
Created attachment 1846437 [details]
no option.png

Description of problem:
Unable to change import strategy if a repo contains an invalid devfile.yaml.

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

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Add page
2. Use a repository that contains an invalid/old devfile, along with other supported build strategy types (eg. https://github.com/redhat-developer-demos/spring-petclinic)
3. Try to create app using builder image strategy

Actual results:
The detection fails due to invalid devfile, and there is no option to select a different import strategy.

Expected results:
If multiple strategies are detected and one fails, there should be an option to select a different strategy.

Additional info:
Comment 2 Christoph Jerolimov 2022-01-04 09:04:22 UTC 
This issue happen also on 4.9.

Verified fix on 4.10.0-0.ci-2022-01-04-012641
Comment 3 Christoph Jerolimov 2022-01-04 09:06:44 UTC 
Tested also 4.8, it is not affected.
Comment 7 errata-xmlrpc 2022-03-10 16:34:06 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.

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