Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitbucket factory repo fails for public repo without bitbucket OAuth #20195

Closed
2 of 23 tasks
Tracked by #20218
skabashnyuk opened this issue Jul 26, 2021 · 1 comment
Closed
2 of 23 tasks
Tracked by #20218
Labels
area/che-server area/factory/server Server side of factory implementation kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@skabashnyuk
Copy link
Contributor

Describe the bug

Bitbucket factory repo fails for public repo without bitbucket OAuth
https://issues.redhat.com/browse/CRW-2094

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Setup CheCluster with public Bitbucket only
    customCheProperties:
      CHE_INFRA_KUBERNETES_WORKSPACE_START_TIMEOUT_MIN: '10'
      CHE_INFRA_KUBERNETES_WORKSPACE__UNRECOVERABLE__EVENTS: 'Failed Scheduling,Failed to pull image'
      CHE_INTEGRATION_BITBUCKET_SERVER__ENDPOINTS: 'https://bitbucket-bitbucket.apps.ocp47-aws.crw-qe.com/'
      CHE_LIMITS_USER_WORKSPACES_RUN_COUNT: '-1'
      CHE_LIMITS_WORKSPACE_IDLE_TIMEOUT: '900001'
      CHE_LOGGER_CONFIG: org.eclipse.che.api.factory.server=DEBUG
    externalDevfileRegistry: false
  1. Test factory with git repo from this SCM server.

Expected behavior

Factory should work

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

Installation method

  • chectl
    • provide a full command that was used to deploy Eclipse Che (including the output)
    • provide an output of chectl version command
  • OperatorHub
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • Dev Sandbox (workspaces.openshift.com)
  • other: please specify

Eclipse Che Logs

Additional context

@skabashnyuk skabashnyuk added kind/bug Outline of a bug - must adhere to the bug report template. area/che-server area/factory/server Server side of factory implementation severity/P2 Has a minor but important impact to the usage or development of the system. labels Jul 26, 2021
@dmytro-ndp
Copy link
Contributor

Actually it is configuration issue, not a Che bug.

It was needed to add BitBucket TLS self-signed certificate to CRW, as it is described in https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.9/html-single/installation_guide/index#importing-untrusted-tls-certificates_crw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server area/factory/server Server side of factory implementation kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

2 participants