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.

Sign up for GitHub

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

Jump to bottom

K8s/OS bootstrapper does not publish error if it occurs during commands executing #12054

Closed
sleshchenko opened this issue Nov 27, 2018 · 1 comment
Closed

K8s/OS bootstrapper does not publish error if it occurs during commands executing #12054

sleshchenko opened this issue Nov 27, 2018 · 1 comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@sleshchenko
Copy link
Member

Description

K8s/OS bootstrapper does not publish error if it occurs during commands executing.

It is caused by fabric8io/kubernetes-client#1173.

After merging fabric8io/kubernetes-client#1268 and releasing a new version of fabric8-kubernetes client we should upgrade it to fix this issue.

Reproduction Steps

  1. Deploy Che.
  2. Remove bootstrapper binaries from workspace master tomcat.
  3. Try to start any workspace with installers configured.
    Expected: Workspace failed to start with a message that failed to download bootstrapper binaries.
    Actual: Workspace failed to start because it reached timeout.
@sleshchenko sleshchenko added the kind/bug Outline of a bug - must adhere to the bug report template. label Nov 27, 2018
@slemeur slemeur removed ide6 labels Jul 1, 2019
@che-bot
Copy link
Contributor

che-bot commented Dec 30, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2019
@che-bot che-bot closed this as completed Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@slemeur @garagatyi @sleshchenko @che-bot