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

Shutting down JKube remote dev is crashing #2004

Closed
sunix opened this issue Jan 16, 2023 · 1 comment · Fixed by #2017
Closed

Shutting down JKube remote dev is crashing #2004

sunix opened this issue Jan 16, 2023 · 1 comment · Fixed by #2017
Assignees
Labels
bug Something isn't working
Milestone

Comments

@sunix
Copy link
Member

sunix commented Jan 16, 2023

Describe the bug

Shutting down (Ctrl-C) the remote-dev is crashing. The cluster is not set back to the normal state.

Eclipse JKube version

1.10.0

Component

Kubernetes Maven Plugin

Apache Maven version

other (please specify in additional context)

Gradle version

None

Steps to reproduce

  1. Follow the https://github.com/marcnuri-demo/jkube-remote-dev#remote-dev-demo-walk-through demo walk-through to the step Stop the remote-dev by typing Ctrl-c in the terminal where it has been started
  2. Hitting Ctrl-C, the exception is raised:
    [INFO] Server announced support for publickey-hostbound@openssh.com version 0
    [INFO] k8s: Kubernetes Service northwind-db:5432 is now available at local port 5432
    [INFO] k8s: Kubernetes Service rabbit-mq:5672 is now available at local port 15672
    [INFO] k8s: Local port '8080' is now available as a Kubernetes Service at northwind:8080
    ^C[Exception in thread "Thread-2" java.lang.NumberFormatException: For input string: "0m"
    	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
    	at java.base/java.lang.Integer.parseInt(Integer.java:668)
    	at java.base/java.lang.Integer.valueOf(Integer.java:999)
    	at org.fusesource.jansi.io.AnsiOutputStream.write(AnsiOutputStream.java:199)
    	at java.base/java.io.FilterOutputStream.write(FilterOutputStream.java:137)
    	at java.base/java.io.PrintStream.write(PrintStream.java:568)
    	at java.base/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:234)
    	at java.base/sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:313)
    	at java.base/sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:111)
    	at java.base/java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:178)
    	at java.base/java.io.PrintStream.write(PrintStream.java:699)
    	at java.base/java.io.PrintStream.print(PrintStream.java:863)
    	at java.base/java.io.PrintStream.println(PrintStream.java:1031)
    	at org.slf4j.impl.SimpleLogger.write(SimpleLogger.java:341)
    	at org.slf4j.impl.SimpleLogger.log(SimpleLogger.java:310)
    	at org.slf4j.impl.SimpleLogger.info(SimpleLogger.java:504)
    	at org.apache.maven.cli.logging.Slf4jLogger.info(Slf4jLogger.java:59)
    	at org.apache.maven.monitor.logging.DefaultLog.info(DefaultLog.java:68)
    	at org.eclipse.jkube.kit.common.util.AnsiLogger.info(AnsiLogger.java:98)
    	at org.eclipse.jkube.kit.remotedev.RemoteDevelopmentService.stop(RemoteDevelopmentService.java:56)
    	at org.eclipse.jkube.maven.plugin.mojo.develop.RemoteDevMojo.lambda$executeInternal$0(RemoteDevMojo.java:46)
    	at java.base/java.lang.Thread.run(Thread.java:833)
    

Expected behavior

  1. It should stop properly with no errors.
  2. It should tell the user how to restore the state manually.

Runtime

OpenShift

Kubernetes API Server version

other (please specify in additional context)

Environment

Dev Sandbox (workspaces.openshift.com)

Eclipse JKube Logs

No response

Sample Reproducer Project

No response

Additional context

No response

@sunix sunix added the bug Something isn't working label Jan 16, 2023
@manusa manusa self-assigned this Jan 25, 2023
@manusa manusa added this to the 1.11.0 milestone Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants