-
Notifications
You must be signed in to change notification settings - Fork 445
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
Artifactory: Credential Bootstrap failure due to Invalid Character #1766
Comments
Thx @Souheil-Yazji for reporting this. |
Confirmed as a bug. A fix will be released with next Artifactory minor version release. |
@eldada is there any progress on this? removing admin block helped |
I see the current release 7.59.11 is still missing this fix. I'll follow up internally and update |
The version with the fix is planned to be release mid July. Probably version 7.63.x |
Is this a request for help?: No
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report
Version of Helm and Kubernetes:
Helm: 3.7.1
K8s: 1.24.x
Which chart:
Artifactory installed via Jfrog Platform
Which product license (Enterprise/Pro/oss):
Enterprise (present in all mostlikely)
JFrog support reference (if already raised with support team): - no support issue raised.
What happened:
When bootstraping credentials to the helm chart for the default admin account creds, including certain characters, for example an "=" sign causes the pod to fail after start-up, forcing crashloop backoff. After digging through the pod's log, the following is found:
This is probably caused by the format of the bootstrap.creds file cred string being
<user>@<ip>=<pass>
. Having an "=" in this case most likely causes a parsing error.This also causes other issues to appear such as
Cluster join: Join key is missing. Pending for 5 seconds with 60 seconds timeout
What you expected to happen:
At least one of the following:
These would be for the artifactory dev team:
4. No termination of the app, some other fail safe for crash avoidance.
5. A graceful termination of the app
How to reproduce it (as minimally and precisely as possible):
Simply create a helm release with all defaults but add to the chart values
If using the jfrog-platform chart:
Anything else we need to know:
The text was updated successfully, but these errors were encountered: