Fedora environment variable VERSION=0 causes Rails db migration reverting

Open
#530 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
dockerfile, fedora, rails, ruby

Research direction

Start by locating the Fedora image Dockerfile and inspect where VERSION=0 is declared. Reproduce the behavior with bin/rails db:migrate VERSION=20080906120000, then verify how the image environment affects the migration target. Done means migrations no longer unexpectedly revert to version 0 when run in the Fedora image.

Written by the indexing model from the issue text.

Description

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

Dominant language
Shell
Stars
54
Forks
156
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sclorg/s2i-ruby-container

All issues in sclorg/s2i-ruby-container

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.