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

Volume created but the secret with the self-signed cert is not #13433

Closed
skabashnyuk opened this issue May 28, 2019 · 3 comments · Fixed by #13546
Closed

Volume created but the secret with the self-signed cert is not #13433

skabashnyuk opened this issue May 28, 2019 · 3 comments · Fixed by #13546
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented May 28, 2019

Description

  1. Failed to start a Che 7 workspace if Che deployment is configured to use self signed cert
2019-02-07 18:23:32,549[aceSharedPool-1]  [WARN ] [.i.k.KubernetesInternalRuntime 249]  - 
Failed to start Kubernetes runtime of workspace workspaceq1ys0pxhpfgzgmu8. 
Cause: Plugins installation process failed. Error: Unrecoverable event occurred: 
'FailedMount', 'MountVolume.SetUp failed for volume "che-self-signed-cert" : secret 
"che-self-signed-cert" not found', 'workspaceq1ys0pxhpfgzgmu8.che-plugin-broker'

A secret with cert body isn't created but che-plugin-broker pod is configured to use it

Follow up of #12634 (comment)

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels May 28, 2019
This was referenced May 28, 2019
@skabashnyuk skabashnyuk added the severity/P1 Has a major impact to usage or development of the system. label May 28, 2019
@metlos metlos self-assigned this Jun 13, 2019
@sleshchenko
Copy link
Member

@dmytro-ndp
Copy link
Contributor

Looks like the issue had affected OpenShift oAuth integration in Eclipse Che being deployed to OKD using the command:

bash ${WORKSPACE}/deploy/openshift/ocp.sh --run-ocp --deploy-che --multiuser --setup-ocp-oauth

org eclipse che selenium site ocpoauth LoginExistedUserWithOpenShiftOAuthTest checkExistedCheUserOcpProjectCreationAndRemoval_time-1560454933251-millis

https://ci.codenvycorp.com/view/qa-nightly/job/che-multiuser-master-ocp-oauth-test/389/Selenium_20tests_20report/screenshots/org.eclipse.che.selenium.site.ocpoauth.LoginExistedUserWithOpenShiftOAuthTest.checkExistedCheUserOcpProjectCreationAndRemoval_time-1560454933251-millis.png

@sleshchenko
Copy link
Member

@dmytro-ndp Thanks for reporting your case, actually the error is the same but the cause is different:

  1. Che deployment is configured to use self-signed cert: Che Server does not create secret for Che 7 on plugin broker phase of workspace start.
  2. (Your case) Che Server is deployed with ocp.sh, OpenShift OAuth is configured but self-signed cert is not: issues during workspace start is caused by ocp.sh server + Che Server templates inconsistency.
    I think that my PR does not solve your case: please create a separate issue if it still actual.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants