如何解决通过字段 'schedulerService' 表示的未满足的依赖关系？
How to resolve Unsatisfied dependency expressed through field 'schedulerService'?
我正在尝试将 custom built SCDF2.5.1（添加 oracle 驱动程序）安装到 openshift 中（遵循 SCDF 的 Kubectl 安装文档）。我修改了 deployment.yaml 以从 git 存储库中提取我的这个自定义 SCDF docker 图像。现在，当我启动容器时，出现以下错误
INFO org.hibernate.dialect.Dialect.<init> - HHH000400: Using dialect: org.hibernate.dialect.Oracle12cDialect
INFO org.hibernate.engine.transaction.jta.platform.internal.JtaPlatformInitiator.initiateService - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.buildNativeEntityManagerFactory - Initialized JPA EntityManagerFactory for persistence unit 'default'
INFO org.springframework.cloud.dataflow.configuration.metadata.ApplicationConfigurationMetadataResolverAutoConfiguration.registryConfigurationMap - Final Registry Configurations: {registry-1.docker.io=RegistryConfiguration{registryHost='registry-1.docker.io', user='null', secret='****'', authorizationType=dockeroauth2, manifestMediaType='application/vnd.docker.distribution.manifest.v2+json', disableSslVerification='false', extra={registryAuthUri=https://auth.docker.io/token?service=registry.docker.io&scope=repository:{repository}:pull&offline_token=1&client_id=shell}}}
WARN org.springframework.cloud.dataflow.server.config.features.SchedulerConfiguration.primaryTaskPlatform - TaskPlatform Kubernetes is selected as primary but has no TaskLaunchers configured
WARN org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext.refresh - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.cloud.dataflow.server.config.features.TaskConfiguration': Unsatisfied dependency expressed through field 'schedulerService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulerService' defined in class path resource [org/springframework/cloud/dataflow/server/config/features/SchedulerConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.cloud.dataflow.server.service.SchedulerService]: Factory method 'schedulerService' threw exception; nested exception is java.lang.IllegalStateException: No valid primary TaskPlatform configured
INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.destroy - Closing JPA EntityManagerFactory for persistence unit 'default'
INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown initiated...
INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown completed.
INFO org.apache.catalina.core.StandardService.log - Stopping service [Tomcat]
ERROR
我看到一个与此相关的线程 post 其中 fix 被提供给 spring-cloud-dataflow-server-kubernetes 和 spring-cloud-dataflow -server-kubernetes-autoconfigure 项目。但我不确定这些更改是否适用于自定义构建 2.5.1 版本。我还检查了我的 deployment.yaml 并且切换 "SPRING_CLOUD_DATAFLOW_FEATURES_SCHEDULES_ENABLED" 设置为 true。
在 deployment.yaml 中，我删除了数据库服务和配置，也删除了 scdf-server 配置，因为我在构建 docker 映像本身时在 application.properties 中添加了驱动程序属性.下面是内置在 scdf jar 中的 deployment.yaml 和 application.properties 文件。仅供参考，从 deployment.yaml 中删除 scdf-server 配置对失败没有影响。上述异常保持不变。还删除了船长 URI。
deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: customscdf-image
labels:
app: customscdf-image
spec:
selector:
matchLabels:
app: customscdf-image
replicas: 1
template:
metadata:
labels:
app: customscdf-image
spec:
containers:
- name: customscdf-image
image: docker-registry.default.svc:5000/scdfadmin/customscdf-image
imagePullPolicy: Always
ports:
- containerPort: 80
livenessProbe:
httpGet:
path: /management/health
port: 80
initialDelaySeconds: 45
readinessProbe:
httpGet:
path: /management/info
port: 80
initialDelaySeconds: 45
resources:
limits:
cpu: 1.0
memory: 2048Mi
requests:
cpu: 0.5
memory: 1024Mi
env:
- name: KUBERNETES_NAMESPACE
valueFrom:
fieldRef:
fieldPath: "metadata.namespace"
- name: SERVER_PORT
value: '80'
- name: SPRING_CLOUD_CONFIG_ENABLED
value: 'false'
- name: SPRING_CLOUD_DATAFLOW_FEATURES_ANALYTICS_ENABLED
value: 'true'
- name: SPRING_CLOUD_DATAFLOW_FEATURES_SCHEDULES_ENABLED
value: 'true'
- name: SPRING_CLOUD_DATAFLOW_TASK_COMPOSED_TASK_RUNNER_URI
value: 'docker://springcloud/spring-cloud-dataflow-composed-task-runner:2.6.0.BUILD-SNAPSHOT'
- name: SPRING_CLOUD_KUBERNETES_CONFIG_ENABLE_API
value: 'false'
- name: SPRING_CLOUD_KUBERNETES_SECRETS_ENABLE_API
value: 'false'
- name: SPRING_CLOUD_KUBERNETES_SECRETS_PATHS
value: /etc/secrets
- name: SPRING_CLOUD_DATAFLOW_SERVER_URI
value: '${HOST_NAME}:9393'
# Add Maven repo for metadata artifact resolution for all stream apps
- name: SPRING_APPLICATION_JSON
value: "{ \"maven\": { \"local-repository\": null, \"remote-repositories\": { \"repo1\": { \"url\": \"https://repo.spring.io/libs-snapshot\"} } } }"
serviceAccountName: scdf-sa
application.properties
spring.application.name=CUSTOMSCDF
spring.datasource.url=DATASOURCE_URL_FOR_ORACLE_DB
spring.datasource.username=user_name
spring.datasource.password=PASSWORD
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver
spring.flyway.enabled=false
spring.jpa.show-sql=true
spring.jpa.hibernate.use-new-id-generator-mappings=true
logging.level.root=info
logging.file.max-size=5GB
logging.file.max-history=30
logging.pattern.console=%d{dd-MM-yyyy HH:mm:ss.SSS} [%thread] %-5level %logger.%M - %msg%n
Dockerfile - 将构建为上面使用的 customscdf-image
FROM maven:3.5.2-jdk-8-alpine AS MAVEN_BUILD
COPY pom.xml /build/
COPY src /build/src/
WORKDIR /build/
RUN mvn package
FROM openjdk:8-jre-alpine
WORKDIR /app
COPY --from=MAVEN_BUILD /build/target/custom-0.0.1-SNAPSHOT.jar /app/
ENTRYPOINT ["java", "-jar", "custom-0.0.1-SNAPSHOT.jar"]
那么我在这里做错了什么或遗漏了什么？请指教
提前致谢。
您很可能缺少任务平台配置 server-config.yaml，它是 k8s 部署文件的一部分。当您使用自己的 application.properties 文件时，我感觉您没有使用那个 k8s 配置文件。
出于某种原因，此自定义构建不读取服务器-config.yaml。即使它在 server-deployment.yaml 中显示为配置映射之一。所以我将 kubenetes 任务平台属性移动到 CustomBuild SCDF Spring 引导项目的 application.properties。所以我从这个项目构建的 docker 图像也具有 kubernetes 属性。添加此后，server-deployment.yaml 能够获取 k8 平台属性并且 SCDF 成功启动 运行。
我的 application.properties 目前如下所示。
spring.application.name=CustomSCDF
spring.datasource.url=jdbc:oracle:thin:@datasource_url
spring.datasource.username=username
spring.datasource.password=Password
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver
#properties moved from server-config.yaml
spring.cloud.dataflow.task.platform.kubernetes.accounts.default.image-pull-policy= always
spring.cloud.dataflow.task.platform.kubernetes.accounts.default.entry-point-style= exec
spring.cloud.dataflow.task.platform.kubernetes.accounts.default.limits.cpu=4
我认为只有自定义构建的应用程序才会面临这个问题。但这需要更清楚。
我正在尝试将 custom built SCDF2.5.1（添加 oracle 驱动程序）安装到 openshift 中（遵循 SCDF 的 Kubectl 安装文档）。我修改了 deployment.yaml 以从 git 存储库中提取我的这个自定义 SCDF docker 图像。现在，当我启动容器时，出现以下错误
INFO org.hibernate.dialect.Dialect.<init> - HHH000400: Using dialect: org.hibernate.dialect.Oracle12cDialect
INFO org.hibernate.engine.transaction.jta.platform.internal.JtaPlatformInitiator.initiateService - HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.buildNativeEntityManagerFactory - Initialized JPA EntityManagerFactory for persistence unit 'default'
INFO org.springframework.cloud.dataflow.configuration.metadata.ApplicationConfigurationMetadataResolverAutoConfiguration.registryConfigurationMap - Final Registry Configurations: {registry-1.docker.io=RegistryConfiguration{registryHost='registry-1.docker.io', user='null', secret='****'', authorizationType=dockeroauth2, manifestMediaType='application/vnd.docker.distribution.manifest.v2+json', disableSslVerification='false', extra={registryAuthUri=https://auth.docker.io/token?service=registry.docker.io&scope=repository:{repository}:pull&offline_token=1&client_id=shell}}}
WARN org.springframework.cloud.dataflow.server.config.features.SchedulerConfiguration.primaryTaskPlatform - TaskPlatform Kubernetes is selected as primary but has no TaskLaunchers configured
WARN org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext.refresh - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.cloud.dataflow.server.config.features.TaskConfiguration': Unsatisfied dependency expressed through field 'schedulerService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulerService' defined in class path resource [org/springframework/cloud/dataflow/server/config/features/SchedulerConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.cloud.dataflow.server.service.SchedulerService]: Factory method 'schedulerService' threw exception; nested exception is java.lang.IllegalStateException: No valid primary TaskPlatform configured
INFO org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.destroy - Closing JPA EntityManagerFactory for persistence unit 'default'
INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown initiated...
INFO com.zaxxer.hikari.HikariDataSource.close - HikariPool-1 - Shutdown completed.
INFO org.apache.catalina.core.StandardService.log - Stopping service [Tomcat]
ERROR
我看到一个与此相关的线程 post 其中 fix 被提供给 spring-cloud-dataflow-server-kubernetes 和 spring-cloud-dataflow -server-kubernetes-autoconfigure 项目。但我不确定这些更改是否适用于自定义构建 2.5.1 版本。我还检查了我的 deployment.yaml 并且切换 "SPRING_CLOUD_DATAFLOW_FEATURES_SCHEDULES_ENABLED" 设置为 true。
在 deployment.yaml 中，我删除了数据库服务和配置，也删除了 scdf-server 配置，因为我在构建 docker 映像本身时在 application.properties 中添加了驱动程序属性.下面是内置在 scdf jar 中的 deployment.yaml 和 application.properties 文件。仅供参考，从 deployment.yaml 中删除 scdf-server 配置对失败没有影响。上述异常保持不变。还删除了船长 URI。
deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: customscdf-image
labels:
app: customscdf-image
spec:
selector:
matchLabels:
app: customscdf-image
replicas: 1
template:
metadata:
labels:
app: customscdf-image
spec:
containers:
- name: customscdf-image
image: docker-registry.default.svc:5000/scdfadmin/customscdf-image
imagePullPolicy: Always
ports:
- containerPort: 80
livenessProbe:
httpGet:
path: /management/health
port: 80
initialDelaySeconds: 45
readinessProbe:
httpGet:
path: /management/info
port: 80
initialDelaySeconds: 45
resources:
limits:
cpu: 1.0
memory: 2048Mi
requests:
cpu: 0.5
memory: 1024Mi
env:
- name: KUBERNETES_NAMESPACE
valueFrom:
fieldRef:
fieldPath: "metadata.namespace"
- name: SERVER_PORT
value: '80'
- name: SPRING_CLOUD_CONFIG_ENABLED
value: 'false'
- name: SPRING_CLOUD_DATAFLOW_FEATURES_ANALYTICS_ENABLED
value: 'true'
- name: SPRING_CLOUD_DATAFLOW_FEATURES_SCHEDULES_ENABLED
value: 'true'
- name: SPRING_CLOUD_DATAFLOW_TASK_COMPOSED_TASK_RUNNER_URI
value: 'docker://springcloud/spring-cloud-dataflow-composed-task-runner:2.6.0.BUILD-SNAPSHOT'
- name: SPRING_CLOUD_KUBERNETES_CONFIG_ENABLE_API
value: 'false'
- name: SPRING_CLOUD_KUBERNETES_SECRETS_ENABLE_API
value: 'false'
- name: SPRING_CLOUD_KUBERNETES_SECRETS_PATHS
value: /etc/secrets
- name: SPRING_CLOUD_DATAFLOW_SERVER_URI
value: '${HOST_NAME}:9393'
# Add Maven repo for metadata artifact resolution for all stream apps
- name: SPRING_APPLICATION_JSON
value: "{ \"maven\": { \"local-repository\": null, \"remote-repositories\": { \"repo1\": { \"url\": \"https://repo.spring.io/libs-snapshot\"} } } }"
serviceAccountName: scdf-sa
application.properties
spring.application.name=CUSTOMSCDF
spring.datasource.url=DATASOURCE_URL_FOR_ORACLE_DB
spring.datasource.username=user_name
spring.datasource.password=PASSWORD
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver
spring.flyway.enabled=false
spring.jpa.show-sql=true
spring.jpa.hibernate.use-new-id-generator-mappings=true
logging.level.root=info
logging.file.max-size=5GB
logging.file.max-history=30
logging.pattern.console=%d{dd-MM-yyyy HH:mm:ss.SSS} [%thread] %-5level %logger.%M - %msg%n
Dockerfile - 将构建为上面使用的 customscdf-image
FROM maven:3.5.2-jdk-8-alpine AS MAVEN_BUILD
COPY pom.xml /build/
COPY src /build/src/
WORKDIR /build/
RUN mvn package
FROM openjdk:8-jre-alpine
WORKDIR /app
COPY --from=MAVEN_BUILD /build/target/custom-0.0.1-SNAPSHOT.jar /app/
ENTRYPOINT ["java", "-jar", "custom-0.0.1-SNAPSHOT.jar"]
那么我在这里做错了什么或遗漏了什么？请指教
提前致谢。
您很可能缺少任务平台配置 server-config.yaml，它是 k8s 部署文件的一部分。当您使用自己的 application.properties 文件时，我感觉您没有使用那个 k8s 配置文件。
出于某种原因，此自定义构建不读取服务器-config.yaml。即使它在 server-deployment.yaml 中显示为配置映射之一。所以我将 kubenetes 任务平台属性移动到 CustomBuild SCDF Spring 引导项目的 application.properties。所以我从这个项目构建的 docker 图像也具有 kubernetes 属性。添加此后，server-deployment.yaml 能够获取 k8 平台属性并且 SCDF 成功启动 运行。
我的 application.properties 目前如下所示。
spring.application.name=CustomSCDF
spring.datasource.url=jdbc:oracle:thin:@datasource_url
spring.datasource.username=username
spring.datasource.password=Password
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver
#properties moved from server-config.yaml
spring.cloud.dataflow.task.platform.kubernetes.accounts.default.image-pull-policy= always
spring.cloud.dataflow.task.platform.kubernetes.accounts.default.entry-point-style= exec
spring.cloud.dataflow.task.platform.kubernetes.accounts.default.limits.cpu=4
我认为只有自定义构建的应用程序才会面临这个问题。但这需要更清楚。