You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2020/05/18 02:22:00 UTC

[jira] [Closed] (FLINK-15798) Running ./bin/kubernetes-session.sh -Dkubernetes.cluster-id= -Dexecution.attached=true fails with exception

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

Yang Wang closed FLINK-15798.
-----------------------------
    Resolution: Cannot Reproduce

> Running ./bin/kubernetes-session.sh -Dkubernetes.cluster-id=<CLUSTER-ID> -Dexecution.attached=true fails with exception
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-15798
>                 URL: https://issues.apache.org/jira/browse/FLINK-15798
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Priority: Major
>             Fix For: 1.11.0, 1.10.2
>
>
> Running {{./bin/kubernetes-session.sh -Dkubernetes.cluster-id=<CLUSTER-ID> -Dexecution.attached=true}} fails with 
> {code}
> 2020-01-28 15:04:28,669 ERROR org.apache.flink.kubernetes.cli.KubernetesSessionCli          - Error while running the Flink session.
> io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://35.234.77.125/api/v1/namespaces/default/services/testing. Message: Unauthorized! Token may have expired! Please log-in again. Unauthorized.
> 	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510)
> 	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:447)
> 	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413)
> 	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372)
> 	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:337)
> 	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:318)
> 	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleGet(BaseOperation.java:812)
> 	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.getMandatory(BaseOperation.java:220)
> 	at io.fabric8.kubernetes.client.dsl.base.BaseOperation.get(BaseOperation.java:164)
> 	at org.apache.flink.kubernetes.kubeclient.Fabric8FlinkKubeClient.getService(Fabric8FlinkKubeClient.java:330)
> 	at org.apache.flink.kubernetes.kubeclient.Fabric8FlinkKubeClient.getInternalService(Fabric8FlinkKubeClient.java:243)
> 	at org.apache.flink.kubernetes.cli.KubernetesSessionCli.run(KubernetesSessionCli.java:104)
> 	at org.apache.flink.kubernetes.cli.KubernetesSessionCli.lambda$main$0(KubernetesSessionCli.java:185)
> 	at org.apache.flink.runtime.security.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:30)
> 	at org.apache.flink.kubernetes.cli.KubernetesSessionCli.main(KubernetesSessionCli.java:185)
> {code}
> even though {{echo "stop" | ./bin/kubernetes-session.sh -Dkubernetes.cluster-id=<CLUSTER-ID> -Dexecution.attached=true}} succeeds with my setup. This is strange as I would expect that the former call should do exactly the same as the second except for sending the "stop" command right away. I think we should check whether this is a real problem or only specific to my setup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)