Question

通过hal deploy apply将Spinnaker部署到EKS时，Spinnaker Clouddriver pod转到CrashLoopBackOff并出现以下错误，

工厂方法“ awsProvider”抛出异常；嵌套异常是java.lang.NullPointerException：无法在空对象上获取属性“名称”

我的Halyard配置如下，

currentDeployment: default
deploymentConfigurations:
- name: default
  version: 1.17.6
  providers:
    appengine:
      enabled: false
      accounts: []
    aws:
      enabled: true
      accounts:
      - name: my-account
        requiredGroupMembership: []
        providerVersion: V1
        permissions: {}
        accountId: '010101010101' # my account id here
        regions: []
        assumeRole: Spinnaker-Clouddriver-Role
        lifecycleHooks: []
      primaryAccount: my-account
      bakeryDefaults:
        baseImages: []
      defaultKeyPairTemplate: '{{name}}-keypair'
      defaultRegions:
      - name: us-east-1
      defaults:
        iamRole: BaseIAMRole

我的Spinnaker-Clouddriver-Role IAM角色目前具有完全权限。我该如何解决？

这是完整日志https://gist.github.com/agentmilindu/cfbebffe46b93458df8158f9355e4041

Answer 1

这或多或少是一个猜测，因为您没有包含有关大三角帆设置的一个版本信息，但是...

根据要旨中的at com.netflix.spinnaker.clouddriver.aws.provider.agent.ReservationReportCachingAgent$_determineVpcOnlyAccounts_closure2.doCall(ReservationReportCachingAgent.groovy:117) ~[clouddriver-aws.jar:na]，它对应于getAmazonEC2(credentials, credentials.regions[0].name) in version 6.5.2

看来他们不容忍像您一样拥有空的regions: []；因此：

aws:
  enabled: true
  accounts:
  - name: my-account
    # ... snip ...
    # vvv-- update this list
    regions:
    - name: us-east-1

三角帆Clouddriver吊舱转到CrashLoopBackOff

1 个答案: