search cancel

AuthenticationHub missing docker image

book

Article ID: 255845

calendar_today

Updated On:

Products

VIP Authentication Hub

Issue/Introduction

For 1.0.3172 we are unable to download the secrets-initializer image

Status : 400

Error : 400 Bad Request
{"message":"Docker preparing for build in agent : rt10b10357dv00.bnymellon.net\nDocker building :/tmp/6965ed8d-1973-4d72-b5b8-59fd85b52c12Sending build context to Docker daemon14.25MB\r\r\nStep 1/1 : FROM securityservices.packages.broadcom.com/ssp-vault-secrets-initializer:1.0.3172\nmanifest for securityservices.packages.broadcom.com/ssp-vault-secrets-initializer:1.0.3172 not found: manifest unknown: The named manifest is not known to the registry.\n\nDocker build Failed for image abcd/linux/bxp/ae/vendor/ssp-vault-secrets-initializer:1.0.3172-SNAPSHOT\nFailed to complete!"}

from ssp helm charts, values.yaml

vaultSecretsInitializer:
    imageRepository: "securityservices.packages.broadcom.com/ssp-vault-secrets-initializer"
    imageTag: 1.0.3172
    imageDigest: "sha256:722a9e69a37846e959897b02f479fdfa9a109bd8fe077fddf87bc59a810d4c5a"
    logLevel: INFO
    pauseOnFailureInMillis: ""
    env:
      appLogLevel: INFO
      rootLogLevel: WARN
      jvmOpts: ""
    resources:
      limits:
        cpu: 400m
        memory: 1Gi
      requests:
        cpu: 200m
        memory: 1Gi

Any idea ? 

Environment

Release : 1.0.3172

Resolution

This is conditional on the vault.enabled feature flag which is disabled by default.   This is used for a reason that is not related to any specific customer.  It is understood that such overloading creates customer confusion so we have fixed this and the image is accessible now.