krateo icon indicating copy to clipboard operation
krateo copied to clipboard

QuickStart Installer Go Panic

Open asbarbati opened this issue 9 months ago • 0 comments

Describe the bug If you attempted to install a fresh cluster, it resulted in a Go panic while waiting for the Vcluster to become ready.

To Reproduce Steps to reproduce the behavior:

  1. Run curl -L https://github.com/krateoplatformops/krateo/releases/latest/download/kind-vcluster.sh | sh
  2. Wait 120sec
  3. Checkout the installer log
  4. See error

Logs

2024/05/07 08:51:01 executing step with id: install-vcluster (chart)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: service.type, value: NodePort)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: service.nodePort, value: 30090)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: openshift.enable, value: false)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: securityContext.allowPrivilegeEscalation, value: false)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.manifests, value: apiVersion: v1
ki...)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.helm[0].chart.name, value: installer)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.helm[0].chart.repo, value: https://charts.kr...)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.helm[0].chart.namespace, value: krateo-system)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.helm[0].release.name, value: installer)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.helm[0].release.namespace, value: krateo-system)
2024/05/07 08:51:14 DBG [chart:install-vcluster]: set (name: init.helm[0].values, value: krateoplatformops...)
2024/05/07 08:51:27 DBG: creating 1 resource(s)
2024/05/07 08:51:27 DBG: creating 11 resource(s)
2024/05/07 08:51:28 DBG: beginning wait for 11 resources with timeout of 5m0s
2024/05/07 08:51:29 DBG: Deployment is not ready: krateo-system/vcluster-k8s. observedGeneration (0) does not match spec generation (1).
2024/05/07 08:51:30 DBG: Deployment is not ready: krateo-system/vcluster-k8s. 0 out of 1 expected pods are ready
...
2024/05/07 08:56:16 DBG: Deployment is not ready: krateo-system/vcluster-k8s. 0 out of 1 expected pods are ready
2024/05/07 08:56:18 DBG: Deployment is not ready: krateo-system/vcluster-k8s. 0 out of 1 expected pods are ready
[controller-runtime] log.SetLogger(...) was never called; logs will not be displayed.
Detected at:
	>  goroutine 652 [running]:
	>  runtime/debug.Stack()
	>  	/usr/local/go/src/runtime/debug/stack.go:24 +0x5e
	>  sigs.k8s.io/controller-runtime/pkg/log.eventuallyFulfillRoot()
	>  	/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/log/log.go:60 +0xcd
	>  sigs.k8s.io/controller-runtime/pkg/log.(*delegatingLogSink).Enabled(0xc0003c7800, 0x10?)
	>  	/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/log/deleg.go:111 +0x32
	>  github.com/go-logr/logr.Logger.Info({{0x2496820?, 0xc0003c7800?}, 0xc0007217a8?}, {0xc000e90450, 0x2b}, {0xc000d92120, 0x6, 0x6})
	>  	/go/pkg/mod/github.com/go-logr/[email protected]/logr.go:276 +0x72
	>  sigs.k8s.io/controller-runtime/pkg/internal/recorder.(*Provider).getBroadcaster.func1.1(0xc000246000)
	>  	/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/recorder/recorder.go:104 +0x1e7
	>  k8s.io/client-go/tools/record.(*eventBroadcasterImpl).StartEventWatcher.func1()
	>  	/go/pkg/mod/k8s.io/[email protected]/tools/record/event.go:401 +0x11d
	>  created by k8s.io/client-go/tools/record.(*eventBroadcasterImpl).StartEventWatcher in goroutine 79
	>  	/go/pkg/mod/k8s.io/[email protected]/tools/record/event.go:387 +0x109

VCluster Log:

2024-05-07 09:18:31	INFO	event.coredns-68bdd584b4-pc2sz.17cd2a455a961714	syncer/syncer.go:146	create virtual event kube-system/coredns-68bdd584b4-pc2sz.17cd2a455a961714	{"component": "vcluster"}
2024-05-07 09:21:15	ERROR	handler/handler.go:49	Error while proxying request: context canceled	{"component": "vcluster"}
2024-05-07 09:21:15	ERROR	filters/timeout.go:142	post-timeout activity - time-elapsed: 9.364108ms, GET "/readyz" result: <nil>	{"component": "vcluster"}
2024-05-07 09:21:16	INFO	pod.coredns-68bdd584b4-pc2sz	syncer/syncer.go:134	update virtual pod kube-system/coredns-68bdd584b4-pc2sz, because status has changed	{"component": "vcluster"}

Server (please complete the following information):

  • OS: Almalinux 9
  • Helm: v3.14.4
  • Kind: v0.22.0

asbarbati avatar May 07 '24 09:05 asbarbati