You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
should display logs of tasks that are defined with "retries: N".
Actual Behavior
The output is completely ignored, yet you can get it via kubectl logs -f PODNAME associated with the step
As soon as I removed the attribute 'retries' - I see log output normally
Steps to Reproduce the Problem
➜ which tknlo
tknlo='tkn -n ci pipelinerun logs -f'
/usr/bin/tkn
NO RETRIES is set for the task in the pipeline
tknlo output
[build-kaniko : build] Successfully installed Flask-2.0.2 Jinja2-3.0.2 MarkupSafe-2.0.1 Werkzeug-2.0.2 click-8.0.3 itsdangerous-2.0.1
[build-kaniko : build] WARNING: You are using pip version 21.0.1; however, version 23.3.2 is available.
[build-kaniko : build] You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
[build-kaniko : build] INFO[0024] Taking snapshot of full filesystem...
[build-kaniko : build] INFO[0026] COPY ..
[build-kaniko : build] INFO[0026] Taking snapshot of files...
[build-kaniko : build] INFO[0026] CMD [ "python3", "app.py"]
[build-kaniko : build] INFO[0026] Pushing image to 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend:latest13
[build-kaniko : build] INFO[0027] Pushed 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend@sha256:f779d655b5a090451e922a10e5c29f161c3df55d41263b32bab4592d93a14ddc
[build-kaniko : build] INFO[0028] Pushing image to 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend:kba13e
[build-kaniko : build] INFO[0028] Pushed 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend@sha256:f779d655b5a090451e922a10e5c29f161c3df55d41263b32bab4592d93a14ddc
[build-kaniko : results] 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend:kba13e
[gitops : clone-kubernetes-repo] Cloning into '/workspace/source/gitops/kubernetes-repo'...
[gitops : clone-kubernetes-repo] branch 'feature/add-prod'set up to track 'origin/feature/add-prod'.
[gitops : clone-kubernetes-repo] Switched to a new branch 'feature/add-prod'
[gitops : clone-kubernetes-repo] HEAD is now at dbd94df gitops: new image sha256:2c9ea6f403f41886fa04e18d1f823eff2a1eb84065e7e7378902b01f512344a5 compiled by tekton in prod env
[gitops : update-image]
[gitops : update-image] ===> PATCH APPS/PROD/VALUES.YAML FILE WITH IMAGE_DIGEST
[gitops : update-image]
[gitops : update-image] patching file apps/prod/values.yaml
[gitops : update-image]
[gitops : update-image] ===> GITOPS DIFF
[gitops : update-image]
[gitops : update-image] diff --git a/apps/prod/values.yaml b/apps/prod/values.yaml
[gitops : update-image] index d8f1fe1..a7b5fe4 100644
[gitops : update-image] --- a/apps/prod/values.yaml
[gitops : update-image] +++ b/apps/prod/values.yaml
[gitops : update-image] @@ -22,7 +22,7 @@ apps:
[gitops : update-image] deployment:
[gitops : update-image] image:
[gitops : update-image] repository: 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend
[gitops : update-image] - digest: sha256:2c9ea6f403f41886fa04e18d1f823eff2a1eb84065e7e7378902b01f512344a5
[gitops : update-image] + digest: sha256:f779d655b5a090451e922a10e5c29f161c3df55d41263b32bab4592d93a14ddc
[gitops : update-image] command:
[gitops : update-image] - bash
[gitops : update-image] - -c
[gitops : update-image]
[gitops : update-image] ===> GITOPS PUSH TO HTTPS://GITHUB.COM/SARITASA-NEST/USUMMIT-KUBERNETES-AWS
[gitops : update-image]
[gitops : update-image] [feature/add-prod 9e6e40f] gitops: new image sha256:f779d655b5a090451e922a10e5c29f161c3df55d41263b32bab4592d93a14ddc compiled by tekton in prod env
[gitops : update-image] 1 file changed, 1 insertion(+), 1 deletion(-)
[gitops : update-image] To https://github.com/org/111-kubernetes-aws
[gitops : update-image] dbd94df..9e6e40f feature/add-prod -> feature/add-prod
[deploy : execute]
[deploy : execute] ===> LOGIN TO ARGOCD
[deploy : execute]
[deploy : execute] 'admin:login' logged in successfully
[deploy : execute] Context 'argocd-server.argo-cd.svc' updated
[deploy : execute]
[deploy : execute] ===> GET ARGOCD VERSION
[deploy : execute]
So you can see that after build-kaniko we immediately see the deploy task output, and the gitops task is completely ignorer, however it has finished successfully and no restart were necessary.
build-kaniko : build] Collecting Jinja2==3.0.2
[build-kaniko : build] Downloading Jinja2-3.0.2-py3-none-any.whl (133 kB)
[build-kaniko : build] Collecting MarkupSafe==2.0.1
[build-kaniko : build] Downloading MarkupSafe-2.0.1-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (30 kB)
[build-kaniko : build] Collecting Werkzeug==2.0.2
[build-kaniko : build] Downloading Werkzeug-2.0.2-py3-none-any.whl (288 kB)
[build-kaniko : build] Installing collected packages: MarkupSafe, Werkzeug, Jinja2, itsdangerous, click, Flask
[build-kaniko : build] Successfully installed Flask-2.0.2 Jinja2-3.0.2 MarkupSafe-2.0.1 Werkzeug-2.0.2 click-8.0.3 itsdangerous-2.0.1
[build-kaniko : build] WARNING: You are using pip version 21.0.1; however, version 23.3.2 is available.
[build-kaniko : build] You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
[build-kaniko : build] INFO[0025] Taking snapshot of full filesystem...
[build-kaniko : build] INFO[0027] COPY ..
[build-kaniko : build] INFO[0027] Taking snapshot of files...
[build-kaniko : build] INFO[0027] CMD [ "python3", "app.py"]
[build-kaniko : build] INFO[0027] Pushing image to 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend:latest14
[build-kaniko : build] INFO[0029] Pushed 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend@sha256:f5ea1f17347f0d3867f3c6684b0033daab029936b94436eed18eec8ff90d8f11
[build-kaniko : build] INFO[0029] Pushing image to 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend:kba14e
[build-kaniko : build] INFO[0029] Pushed 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend@sha256:f5ea1f17347f0d3867f3c6684b0033daab029936b94436eed18eec8ff90d8f11
[build-kaniko : results] 111.dkr.ecr.us-east-1.amazonaws.com/111/prod/backend:kba14e
[deploy : execute]
[deploy : execute] ===> LOGIN TO ARGOCD
[deploy : execute]
[deploy : execute] 'admin:login' logged in successfully
[deploy : execute] Context 'argocd-server.argo-cd.svc' updated
[deploy : execute]
[deploy : execute] ===> GET ARGOCD VERSION
This will fix the logs command not showing logs
if there are retries and task has completed in first go
Failure and Completion of taskrun should not
depend on no. of retries. Also retries will
not scheduled be if task is done so add a check
for that.
Add e2e test for this scenarioi
Fixtektoncd#2208
This will fix the logs command not showing logs
if there are retries and task has completed in first go
Failure and Completion of taskrun should not
depend on no. of retries. Also retries will
not scheduled be if task is done so add a check
for that.
Add e2e test for this scenarioi
Fixtektoncd#2208
This will fix the logs command not showing logs
if there are retries and task has completed in first go
Failure and Completion of taskrun should not
depend on no. of retries. Also retries will
not scheduled be if task is done so add a check
for that.
Add e2e test for this scenarioi
Fix#2208
This will fix the logs command not showing logs
if there are retries and task has completed in first go
Failure and Completion of taskrun should not
depend on no. of retries. Also retries will
not scheduled be if task is done so add a check
for that.
Add e2e test for this scenarioi
Fix#2208
Versions and Operating System
Expected Behavior
should display logs of tasks that are defined with "retries: N".
Actual Behavior
The output is completely ignored, yet you can get it via
kubectl logs -f PODNAME
associated with the stepAs soon as I removed the attribute 'retries' - I see log output normally
Steps to Reproduce the Problem
➜ which tknlo tknlo='tkn -n ci pipelinerun logs -f' /usr/bin/tkn
NO RETRIES is set for the task in the pipeline
tknlo output
history of pods
RETRIES is set for the task in the pipeline
when added retries to pipeline task:
tknlo output
tkn logs do not output the task output.
So you can see that after
build-kaniko
we immediately see thedeploy
task output, and thegitops
task is completely ignorer, however it has finished successfully and no restart were necessary.history of pods
Additional Info
The text was updated successfully, but these errors were encountered: