attempting to sync unrecognized object v1.Secret - error while cloning a repository containing devfile.yaml from gitlab.org.com

[Divine1]

Summary

i have installed above eclipse-che version in minikube cluster and installation is successful

i want to integrate gitlab-oauth with eclipse-che

l have applied below gitlab-secret in eclipse-che namespace.

kind: Secret
apiVersion: v1
metadata:
  name: gitlab-oauth-config
  namespace: 'eclipse-che' 
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: oauth-scm-configuration
  annotations:
    che.eclipse.org/oauth-scm-server: gitlab
    che.eclipse.org/scm-server-endpoint: 'https://gitlab.org.com'
type: Opaque
data:
  id: 'ZWFkNDhjNzE1ODQ1ZDU3NDI1M2ExOGRmZTVlOTlkMjhhYjViMmY2OGQ4NDY5ODZmMTQid'
  secret: 'OGM0MDMwNWQ2OWI1ZGQ1ZGQ3ODk0YWQ0ZDc1MjZmMzNjMmZiMTUwMzhiMDJkMGZsecret'

then i opened the eclipse-che website https://192.168.49.2.nip.io, then logged-in using [email protected] / admin

After login, i provided my repository containing valid devfile.yaml https://gitlab.org.com/demoproject.git -> clicked create button -> this redirected the website from eclipse-che to gitlab.org.com , the sso authentication was successful. But the dev file cloning process failed due to this error attempting to sync unrecognized object v1.Secret

i have attached the screenshot showing error below. Please let me know how to fix this error.

Relevant information

No response

[benoitf]

related to devfile/devworkspace-operator#751

requires 0.12.0 operator or next channel

[Divine1]

related to devfile/devworkspace-operator#751

requires 0.12.0 operator or next channel

thank you for the response.

how do i use 0.12.0 operator or next channel to fix this issue ? Please let me know if there are any steps which i can follow in-order to solve this issue

[tolusha]

We are going to update che-operator to use DW 0.12.1 as a dependency
eclipse-che/che-operator#1302

cc @amisevsk

[Divine1]

@tolusha @amisevsk

thank you for this update.
when is it expected to be released?
how do i install the new release? chectl update next ?

currently below is the version i'm using

[amisevsk]

The changes will land in Che next as soon as eclipse-che/che-operator#1302 is merged. I'm not 100% on the process of that landing in chectl, @benoitf can confirm.

[benoitf]

7.43.0 stable release will happen next week
Chectl/next will also include these changes on the next build of chectl after operator pr will be merged

[Divine1]

@benoitf

is the fix discussed here released in this chectl version 0.0.20220128-next.0a7174a ? or is it yet to be released?

i'm checking with you on this because i updated to the chectl version 0.0.20220128-next.0a7174a today but still the issue with gitlab-org sso exists (attached screenshot below)..

[amisevsk]

@Divine1 It should be fixed across the board if you are using next images/versions. One way to double check is to find the devworkspace-controller-manager deployment and check which image is being used (should be v0.12.3 or next).

[Divine1]

@amisevsk thank you for the response. i'm able to update eclipse-che server to the latest version.

i'm facing some issues, i will create a new issue.
Have a great day