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

Jfrog: resolve issue with license #1866

Closed
1 of 2 tasks
Souheil-Yazji opened this issue Oct 18, 2023 · 1 comment
Closed
1 of 2 tasks

Jfrog: resolve issue with license #1866

Souheil-Yazji opened this issue Oct 18, 2023 · 1 comment
Assignees

Comments

@Souheil-Yazji
Copy link
Contributor

Souheil-Yazji commented Oct 18, 2023

cc @zachomedia @Jose-Matsuda

Attempting to update the jfrog license yields an error:
In order to use this function, it is required to configure your Artifactoryinstance as HA.

No info online about neither this requirement or the error.

The currently in-use license does not appear in the license menu either, however jfrog seems to recognize that it is there:

Image

The subcomponents such as Xray are working fine, this would not be the case if the License was not available.

Looking for the License on Cluster

After checking the Artifactory pod, the artifactory.lic does exist and contains the previously provided license, however the folder structure does not match the docs. During the upgrade of the Jfrog-Platform, there was explicit documentation notes specifying that the PV/C(s) for Xray must be deleted before the upgrade. One possibility is that the upgrade of the Jfrog-Platform helm chart actually also requires the deletion of the PV/Cs for the Artifactory deployment as well.

Posssibilities

  • back-up the old artifactory.lic file, duplicate and update it's license value. Cross fingers and hope it works
  • Back up the PVC for rt, delete the old PVC and redeploy the helm chart. Cross fingers and toes, hope it works
@Souheil-Yazji
Copy link
Contributor Author

Souheil-Yazji commented Oct 23, 2023

Attempted possibility 1 but it seems that the license is persisted somewhere else (probably the database or something?) and it respawns the file with the original license.

Will have to attempt 2 in a new issue.

CNS to open a support ticket with jfrog, they've encountered the same bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant