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
Please fill out the issue checklist below and provide ALL the requested information.
I reviewed open and closed Github issues that may be related to my problem.
I am reporting a bug that others will be able to reproduce.
Describe the bug
tail does not work when creating a workload with Dockerfile builds even if the workload is valid and becomes ready
Expected behavior
Show logs like with any other workload source
Steps to Reproduce
tanzu apps workload apply tanzu-java-web-app-dockerfile9 \
--namespace dev \
--git-branch main --git-commit "1ca82aea6b43f93f4109f24dee5d71c4fe7f5055" \
--git-repo https://github.com/garethjevans/tanzu-java-web-app-dockerfile \
--label apps.tanzu.vmware.com/has-tests=true \
--label app.kubernetes.io/part-of=test-workload \
--type web \
--param dockerfile=./Dockerfile \
--yes --tail
Error waiting forready condition: Failed to become ready: unable to retrieve outputs for resource [image-provider]in supply chain [source-to-url]: failed to find any healthy object in the set of immutable stamped objects
Screenshots
If applicable, add screenshots to help explain your problem.
Version (Apps plugin version, Version of K8s running on cluster)
Put the output of the following commad
tanzu version && tanzu apps version
version: v0.90.0-beta.0
buildDate: 2023-05-31
sha: 1fc71327
v0.12.0-build.4
Environment where the bug was observed (cloud, OS, etc)
Please fill out the issue checklist below and provide ALL the requested information.
Describe the bug
tail
does not work when creating a workload with Dockerfile builds even if the workload is valid and becomes readyExpected behavior
Show logs like with any other workload source
Steps to Reproduce
Screenshots
If applicable, add screenshots to help explain your problem.
Version (Apps plugin version, Version of K8s running on cluster)
Put the output of the following commad
tanzu version && tanzu apps version version: v0.90.0-beta.0 buildDate: 2023-05-31 sha: 1fc71327 v0.12.0-build.4
Environment where the bug was observed (cloud, OS, etc)
MacOS Ventura 13.4
Additional context & Relevant Debug Output (Logs, etc)
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: