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

ssvm: unable to find valid certification path to requested target #9962

Open
PPisz opened this issue Nov 21, 2024 · 6 comments
Open

ssvm: unable to find valid certification path to requested target #9962

PPisz opened this issue Nov 21, 2024 · 6 comments

Comments

@PPisz
Copy link

PPisz commented Nov 21, 2024

ISSUE TYPE
  • Bug Report
COMPONENT NAME
secondary storage vm
CLOUDSTACK VERSION
4.19.3
CONFIGURATION
OS / ENVIRONMENT
SUMMARY

Can't download and register a template/iso from a site secured with a letsencrypt certificate, for example: https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.8.3/metal-amd64.iso
Even after manually importing all letsencryt certificates it doesn't work correctly.

STEPS TO REPRODUCE
Create fresh ssvm 4.19.3 and import iso
EXPECTED RESULTS
We can download template/iso from letsencrypt certificate sites
ACTUAL RESULTS
2024-11-21 15:08:55,587 INFO  [storage.template.HttpTemplateDownloader] (agentRequest-Handler-3:null) No credentials configured for host=factory.talos.dev:443
2024-11-21 15:08:56,461 INFO  [storage.template.DownloadManagerImpl] (pool-1-thread-2:null) Download Completion for jobId: a4d992d1-0ae8-4a66-bbcd-2b5973506bd8, status=UNRECOVERABLE_ERROR
2024-11-21 15:08:56,484 INFO  [storage.template.DownloadManagerImpl] (pool-1-thread-4:null) local: /mnt/SecStorage/9bf7d36f-f049-3f71-89a8-101bacf6be00/template/tmpl/36/263/dnld2856126097776773813tmp_, bytes=(0 bytes) 0, error=PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, pct=0
@DaanHoogland
Copy link
Contributor

@PPisz , I think you mean version 4.19.1.3, right? (instead of 4.19.3)

@DaanHoogland
Copy link
Contributor

@PPisz , can you confirm this worked before, in 4.19.1.2 or earlier?

@PPisz
Copy link
Author

PPisz commented Nov 25, 2024

Unfortunately I don't know how it looked like on earlier versions, it certainly didn't work on 4.19.1.2

@PPisz
Copy link
Author

PPisz commented Nov 25, 2024

@PPisz , I think you mean version 4.19.1.3, right? (instead of 4.19.3)

Yes, 4.19.1.3

@DaanHoogland
Copy link
Contributor

I can confirm this is an issue in latest 4.18 as well

@weizhouapache
Copy link
Member

I can also reproduce the issue with 4.19.1 and 4.20.0.0

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

No branches or pull requests

3 participants