-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Missing configuration and misconfigured port #3236
Comments
@mficek , can you double check which version of flytekit you're running? We recently fixed this in flyteorg/flytekit#1384 (which went out in flytekit 1.3.0). |
@eapolinario It's 1.3.0
|
Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏 |
Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏 |
Describe the bug
When submitting a new workflow to a demo cluster with
pyflyte run --remote core/flyte_basics/hello_world.py my_wf
, it does not work because no configuration is provided. After callingflytectl config init
, the config file~/.flyte/config.yaml
is created, but the endpoint port there is not 30080 as in the demo cluster, but 30081. I had to manually change (rewrite) the config file to haveendpoint: dns:///localhost:30080
. Then, everything works well.Expected behavior
Following userguide_setup, I'd expect that following all steps from top to bottom would lead to successful
--remote
execution, which didn't happen.Additional context to reproduce
git clone https://github.com/flyteorg/flytesnacks
cd flytesnacks/cookbook
pip install -r core/requirements.txt
flytectl demo start
pyflyte run --remote core/flyte_basics/hello_world.py my_wf
<-- this failsflytectl config init
~/.flyte/config.yaml
and change edpoint port from 30081 to 30080pyflyte run --remote core/flyte_basics/hello_world.py my_wf
<-- now it worksSteps 8 and 9 are missing in the documentation.
Screenshots
Result of step 8 in Additional context to reproduce:
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: