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

ls: cannot access '/layers/paketo-buildpacks_bellsoft-liberica/jre/bin/keytool': No such file or directory #2388

Closed
harim-k opened this issue Jun 26, 2023 · 3 comments · Fixed by #3093
Labels
accepted Accepted the issue

Comments

@harim-k
Copy link

harim-k commented Jun 26, 2023

SECURITY NOTICE: If you have found a security problem in the UAA, please do not file a public github issue. Instead, please send an email to [email protected]

Thanks for taking the time to file an issue. You'll minimize back and forth and help us help you more effectively by answering all of the following questions as specifically and completely as you can.

What version of UAA are you running?

76.14.0

What output do you see from curl <YOUR_UAA>/info -H'Accept: application/json'?

How are you deploying the UAA?

I am deploying the UAA

  • other (please explain)

kubernetes
$ ytt -f templates -f overlays/values.yml -f | kubectl apply -f -

What did you do?

build-uaa-truststore container do not init with error
ls: cannot access '/layers/paketo-buildpacks_bellsoft-liberica/jre/bin/keytool': No such file or directory

If possible, provide a recipe for reproducing the error. Exact curl or uaac commands with verbose output are helpful. If your problem is configuration-related, please include portions of your uaa.yml or bosh deployment manifest that you believe may be relevant (but do not divulge secrets!)

What did you expect to see? What goal are you trying to achieve with the UAA?

What did you see instead?

Please include UAA logs if available.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/185477531

The labels on this github issue will be updated when the story is started.

@strehle
Copy link
Member

strehle commented Jul 4, 2023

The K8s deployment is no longer supported, however if you have a PR we can check this, but I cannot really check your issue since we use bosh or docker based deployments only

@strehle
Copy link
Member

strehle commented Jul 27, 2023

we cannot support k8s anymore

@strehle strehle closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2023
@cf-gitbot cf-gitbot added delivered accepted Accepted the issue and removed delivered labels Oct 9, 2023
achrinza added a commit to achrinza/uaa that referenced this issue Oct 23, 2024
Updates the `JAVA_HOME` env var for the `build-uaa-truststore` init contianer to match the updated path used by the Paketo buildpack.

fixes: cloudfoundry#2388
Signed-off-by: Rifa Achrinza <[email protected]>
strehle pushed a commit that referenced this issue Nov 4, 2024
Updates the `JAVA_HOME` env var for the `build-uaa-truststore` init contianer to match the updated path used by the Paketo buildpack.

fixes: #2388
Signed-off-by: Rifa Achrinza <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Accepted the issue
Projects
Development

Successfully merging a pull request may close this issue.

3 participants