[jira] [Updated] (KARAF-7705) Karaf client failed without Stdin

["jincongho (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jincongho updated KARAF-7705:
-----------------------------
    Summary: Karaf client failed without Stdin  (was: Karaf client failed without TTY)

> Karaf client failed without Stdin
> ---------------------------------
>
>                 Key: KARAF-7705
>                 URL: https://issues.apache.org/jira/browse/KARAF-7705
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.4.4
>            Reporter: jincongho
>            Priority: Major
>              Labels: regresion
>
> I'm running the `karaf/bin/client [command]` as part of a Kubernetes startup script, but getting "Closed" error. There are similar issues reported here: [https://stackoverflow.com/questions/70355095/unable-to-run-client-command-for-apache-karaf-4-3-3-through-remote-server/76565804#76565804] 
> Quick repro:
> {code:java}
> >>> kubectl exec -it [pod] -c [container] -- /bin/sh -c "karaf/bin/client [command]"
> ***Output from Karaf command***
> >>> kubectl exec [pod] -c [container] -- /bin/sh -c "karaf/bin/client [command]"
> Closed
> command terminated with exit code 1{code}
> This happen after upgrading from Karaf 4.0.x. The root cause is a regression from [https://github.com/apache/karaf/commit/d6d503d2a59304115e23922bde6f72611dd054f0]
> This impact all `karaf/bin/client [command]` usage, which is a very useful feature. Current workaround is using batch mode `-b`, but supporting `karaf/bin/client [command]` will be clean and simple.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)