-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fedora environment variable VERSION=0 causes Rails db migration reverting #530
Comments
Thanks for the report, please could you share what are the versions of your Rails and ActiveRecord gems you use in the application? |
Ok, I did some testing with Rails 6.1.7.7. For a workaround it looks to be necessary to specify the variable VERSION as empty in command like so: Alternative workaround for when executed via shell (e.g. bash), unset the version like so: |
We plan to incorporate a fix to ruby 3.3 Fedora image. |
Settings variable to 'VERSION=' or 'VERSION=""' cause a problems in our testing suite. See here: https://github.com/sclorg/container-common-scripts/blob/master/tag.sh#L35 it raises an exception like:
We need to change this row https://github.com/sclorg/container-common-scripts/blob/master/tag.sh#L35 |
Would renaming the VERSION variable in the Fedora containerfile be possible/reasonable? Something like "RUBY_IMAGE_VERSION="? From the scripts, it doesn't look like we expect usage outside of the container labels, but I havent investigated the usage in detail. |
I think the variables should be either prefixed, or locally scoped. |
Container platform
OCP 4
Version
Fedora
OS version of the container image
Fedora
Bugzilla, Jira
No response
Description
In Rails, it support this ENV when running migrations: bin/rails db:migrate VERSION=20080906120000
In Fedora images, it has VERSION=0 in the dockerfile which makes the target version 0 and reverting all the db migrations
Reproducer
No response
The text was updated successfully, but these errors were encountered: