After deployment, the workflow was created incorrectly

[liuzhiyuan0502]

Let me ask you a question：After deployment, the workflow was created incorrectly.
Error Message:
Warning code: 50032，Warning message: Try to ask Linkis forcreating a new contextld failed Linkis error msg:HttpClientResultException:errCode: 10905desc.URL/api/rest_j/v1/contextservice/createContextlDrequestfailed!1ResponseBodyfmethod":"/api/rest_j/1/contextservice/createConSupplied VIP Address cannot be null","data":[data":null. errCode: 10905 ,desc: URL/api/rest_j/v1/contextservice/createContextlDrequestfailed!ResponseBodyIsmethod":"/api/rest j/1/contextservice/createConSupplied VIP Address cannot be null","data".data"null.,ip: dss-service ,port: 9003serviceKinddss-framework-orchestrator-dss-service ,port: 9003server-devip:serviceKind.dss-framework-orchestrator-server-dev.

Originally posted by @15259236303 in #3944 (comment)

[github-actions]

😊 Welcome to the Apache Linkis community!!

We are glad that you are contributing by opening this issue.

Please make sure to include all the relevant context.
We will be here shortly.

If you are interested in contributing to our website project, please let us know!
You can check out our contributing guide on
👉 How to Participate in Project Contribution.

Community

WeChat Assistant	WeChat Public Account

Mailing Lists

Name	Description	Subscribe	Unsubscribe	Archive
dev@linkis.apache.org	community activity information	subscribe	unsubscribe	archive

[binbinCheng]

Hello! You failed to create ContextID. It is recommended to check whether the parameters are correct when creating

[QuantumXiecao]

This problem is due to linkis-gateway-server-support-1.1.1.jar version incompatible as depicted by the following picture:

So Eureka could not extract services by the ps-cs which is the service name of early version(Currently it should be LINKIS-PS-PUBLICSERVICE)
You should go into the linkis install directory下lib/linkis-spring-cloud-services/linkis-mg-gateway to check linkis-gateway-server-support jar=>You should keep 1.3.* and delete 1.1.* releated jars. After restarting mg-gateway(sh sbin/linkis-daemon.sh restart mg-gateway), you can continue your job. @liuzhiyuan0502

I have tested it which is shown as:

[QuantumXiecao]

Of course this problem in essence is due to the released linkis has duplicate jars(url:http://mirrors.obs.cn-north-276.intelligentmininglab.com/apache/linkis/apache-linkis-1.3.0-incubating-bin.tar.gz):

Users who download this linkis tar might encounter the same problem.
Strongly recommend redistribute one new 1.3.0 release jar as quickly as possible.
@binbinCheng @peacewong

[liuzhiyuan0502]

Thank you very much for your guidance!

[casionone]

Thanks!
Already published binary packages cannot be re-covered
This has been fixed in version 1.3.1

[casionone]

I will close this issue. You can reopen if necessary