Closed mattwelke closed 5 months ago
Some more info. When I look at the logs of the kubevela-vela-core-<n>
pod, I see errors:
"msg"="Reconciler error" "error"="cannot update application status: the server could not find the requested resource (patch applications.core.oam.dev first-vela-app)" "Application"={"name":"first-vela-app","namespace":"prod"} "controller"="application" "controllerGroup"="core.oam.dev" "controllerKind"="Application" "name"="first-vela-app" "namespace"="prod" "reconcileID"="e8ede21d-9334-4ede-a415-5f7500b2b11a"
Was able to fix this by downgrading my vela
CLI to 1.9.6
(that was the version my colleague was using and things worked fine for them).
I was running 1.9.10
before.
May be related to https://github.com/kubevela/kubevela/issues/6493, a bug logged for 1.9.10.
Instead, I see this:
maxprocs.go:47: maxprocs: Leaving GOMAXPROCS=20: CPU quota undefined About: Name: first-vela-app Namespace: prod Created at: 2024-04-03 13:51:39 -0400 EDT Status:
Yes, that's the same output (no status output) I got before raising https://github.com/kubevela/kubevela/issues/6493
Go back to v1.9.9 and you will be fine, v1.9.10 wasn't a substantial update anyway.
For picking up kubevela, you will be fine with v1.9.9. Don't let this put you off, Kubevela is great! 🙂
Ah, please also note you've raised this on the "kubevela.github.io" repo, which is for the website.
The one for the software is "kubevela" - as with my ticket 🙂
Ah, please also note you've raised this on the "kubevela.github.io" repo, which is for the website.
Yes, it's clear now the issue isn't with the tutorial, but with the software itself.
Closing this since there's nothing to do with docs and the software bug has already been logged.
When following the tutorial at https://kubevela.io/docs/quick-start/, everything works for me until I get to the part where I should run
vela status first-vela-app
. The tutorial says that I should see output like the following:Instead, I see this:
(We can ignore "maxprocs.go:47: maxprocs: Leaving GOMAXPROCS=20: CPU quota undefined" for now. I get this error regardless of which
vela
command I run, and it doesn't seem to stop anything from working. Thevela
commands do begin to run.)My application doesn't seem to have a status yet.
The next steps in the tutorial are about port forwarding and then resuming the workflow.
When I run
vela port-forward first-vela-app 8000:8000
, I get the following output:I wonder if this issue (there being no pod associated with my application) is related to the fact that there is no status for my application yet.
Then, when I run
vela workflow resume first-vela-app
, which I understand to be the command I would run to get the workflow to resume (it appears designed to halt with a manual approval step), I get this output:So it appears that I can't resume my workflow yet because of some issue that KubeVela encounters early on after I deploy my app, and it probably is related to me not seeing a status at all for my app.
Some info that might be useful for troubleshooting:
(using
kind
)(KubeVela install appears to have succeeded)
(KubeVela pods appear to be running... I expect that at least one of these pods should react to my application by reconciling it)
(app appears to have been at least applied to the Kube API)