Automatic V2 migration broke static files/css in django app

Hi, I went to deploy my fly app with fly deploy and got a message that said

This feature is highly experimental and may produce unexpected results. Proceed?

After continuing on, I realized my admin page was no longer loading any styles/css. Went to check our logs and found errors listed out below. Thankfully our front end is hosted on Vercel but it’s quite a trust-breaking endeavor to see our website no longer loading any CSS out of the blue after a deployment to fix a typo.

2023-05-24T17:29:06.306 app[3d8d349a231d89] lax [info] Not Found: /static/admin/css/nav_sidebar.css

2023-05-24T17:29:06.313 app[3d8d349a231d89] lax [info] Not Found: /static/admin/css/responsive.css

2023-05-24T17:29:06.315 app[3d8d349a231d89] lax [info] Not Found: /static/admin/css/dashboard.css

2023-05-24T17:29:06.389 app[3d8d349a231d89] lax [info] Not Found: /static/admin/js/theme.js

2023-05-24T17:29:06.392 app[568394df72538e] lax [info] Not Found: /static/admin/js/nav_sidebar.js

2023-05-24T17:29:26.845 app[3d8d349a231d89] lax [info] Not Found: /static/admin/css/base.css

2023-05-24T17:29:26.853 app[568394df72538e] lax [info] Not Found: /static/admin/css/responsive.css

2023-05-24T17:29:26.856 app[568394df72538e] lax [info] Not Found: /static/admin/css/nav_sidebar.css

2023-05-24T17:29:26.904 app[3d8d349a231d89] lax [info] Not Found: /static/admin/css/dark_mode.css

2023-05-24T17:29:26.976 app[3d8d349a231d89] lax [info] Not Found: /static/admin/js/theme.js

2023-05-24T17:29:26.978 app[568394df72538e] lax [info] Not Found: /static/admin/js/nav_sidebar.js

2023-05-24T17:29:29.077 app[5683921ad9058e] lax [info] Not Found: /static/admin/css/base.css

2023-05-24T17:29:29.079 app[5683921ad9058e] lax [info] Not Found: /static/admin/css/dark_mode.css

2023-05-24T17:29:29.080 app[568394df72538e] lax [info] Not Found: /static/admin/css/responsive.css

2023-05-24T17:29:29.083 app[568394df72538e] lax [info] Not Found: /static/admin/css/login.css

2023-05-24T17:29:29.084 app[5683921ad9058e] lax [info] Not Found: /static/admin/css/nav_sidebar.css

2023-05-24T17:29:29.170 app[3d8d349a231d89] lax [info] Not Found: /static/admin/js/theme.js

2023-05-24T17:29:29.172 app[3d8d349a231d89] lax [info] Not Found: /static/admin/js/nav_sidebar.js

EDIT: Also please note this deploy happened with a .toml that was based on our legacy v1 app. I did not migrate it beforehand. After reading through the forum, I’m now aware of the tool to migrate tomls to v2. Nevertheless, I would expect most users don’t check the form regularly and will likely deploy from a v1 toml so it could still be an issue.

What version of flyctl did you use to migrate? fly version should tell you. This is working properly in my tests, so I’d like to figure out where it went bad.

I just wanted to highlight this point ^^^ I proactively migrated my apps (other than a few “demo” apps) but at a minimum, feels like you could have emailed customers and warned them about this situation - specifically, that auto-migration was going to leave them with an outdated toml, which means that subsequent deploys could cause unexpected issues. Expecting users to check the forums seems like a bit much.

I understand that you’re eager to get everyone on v2 but a proactive warning with ample lead time would have avoided surprises like this one. I also realize that the emails that are sent post-auto migration suggests running fly config save but I think the wording could be more emphatic about the possible consequences of not doing so.

Feel free to correct me if you think I misunderstood anything about the process.

1 Like

I was on version 0.0.427 after checking fly status. I’ve since upgraded to 0.1.13