cli
cli copied to clipboard
Added -- showlog, but no log printing
Versions and Operating System
-
Kubernetes version:
Output of
kubectl version:Client Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.4-dirty", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"dirty", BuildDate:"2021-03-15T10:03:32Z", GoVersion:"go1.16.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:12:29Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}
- Tekton Pipeline version:
**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**
Client version: 0.25.0 Pipeline version: v0.37.2 Triggers version: v0.20.2 Dashboard version: v0.28.0
- Operating System:
ubuntu 20.4,mac os(10.15.7)
# Expected Behavior
# Actual Behavior
# Steps to Reproduce the Problem
1.The local console can print logs to check the execution of the pipeline(tkn pipeline start ...... --showlog)
2.After many times of execution(tkn pipeline start ...... --showlog), the local console suddenly has no logs
3.Change to a different system and execute. At first, there was a log, but it stopped printing after a while
# Additional Info
The console can print logs after adding -- showlog in the earlier stage. However, after a period of time, the console suddenly stops printing logs, but the pod corresponding to pipelinerun still has logs.
tkn pipeline start --filename builds/tekton/build/unittest_main.yaml --param [email protected]:re/rx.git --param gitrevision=add_tekton_0908 --param cov-flag=false --param module=all -w name=shared-data,volumeClaimTemplateFile=builds/tekton/build/workspace-template.yaml -w name=gitlab-release-credentials,secret=gitlab-release-credentials --pod-template builds/tekton/build/pod-template.yaml -k /home/jenkins/workspace/workspace/re_dept/debug/whh_debug/test_config/config --pipeline-timeout 15m -n tekton-pipelines --showlog
The logs can be viewed through tkn pipeline logs xxx, but after adding -- showlog to the local console, after a certain number of executions
I'm using tutorial from here: https://redhat-scholars.github.io/tekton-tutorial/tekton-tutorial/tasks.html using:
minikube version: v1.28.0
kubectl and kubernetes: v1.23.3
tkn version
Client version: 0.27.0
Pipeline version: v0.24.3
Dashboard version: v0.30.0
running:
tkn clustertask start echoer --showlog
TaskRun started: echoer-run-nmqr9
Waiting for logs to be available...
task echoer create has not started yet or pod for task not yet available
No output at all.
But logs do exist:
kubectl logs echoer-run-nmqr9-pod-5fstw --all-containers
Meeow!! from Tekton 😺🚀
2022/11/16 13:19:06 Copied /ko-app/entrypoint to /tekton/tools/entrypoint
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.