Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2025592

Summary: ODC 4.9 supports invalid devfiles only
Product: OpenShift Container Platform Reporter: Mario Loriedo <mloriedo>
Component: Dev ConsoleAssignee: Rohit Rai <rorai>
Status: CLOSED ERRATA QA Contact: Mohammed Saud <msaud>
Severity: medium Docs Contact:
Priority: high    
Version: 4.10CC: aos-bugs, msaud, 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:
: 2029861 (view as bug list) Environment:
Last Closed: 2022-03-10 16:30:15 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: 2029861    
Attachments:
Description Flags
devconsole samples with invalid devfiles none

Description Mario Loriedo 2021-11-22 14:43:58 UTC 
Created attachment 1843026 [details]
devconsole samples with invalid devfiles

Created attachment 1843026 [details]
devconsole samples with invalid devfiles

## Description of problem:

The devfiles that are included in 4 ODC samples are invalid. 

The component image build guidance has an invalid container image:

```
  - name: buildguidance
    attributes:
      tool: console-import
    container:
      image: buildguidanceimage-placeholder
      memoryLimit: 1024Mi
      endpoints:
        - name: http-3001
          targetPort: 3001
```

The problem is that Eclipse Che (or any tool that supports devfile v2) will try to pull the image and fail when trying to start a workspace based on those samples.

We have opened an issue on the [devfile registry side](https://github.com/devfile/api/issues/666) but if the fix happens on the devfile registry repo only, OSD will get broken. A fix should be provided OSD-side as well. 

## Prerequisites (if any, like setup, operators/versions):

OCP 4.9 (and previous releases of ODC that support devfiles)

## Steps to Reproduce

Deploy Eclipse Che on an OCP cluster
Create an application from one of the samples with at devfile
Click on the Eclipse Che link on the topology view

### Actual results: Che workspace startup fails.
### Expected results: Che workspace should start successfully.

## Reproducibility (Always/Intermittent/Only Once):

Always

## Additional info:

Eclipse Che versions prior to 7.39 and CodeReady Workspaces before 2.13 didn't support devfile v2. But that got fixed.
https://issues.redhat.com/browse/CRW-2411
Comment 1 Mohammed Saud 2021-12-07 14:21:54 UTC 
Verified on:
Build:   4.10.0-0.ci-2021-12-06-061923
Browser: Firefox 94
Comment 4 errata-xmlrpc 2022-03-10 16:30:15 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