https://rancher.com/ logo
#harvester
Title
# harvester
n

narrow-artist-37495

04/06/2023, 9:14 PM
Hi folks, I just installed Harvester bare metal on one of my homelab machines for evaluation and I'm really excited at the possibilities! It is a clean install and I'm having an issue pulling images from a URL. Since it is a clean install at the latest version, I'm not sure if it is an issue with my configuration or a bug. Wanted to do a sanity check here before filing a bug. When I go to download an image, I get the error
Head "<https://github.com/rancher/k3os/releases/download/v0.20.6-k3s1r0/k3os-amd64.iso>": x509: certificate is not valid for any names, but wanted to match <http://github.com|github.com>
This happens for different domains and images as well. If I try with just the http protocol, I get
Got 404 status code from <http://github.com/rancher/k3os/releases/download/v0.20.6-k3s1r0/k3os-amd64.iso>
. No VMs are running. I have the default management network and a VM network (both are reporting as active). It is connected to my home LAN with nothing fancy like proxies going on. In advanced settings, I don't have anything set for
additional-ca
,
http-proxy
,
ssl-certificates
,
ssl-parameters
, or
vip-pools
. I'm not really sure how to debug this further. Is this a bug that I should file or is there an issue with my configuration?
🙌 1
Well I just realized I was running v1.1.2-rc5 instead of the stable v1.1.1. Whoops. Just reinstalled with the stable version and it works.
If this isn't a known issue with v1.1.2-rc5, I saved the support bundle before nuking the instance and I'm happy to file a bug.
👀 1
r

red-king-19196

04/10/2023, 8:27 AM
Sure! We can look at the support bundle to see what happened. Feel free to attach it here. Thank you.
n

narrow-artist-37495

04/13/2023, 8:52 AM
supportbundle_1b7cc225-3490-415f-9da6-2dd2652c47fa_2023-04-06T23-22-48Z.zip
👍 1
r

red-king-19196

04/17/2023, 7:05 AM
I’ve checked the support bundle file. It seems similar errors happen not only with your image, but there are also lots of certificate errors in the logs for harvester system components:
Copy code
logs/cattle-system/rancher-68799df576-6kgtk/rancher.log:2023-04-06T23:22:39.960195043Z 2023/04/06 23:22:39 [ERROR] error syncing 'rancher-stable': handler helm-clusterrepo-download: Get "<https://releases.rancher.com/server-charts/stable/index.yaml>": x509: certificate is not valid for any names, but wanted to match <http://releases.rancher.com|releases.rancher.com>, requeuing
logs/harvester-system/harvester-5b6b4994-qq5jf/apiserver.log:2023-04-06T21:05:28.733608477Z time="2023-04-06T21:05:28Z" level=error msg="failed syncing version metadata: Post \"<https://harvester-upgrade-responder.rancher.io/v1/checkupgrade>\": x509: certificate is not valid for any names, but wanted to match <http://harvester-upgrade-responder.rancher.io|harvester-upgrade-responder.rancher.io>"
logs/longhorn-system/longhorn-manager-qfv6g/longhorn-manager.log:2023-04-06T21:05:38.593416886Z time="2023-04-06T21:05:38Z" level=debug msg="Failed to check for the latest and stable Longhorn versions" controller=longhorn-setting error="Post \"<https://longhorn-upgrade-responder.rancher.io/v1/checkupgrade>\": x509: certificate is not valid for any names, but wanted to match <http://longhorn-upgrade-responder.rancher.io|longhorn-upgrade-responder.rancher.io>" node=boogle
However, I cannot reproduce it in my environment with v1.1.2-rc5. Could you let me know if you managed to reproduce this?
7 Views