Bug 2033044 - Unable to change import strategy if devfile is invalid
Summary: Unable to change import strategy if devfile is invalid
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Mohammed Saud
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 2036859
TreeView+ depends on / blocked
 
Reported: 2021-12-15 18:35 UTC by Mohammed Saud
Modified: 2022-03-10 16:34 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
no option.png (58.66 KB, image/png)
2021-12-15 18:35 UTC, Mohammed Saud
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10688 0 None open Bug 2033044: Shift invalid devfile alert down 2021-12-22 08:01:10 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:34:18 UTC

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


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