Good morning, we upgraded our Metaflow containers ...
# ask-metaflow
l
Good morning, we upgraded our Metaflow containers a while back to 2.4.3. Below is the snippet from our Terraform config confirming the versions. We are seeing some strange behavior on our UI of Metaflow where we get timeouts and 500's only on our prod environment. We are looking at database as a possible issue with it. Do we have the right UI to match the backend versions? Is there a place where we can see the list of available version of the UI?
Copy code
metadata_service_container_image = "netflixoss/metaflow_metadata_service:v2.4.3"
  ui_static_container_image        = "public.ecr.aws/outerbounds/metaflow_ui:v1.1.2"
a
Usually there isn't a strict requirement to use service version X with UI version Y. This said, your UI version is somewhat old, I'd try
1.3.6
(though upgrading UI image is unlikely to fix any 500s from backend)
you can look here for latest builds in our ECR repo https://gallery.ecr.aws/outerbounds/metaflow_ui (they do somewhat lag behind OSS releases)
h
Hi @average-beach-28850, I looked at the ECR gallery and it seems it doesn't follow a particular tagging convention. How do you suggest we track the available upgrades from an automation perspective? I am used to Renovate using github releases to pull the container with the same tag, but in this case it doesn't seem there is a 1:1 relationship. To clarify, if I see a github release
v1.3.10
I would expect being able to pull a container with that same image tag
v1.3.10
but the gallery doesn't show one. Is it possible for you guys to add this automated build/tag feature to reflect your github releases?
a
The tag is the same as GH release (we actually even both tag it as
1.3.3
and
v1.3.3
for backwards compatibility). The problem is that this is actually not fully automated and I kick off those builds in our CICD manually, so they're not 100% in sync
h
I hear you and can appreciate that it's not easy to manage without automation! I see that v1.3.10 is now available 🙂 Is there a way for you to try and have an image published to ECR via a github action when a new GH release is published?
👍 1
Update: Renovate found
public.ecr.aws/outerbounds/metaflow_ui:v2.2.4
to be a newer version than
v1.3.10
but I believe this version was one of the initial ones and must have been tagged in relation with the metaflow image version back then. Can you please delete that one so it doesn't confuse it?
a
let me see.. and to your point we do need to automate it its just there are some admin barriers (the repo is under netflix technically)
h
I hear you, thanks for your help!
hi @average-beach-28850, sorry for the direct ping again but I was wondering if you could please delete
v2.2.4
from ECR, or at least retag to a version that doesn't clash with the new versioning scheme? TIA!
a
sure! done
h
awesome, you rock, thank you!!
👍 1