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
I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
I have searched existing issues and could not find a match for this bug
I expected the same behavior as when initContainers are defined directly in Workflow YAML files: any containers relating to a particular node/step should be available to select from the dropdown menu as part of the Logs tab.
This is not the case when the initContainer is defined in a Workflow Template, in which case no initContainer options are shown in the dropdown menu.
This issue does not present when initContainers are defined directly as part of a Workflow, but does occur when initContainers are defined in a Workflow Template, instead.
Version(s)
v3.6.5, latest
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
worflow template:
apiVersion: argoproj.io/v1alpha1kind: WorkflowTemplatemetadata:
name: init-containerspec:
templates:
- name: test-init-wftcontainer:
name: alpineimage: "alpine:latest"command:
- sh
- -xcargs:
- | echo "Logs from main container, defined in the WF template YAML."initContainers:
- name: test-init-containerimage: "alpine:latest"command:
- sh
- -cargs:
- | echo "Logs from InitContainer, defined directly in WF template YAML."
UI when defining initContainers directly in Workflow:
UI when defining initContainers in Workflow Template:
The init containers are missing from the dropdown list in Logs tab. (but as a workaround, i can manually type a hidden container name into the box to retrieve the logs for that container)
Uh oh!
There was an error while loading. Please reload this page.
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
I expected the same behavior as when initContainers are defined directly in Workflow YAML files: any containers relating to a particular node/step should be available to select from the dropdown menu as part of the Logs tab.
This is not the case when the initContainer is defined in a Workflow Template, in which case no initContainer options are shown in the dropdown menu.
This issue does not present when initContainers are defined directly as part of a Workflow, but does occur when initContainers are defined in a Workflow Template, instead.
Version(s)
v3.6.5, latest
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
worflow template:
workflow (utilizes the template):
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: