https://flyte.org logo
Join Slack
Powered by
I am trying to setup flyte v2 oss in our on prem e...
# flyte-v2-support
c
I am trying to setup flyte v2 oss in our on prem environment. I'm running into an issue where it seems the S3 metadata bucket is not passed along or used? The docs indicate specifying a storage 
metadataContainer
Copy code
storage:
    metadataContainer: <flyte-bucket>
But it doesn't seem like this config is used anywhere in the codebase. When the pod eventually does run it gets a 404 trying publish the error that occurred, presumably after failing to get inputs.
Copy code
Error performing PUT https://<redacted>/flyte-data/67/flytesnacks/development/rgd67nffkq956ml4pzwr/a0/1/error.pb in 1.015023907s - Server returned non-2xx status code: 404 Not Found
Just wanted to ask before digging into the code and figuring out where task metadata is actually stored and how to wire things up
g
w
Do we need to update docs @glamorous-carpet-83516 ?
g
yes, Jason is going to open a PR
☝️ 1
c
I'm on v2.0.30. When I dropped the 
metadataContainer
config I started getting errors about 
my-organization-flyte-container
which is the default helm chart value for the 
metadataContainer
which is so strange because I cannot find any other reference to the 
metadataContainer
.
Anyhow, when I configure the prefix in both places I'm still getting this in the task container logs
Copy code
[flyte] WARNING Flyte runtime started for action a0 with run name rvd59vpnkdddkmzgdwtl
[flyte] ERROR Failed to load task before execution: Object at location uploads/flytesnacks/development/HJYLNKKIIWJY7ZQDUW6GB6442Y======/fast5bc56306562ff35a4d45ceebbc9b72fd.tar.gz not found: Error performing HEAD https://<redacted>-flyte-metadata-dev-non-prod/uploads/flytesnacks/development/HJYLNKKIIWJY7ZQDUW6GB6442Y%3D%3D%3D%3D%3D%3D/fast5bc56306562ff35a4d45ceebbc9b72fd.tar.gz in 158.352143ms - Server returned non-2xx status code: 404 Not Found:
Copy code
Args:
      a0
      --inputs
      s3://<redacted>-flyte-metadata-dev-non-prod/uploads/dev/flytesnacks/development/offloaded-inputs/S5Bc0AJwRnQ/inputs.pb
...
      --tgz
      s3://<redacted>-flyte-metadata-dev-non-prod/uploads/flytesnacks/development/HJYLNKKIIWJY7ZQDUW6GB6442Y======/fast5bc56306562ff35a4d45ceebbc9b72fd.tar.gz
I will validate permissions..
Got it all squared away. I will double check whether the 
metadataContainer
is necessary
Can confirm that 
metadataContainer
is still required. I will investigate more as to why..
g
ah, it’s used in the helm chart. github.com/flyteorg/flyte/blob/…/configmap.yaml#… I was trying to search it in golang
c
I see now, I think the GitHub search wasn't showing the full results. It gets set as 
container
which is used for the 
initContainer
so its still required
Open in Slack
PreviousNext
Powered by