https://prefect.io
Join Slack
Missing Quick Run Button The Quick Run button is missing on our self-hosted server. Version 0.14.1. ...
# prefect-ui
j
Missing Quick Run Button The Quick Run button is missing on our self-hosted server. Version 0.14.1. Not able to kick off any new runs
z
Hi Jack — our team is looking into this. For now, you should be able to use the “Run” button still?
j
The javascript console is showing a couple of errors. Perhaps related?
I'm not familiar with using the standard Run button. It says "The flow has no parameters. Click Run to launch your flow" When I click Run, this popup error appears:
z
Can you share the versions of your UI / Server? It kind of looks like the database schema is behind.
j
I was told it is was this:
Copy code
root@b9fa9b14b2f1:/prefect-server# prefect version
  0.14.1+55.g8f6792ba3
We were running 0.13.19 a week ago. Then we started a second (staging) box running 0.14.1, pointed at the same database. (Yes, we had two servers pointed at the same database for a couple days.) Once we verified that the staging box worked, supposedly the docker container running the QA server was promoted to be our production box.
I don't suppose there's a way from the web UI to see exactly which version is running...?
When you say versionS, do you mean server version? (I thought server and UI were one and the same)
z
In the UI if you open the left side-bar there should be some dates for the version of the UI and API you are on
j
I don't see a left side bar...
z
Click “Default”
j
"Default" does not appear to be a link.
I can select the text, but nothing happens when clicked
a
in the top grey bar?
j
Found it...
Is there a key somewhere mapping those dates to prefect versions?
z
When we pin a prefect version we collect the most versions of the UI/API for 
prefect server start
— can you provide some more details on how you’re running your Prefect Server instance?
j
Just a sec, getting our server manager an invite to this slack workspace
j
Hello!
j
You made it!
j
Right, so we are running all the docker images started by 
prefect server start
on ECS, with a RDS database backend.
I recently upgraded the images to 
0.14.1+55.g8f6792ba3
, (as reported inside the Docker image)… if there's a better way to upgrade, something that includes a database migration, I'd love to hear about it.
✅ 1
z
Hi 😄 so with the helm chart the deployment includes a sidecar init container to run the database migration e.g. https://github.com/PrefectHQ/server/blob/master/helm/prefect-server/templates/graphql/deployment.yaml#L43
The key here is that when you bump your images you should probably be doing 
prefect-server database upgrade
as well
j
Ok, just saw that in the Github, I'll run through that and see how far behind we are.
This is a bit piecemeal at the moment, but I imagine once things are settled a bit more I'll work out a reliable synchronization to keep our infrastructure in line with your latest published images.
18 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by