Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StatefulSet artifactory-ha-jfrog-deployme-artifactory-ha-member failed. Not found: "gcpcreds-json" #1873

Closed
abhisheksama opened this issue Apr 11, 2024 · 2 comments
Assignees

Comments

@abhisheksama
Copy link

Is this a request for help?:


Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG REPORT

Version of Helm and Kubernetes:
107.77.6

Which chart:
artifactory-ha

Which product license (Enterprise/Pro/oss):
Enterprise

JFrog support reference (if already raised with support team):

What happened:
I was trying to upgrade the artifactory HA version to 107.77.6 chart version using Argo CD. The artifactory-ha-member
throwed an error saying "gcp-cred.json" not found and so I deleted the pv and tried to recreate it to resolve the error but it throws the same error again. Upon looking I found that the gcp-cred.json is not being defined under spec.volumes here unlike the primary sts here. After manually [2] under "volumes" I was able to resolve the error.

[1]:
create Pod artifactory-ha-jfrog-deployme-artifactory-ha-member-0 in StatefulSet artifactory-ha-jfrog-deployme-artifactory-ha-member failed error: Pod "artifactory-ha-jfrog-deployme-artifactory-ha-member-0" is invalid: [spec.containers[6].volumeMounts[2].name: Not found: "gcpcreds-json", spec.initContainers[3].volumeMounts[5].name: Not found: "gcpcreds-json"]

[2]

  • name: gcpcreds-json
    secret:
    defaultMode: 420
    secretName: artifactory-gcp-storage-creds-csi-managed-secret

What you expected to happen:

I expect it to create [2] under volumes so that the secret can be used through mountpath

How to reproduce it (as minimally and precisely as possible):
deploy artifactory HA with persistence enabled and using a custom google service account.

Anything else we need to know:

agunnerson-elastic added a commit to agunnerson-elastic/jfrog-helm-charts that referenced this issue May 3, 2024
Previously, only the volumeMount was created, but not the volume itself.

Fixes: jfrog#1873

Signed-off-by: Andrew Gunnerson <[email protected]>
agunnerson-elastic added a commit to agunnerson-elastic/jfrog-helm-charts that referenced this issue May 3, 2024
Previously, only the volumeMount was created, but not the volume itself.
This affected only member nodes, not primary nodes.

Fixes: jfrog#1873

Signed-off-by: Andrew Gunnerson <[email protected]>
agunnerson-elastic added a commit to agunnerson-elastic/jfrog-helm-charts that referenced this issue May 3, 2024
…omSecretName

Previously, only the volumeMount was created, but not the volume itself.
This affected only member nodes, not primary nodes.

Fixes: jfrog#1873

Signed-off-by: Andrew Gunnerson <[email protected]>
agunnerson-elastic added a commit to agunnerson-elastic/jfrog-helm-charts that referenced this issue May 3, 2024
…viceAccount.customSecretName

Previously, only the volumeMount was created, but not the volume itself.
This affected only member nodes, not primary nodes.

Fixes: jfrog#1873

Signed-off-by: Andrew Gunnerson <[email protected]>
@oumkale
Copy link
Member

oumkale commented May 10, 2024

Hi @abhisheksama ,

Thank you for your issue, we have already taken this internally and it will be released in upcoming release 7.84.x

Will keep you updated

@oumkale oumkale self-assigned this May 10, 2024
@oumkale
Copy link
Member

oumkale commented May 14, 2024

This has been fixed in Artifactory version: 7.84.10, closing this issue.

@oumkale oumkale closed this as completed May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants