New RunLLM response generated: >>>*# Question* He...
# runllm-flyte-trial
j
New RunLLM response generated: >>>*# Question* Hello Community! While trying out the “Getting started with workflow development” part of the tutorial, I have encountered an issue that when running
pyflyte run
immediately after creating a new project through
flytectl create project
, the web console shows failed to create workflow in propeller namespace “projectName-domain” not found. I believe this is a similiar issue to issue. It seems that it takes time to create kubernetes namespace after running
flytectl create project
. If running
pyflyte run
too soon, the namespace may not be created in time. Is this an expected behavior of flytectl or should it be considered a bug? Thanks for the reply in advance! You can reproduce this issue by the script below: (change the project name accordingly to, it must be a new project)
Copy code
flytectl create project \
      --id "new-project" \
      --labels "my-label=new-project" \
      --description "My Flyte project" \
      --name "My project"

pyflyte run --remote -p new-project -d development example.py wf --name Ada
# Answer Yes, this is a known issue where there is a delay in the creation of Kubernetes namespaces after running
flytectl create project
. If you run
pyflyte run
too soon, the namespace may not be created in time, leading to the error "failed to create workflow in propeller namespace 'projectName-domain' not found". According to this discussion, the namespace creation process can take a few minutes. This delay can cause issues when deploying workflows immediately after creating a new project. Would you like more details on how to handle this delay or any other related information? Sources: - GitHub Issue #5376 Slack Link https://.slack.com/archives/CP2HDHKE1/p1727461422.900729 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.