:raising_hand: I have found a pair of issues that ...
# flyte-support
b
šŸ™‹ I have found a pair of issues that I'm unsure about (whether either is a known bug or should be raised as a new issue on github): • My tasks were failing with this trace, which I narrowed down to being because my
PodTemplate
for this task had
/bin/bash -c
as the
command
(where
arguments
was the
pyflyte-fast-execute ...
etc)
Copy code
[...]
/usr/local/lib/python3.10/dist-packages/flytekit/bin/entrypoint.py:754 in    │
│ fast_execute_task_cmd                                                        │
│                                                                              │
│ ā± 754 │   p = subprocess.Popen(cmd, env=env)                                 │
│                                                                              │
│ /usr/lib/python3.10/subprocess.py:971 in __init__                            │
│                                                                              │
│ ā±  971 │   │   │   self._execute_child(args, executable, preexec_fn, close_f │
│                                                                              │
│ /usr/lib/python3.10/subprocess.py:1733 in _execute_child                     │
│                                                                              │
│ ā± 1733 │   │   │   │   executable = args[0]                                  │
╰──────────────────────────────────────────────────────────────────────────────╯
IndexError: list index out of range
• I was happy to find and correct the cause, but I was also confused because another domain for this same project was using the same
PodTemplate
and didn't have the `command`: I confirmed that the configured
PodTemplate
in my
cluster_resource_manager
config did not have this
command
either. I can't figure out when I added or removed this
command
but I'm assuming I removed it at some point: I'm guessing the cluster resource manager / syncresources can't detect removed keys from a PodTemplate? Is that a known limitation? ā—¦ I resolved this by doing a manual
kubectl edit podtemplate...
and removing the
command
entirely but curious whether its worth reporting this