I feel like I m missing something really stupid with the run flyte-org #ask-the-community

Title

# ask-the-community

Dan Corbiani

02/17/2023, 10:37 PM

I feel like I'm missing something really stupid with the run command. I posted an image of the config. It is going to the right URL. The job gets spawned and will start to run, but the URL in the

pyflyte run

response is wrong. Could this be a bug?

Yee

02/17/2023, 10:46 PM

actually in the latest versions we’ve moved all the sandbox web ports to 30080.

Dan Corbiani

02/17/2023, 10:46 PM

We're note using the sandbox.

Yee

02/17/2023, 10:46 PM

oic

Dan Corbiani

02/17/2023, 10:46 PM

We're trying to test a more production deployment. @justin hallquist

Yee

02/17/2023, 10:46 PM

that you’ve port-forwarded?

Dan Corbiani

02/17/2023, 10:47 PM

essentially.

we stand up the services in a local kubernetes cluster using k3s

and I can get to the UI

And the job posts and starts. It just looks like the url in the print is off,

Yee

02/17/2023, 10:49 PM

perhaps the config is not getting used…

justin hallquist

02/17/2023, 10:49 PM

sorry for clarity we're not port-forwarding as we're using the nodeport 30081 from the admin -- my understanding is the config above should also print 30081 in the output as it's being told that's where the console is?

Yee

02/17/2023, 10:50 PM

https://github.com/flyteorg/flytekit/blob/99d3d5048c207d32f469dde8797bcbb4408d6617/flytekit/remote/remote.py#L1710

it very explicitly looks at that value.

can you re-try with

pyflyte -c <config file> ...

Dan Corbiani

02/17/2023, 10:54 PM

same

image.png

Yee

02/17/2023, 10:56 PM

which flytekit version?

justin hallquist

02/17/2023, 11:02 PM

1.1.1

Yee

02/17/2023, 11:07 PM

could you bump to 1.3.1?

justin hallquist

02/17/2023, 11:07 PM

ya one sec

sorry for the wait -- mini dependency hell bumping there (flytekit -> flyteidl -> grpcio -> google stuffs etc) that bump fixed it

thanks! 😄

Yee

02/17/2023, 11:23 PM

yup sure

Dan Corbiani

02/17/2023, 11:24 PM

🦜

Yee

02/17/2023, 11:25 PM

yeah the recent protobuf break is pretty annoying.

going forward we are planning on maintaining both 1.2.x and 1.3+ with the former being protobuf 3 and latter versions protobuf 4

sorry forgot to mention that.

may have been easier to just go to 1.2.x 😬

justin hallquist

02/17/2023, 11:27 PM

np -- ended up working so no foul there 😄