Bug 2029861 - ODC 4.9 supports invalid devfiles only
Summary: ODC 4.9 supports invalid devfiles only
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Rohit Rai
QA Contact: spathak@redhat.com
Depends On: 2025592
TreeView+ depends on / blocked
Reported: 2021-12-07 13:36 UTC by Rohit Rai
Modified: 2022-01-31 18:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2025592
Last Closed: 2022-01-31 18:22:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10620 0 None open [release-4.9] Bug 2029861: backport the change from #10394 to release 4.9 2021-12-07 14:22:24 UTC
Red Hat Product Errata RHBA-2022:0279 0 None None None 2022-01-31 18:22:54 UTC

Description Rohit Rai 2021-12-07 13:36:04 UTC
+++ This bug was initially created as a clone of Bug #2025592 +++

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
      tool: console-import
      image: buildguidanceimage-placeholder
      memoryLimit: 1024Mi
        - 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):


## Additional info:

Eclipse Che versions prior to 7.39 and CodeReady Workspaces before 2.13 didn't support devfile v2. But that got fixed.

Comment 7 Mario Loriedo 2022-01-28 12:38:10 UTC
You are probably logged in as kubeadmin. You should login as a different user or RHSSO will not let you in (kubeadmin doesn't have a user id and is not considered a valid user by RH SSO).

Comment 8 spathak@redhat.com 2022-01-28 17:03:37 UTC
Okay As this bug is not related to the aforementioned issue, will mark it as verified

Comment 10 spathak@redhat.com 2022-01-28 17:08:38 UTC
Verified on build version: 4.9.0-0.nightly-2022-01-24-212243
Browser: Google Chrome 97

Comment 12 errata-xmlrpc 2022-01-31 18:22:33 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 (OpenShift Container Platform 4.9.18 bug fix 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.