odo: First push of long-running build fails to start the Java program in the pod

[kind/bug]

What versions of software are you using?

  • Operating System: Windows 10
  • Output of odo version: odo v0.0.20 (bd3e74a4) Server: https://172.18.93.45:8443 Kubernetes: v1.11.0+d4cacc0

How did you run odo exactly?

using VS Code OpenShift connector

Actual behavior

using VS Code OpenShift connector extension.

if we try to do another push, the application is well started

Expected behavior

when build is finished, the jar is found in /deployments and the application is available

Any logs, error output, etc?

the pod logs is showing several errors of not finding any jars in /deployments. Before the build has finished, there is no more logs that are incoming. Looks alike it doesn’t try to start the jar anymore.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 19 (17 by maintainers)

Most upvoted comments

@dharmit The OpenShift Connector currently uses odo 0.0.20 and will remain so for the latest release as well. As migrating to odo beta requires breaking changes and workflow change too, that work is still in progress. So the install will always prompt to use the functionality of odo 0.0.20.