task devops status is failed (5/5)

**************************************************

Collecting installation results …

Task ‘devops’ failed:

******************************************************************************************************************************************************

{

“counter”: 144,

“created”: “2023-08-21T06:51:02.614318”,

“end_line”: 174,

“event”: “runner_on_failed”,

“event_data”: {

“duration”: 358.927904,

“end”: “2023-08-21T06:51:02.614178”,

“event_loop”: null,

“host”: “localhost”,

“ignore_errors”: null,

“play”: “localhost”,

“play_pattern”: “localhost”,

“play_uuid”: “5a2c0cae-f4e2-03f2-d5e4-000000000005”,

“playbook”: “/kubesphere/playbooks/devops.yaml”,

“playbook_uuid”: “baf97a20-304c-479d-bf83-06f4ec2e7581”,

“remote_addr”: “127.0.0.1”,

“res”: {

“_ansible_no_log”: false,

“attempts”: 3,

“changed”: true,

“cmd”: “# Delete Job migrate because ‘helm upgrade’ will try to update immutable fields of Job, which is not allowed. \n/usr/local/bin/kubectl delete job -n kubesphere-devops-system migrate –ignore-not-found\n\nks_devops_chart_version=0.1.19\ncharts_folder=/kubesphere/kubesphere/ks-devops/charts\nks_devops_chart=$charts_folder/ks-devops-$ks_devops_chart_version.tgz\n\n# Create or update CRDs manually\ntar xzvf $ks_devops_chart -C $charts_folder\n/usr/local/bin/kubectl apply -f $charts_folder/ks-devops/crds\n/usr/local/bin/kubectl apply -f $charts_folder/ks-devops/charts/s2i/crds\n\n# Import the templates seperately due the potential webhook issues\nrm -rf s2i-templates\nhelm template $charts_folder/ks-devops/charts/s2i/ -f /kubesphere/kubesphere/ks-devops/ks-devops-values.yaml -s templates/binary.yaml -s templates/java.yaml -s templates/nodejs.yaml -s templates/python.yaml -s templates/tomcat.yaml > s2i-templates\\templates.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/binary.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/java.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/nodejs.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/python.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/tomcat.yaml\n\n/usr/local/bin/helm upgrade –install devops $ks_devops_chart -n kubesphere-devops-system -f /kubesphere/kubesphere/ks-devops/ks-devops-values.yaml –wait\n\n/usr/local/bin/kubectl apply -f s2i-templates\\templates.yaml\n”,

“delta”: “0:01:08.264046”,

“end”: “2023-08-21 14:51:02.584872”,

“invocation”: {

“module_args”: {

“_raw_params”: “# Delete Job migrate because ‘helm upgrade’ will try to update immutable fields of Job, which is not allowed. \n/usr/local/bin/kubectl delete job -n kubesphere-devops-system migrate –ignore-not-found\n\nks_devops_chart_version=0.1.19\ncharts_folder=/kubesphere/kubesphere/ks-devops/charts\nks_devops_chart=$charts_folder/ks-devops-$ks_devops_chart_version.tgz\n\n# Create or update CRDs manually\ntar xzvf $ks_devops_chart -C $charts_folder\n/usr/local/bin/kubectl apply -f $charts_folder/ks-devops/crds\n/usr/local/bin/kubectl apply -f $charts_folder/ks-devops/charts/s2i/crds\n\n# Import the templates seperately due the potential webhook issues\nrm -rf s2i-templates\nhelm template $charts_folder/ks-devops/charts/s2i/ -f /kubesphere/kubesphere/ks-devops/ks-devops-values.yaml -s templates/binary.yaml -s templates/java.yaml -s templates/nodejs.yaml -s templates/python.yaml -s templates/tomcat.yaml > s2i-templates\\templates.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/binary.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/java.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/nodejs.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/python.yaml\nrm -rf $charts_folder/ks-devops/charts/s2i/templates/tomcat.yaml\n\n/usr/local/bin/helm upgrade –install devops $ks_devops_chart -n kubesphere-devops-system -f /kubesphere/kubesphere/ks-devops/ks-devops-values.yaml –wait\n\n/usr/local/bin/kubectl apply -f s2i-templates\\templates.yaml\n”,

“_uses_shell”: true,

“argv”: null,

“chdir”: null,

“creates”: null,

“executable”: “/bin/bash”,

“removes”: null,

“stdin”: null,

“stdin_add_newline”: true,

“strip_empty_ends”: true,

“warn”: true

}

“msg”: “non-zero return code”,

“rc”: 1,

“start”: “2023-08-21 14:49:54.320826”,

“stderr”: "W0821 14:50:01.414810 48025 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob\nW0821 14:50:01.416351 48025 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob\nW0821 14:50:01.419751 48025 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob\nError: UPGRADE FAILED: cannot patch \“binary\” with kind S2iBuilderTemplate: Internal error occurred: failed calling webhook \“s2ibuildertemplate.kb.io\”: Post \“https://webhook-server-service.kubesphere-devops-system.svc:443/validate-devops-kubesphere-io-v1alpha1-s2ibuildertemplate?timeout=10s\”: context deadline exceeded\nWarning: resource s2ibuildertemplates/binary is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create –save-config or kubectl apply. The missing annotation will be patched automatically.\nWarning: resource s2ibuildertemplates/java is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create –save-config or kubectl apply. The missing annotation will be patched automatically.\nWarning: resource s2ibuildertemplates/nodejs is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create –save-config or kubectl apply. The missing annotation will be patched automatically.\nWarning: resource s2ibuildertemplates/python is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create –save-config or kubectl apply. The missing annotation will be patched automatically.\nWarning: resource s2ibuildertemplates/tomcat is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create –save-config or kubectl apply. The missing annotation will be patched automatically.\nError from server (InternalError): error when applying patch:\n{\“metadata\”:{\“annotations\”:{\“kubectl.kubernetes.io/last-applied-configuration\”:\"{\\\“apiVersion\\\”:\\\“devops.kubesphere.io/v1alpha1\\\”,\\\“kind\\\”:\\\“S2iBuilderTemplate\\\”,\\\“metadata\\\”:{\\\“annotations\\\”:{\\\“descriptionCN\\\”:\\\“\u4e8c\u8fdb\u5236\u6587\u4ef6\u7684\u6784\u5efa\u5668\u6a21\u7248\\\”,\\\“descriptionEN\\\”:\\\“This is a builder template for binary build\\\”,\\\“devops.kubesphere.io/s2i-template-url\\\”:\\\“https://github.com/kubesphere/s2i-binary-container\\\\\\"},\\\\\\"labels\\\\\\":{\\\\\\"binary-type.kubesphere.io\\\\\\":\\\\\\"binary\\\\\\",\\\\\\"builder-type.kubesphere.io/b2i\\\\\\":\\\\\\"b2i\\\\\\",\\\\\\"controller-tools.k8s.io\\\\\\":\\\\\\"1.0\\\\\\"},\\\\\\"name\\\\\\":\\\\\\"binary\\\\\\"},\\\\\\"spec\\\\\\":{\\\\\\"codeFramework\\\\\\":\\\\\\"binary\\\\\\",\\\\\\"containerInfo\\\":[{\\\“builderImage\\\”:\\\“kubesphere/s2i-binary:v3.2.0\\\”}],\\\“defaultBaseImage\\\”:\\\“kubesphere/s2i-binary:v3.2.0\\\”,\\\“description\\\”:\\\“This is a builder template for binary build\\\”,\\\“environment\\\”:[{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“Arguments to use when calling binary,\\\”,\\\“key\\\”:\\\“ARGS\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”}],\\\“iconPath\\\”:\\\“assets/binary.png\\\”,\\\“version\\\”:\\\“0.0.1\\\”}}\\n\"}}}\nto:\nResource: \“devops.kubesphere.io/v1alpha1, Resource=s2ibuildertemplates\”, GroupVersionKind: \“devops.kubesphere.io/v1alpha1, Kind=S2iBuilderTemplate\”\nName: \“binary\”, Namespace: \“\”\nfor: \“s2i-templatestemplates.yaml\”: Internal error occurred: failed calling webhook \“s2ibuildertemplate.kb.io\”: Post \“https://webhook-server-service.kubesphere-devops-system.svc:443/validate-devops-kubesphere-io-v1alpha1-s2ibuildertemplate?timeout=10s\”: context deadline exceeded\nError from server (InternalError): error when applying patch:\n{\“metadata\”:{\“annotations\”:{\“kubectl.kubernetes.io/last-applied-configuration\”:\"{\\\“apiVersion\\\”:\\\“devops.kubesphere.io/v1alpha1\\\”,\\\“kind\\\”:\\\“S2iBuilderTemplate\\\”,\\\“metadata\\\”:{\\\“annotations\\\”:{\\\“descriptionCN\\\”:\\\“Java \u5e94\u7528\u7684\u6784\u5efa\u5668\u6a21\u7248\u3002\u901a\u8fc7\u8be5\u6a21\u7248\u53ef\u6784\u5efa\u51fa\u76f4\u63a5\u8fd0\u884c\u7684\u5e94\u7528\u955c\u50cf\u3002\\\”,\\\“descriptionEN\\\”:\\\"This is a builder template for Java builds whose result can be run directly without any further application server.It’s suited ideally for microservices with a flat classpath (including \\\\\\\“far jars\\\\\\\”).\\\",\\\“devops.kubesphere.io/s2i-template-url\\\”:\\\“https://github.com/kubesphere/s2i-java-container/blob/master/java/images\\\\\\",\\\\\\"helm.sh/hook\\\\\\":\\\\\\"pre-install\\\\\\"},\\\\\\"labels\\\\\\":{\\\\\\"binary-type.kubesphere.io\\\\\\":\\\\\\"jar\\\\\\",\\\\\\"builder-type.kubesphere.io/b2i\\\\\\":\\\\\\"b2i\\\\\\",\\\\\\"builder-type.kubesphere.io/s2i\\\\\\":\\\\\\"s2i\\\\\\",\\\\\\"controller-tools.k8s.io\\\\\\":\\\\\\"1.0\\\\\\"},\\\\\\"name\\\\\\":\\\\\\"java\\\\\\"},\\\\\\"spec\\\\\\":{\\\\\\"codeFramework\\\\\\":\\\\\\"java\\\\\\",\\\\\\"containerInfo\\\":[{\\\“buildVolumes\\\”:[\\\“s2i_java_cache:/tmp/artifacts\\\”],\\\“builderImage\\\”:\\\“kubesphere/java-8-centos7:v3.2.0\\\”,\\\“runtimeArtifacts\\\”:[{\\\“source\\\”:\\\“/deployments\\\”}],\\\“runtimeImage\\\”:\\\“kubesphere/java-8-runtime:v3.2.0\\\”},{\\\“buildVolumes\\\”:[\\\“s2i_java_cache:/tmp/artifacts\\\”],\\\“builderImage\\\”:\\\“kubesphere/java-11-centos7:v3.2.0\\\”,\\\“runtimeArtifacts\\\”:[{\\\“source\\\”:\\\“/deployments\\\”}],\\\“runtimeImage\\\”:\\\“kubesphere/java-11-runtime:v3.2.0\\\”}],\\\“defaultBaseImage\\\”:\\\“kubesphere/java-8-centos7:v3.2.0\\\”,\\\“description\\\”:\\\"This is a builder template for Java builds whose result can be run directly without any further application server.It’s suited ideally for microservices with a flat classpath (including \\\\\\\“far jars\\\\\\\”)\\\",\\\“environment\\\”:[{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“Arguments to use when calling Maven, replacing the default package hawt-app:build -DskipTests -e. Please be sure to run the hawt-app:build goal (when not already bound to the package execution phase), otherwise the startup scripts won’t work.\\\”,\\\“key\\\”:\\\“MAVEN_ARGS\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“Additional Maven arguments, useful for temporary adding arguments like -X or -am -pl .\\\”,\\\“key\\\”:\\\“MAVEN_ARGS_APPEND\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“With Repositories you specify from which locations you want to download certain artifacts, such as dependencies and maven-plugins.\\\”,\\\“key\\\”:\\\“MAVEN_MIRROR_URL\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“If set then the Maven repository is removed after the artifact is built. This is useful for keeping the created application image small, but prevents incremental builds. The default is false\\\”,\\\“key\\\”:\\\“MAVEN_CLEAR_REPO\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“boolean\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“Path to target/ where the jar files are created for multi module builds. These are added to ${MAVEN_ARGS}\\\”,\\\“key\\\”:\\\“ARTIFACT_DIR\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“Arguments to use when copying artifacts from the output dir to the application dir. Useful to specify which artifacts will be part of the image. It defaults to -r hawt-app/* when a hawt-app dir is found on the build directory, otherwise jar files only will be included (*.jar).\\\”,\\\“key\\\”:\\\“ARTIFACT_COPY_ARGS\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“the directory where the application resides. All paths in your application are relative to this directory. By default it is the same directory where this startup script resides.\\\”,\\\“key\\\”:\\\“JAVA_APP_DIR\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\“directory holding the Java jar files as well an optional classpath file which holds the classpath. Either as a single line classpath (colon separated) or with jar files listed line-by-line. If not set JAVA_LIB_DIR is the same as JAVA_APP_DIR.\\\”,\\\“key\\\”:\\\“JAVA_LIB_DIR\\\”,\\\“required\\\”:false,\\\“type\\\”:\\\“string\\\”},{\\\“defaultValue\\\”:\\\“\\\”,\\\“description\\\”:\\\"options to add when calling