Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1359032

Summary:	Upgrade to Rails 4.1.6+
Product:	Red Hat Software Collections	Reporter:	Lukas Zapletal <lzap>
Component:	rubygem-rails	Assignee:	ruby maint <ruby-maint>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rh-ror41	CC:	bbuckingham, ehelms, fabian, hhorak, vondruch
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	2.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-09 07:31:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1357583

Description Lukas Zapletal 2016-07-22 06:59:51 UTC

It fixes possible problems for STI (discovery plugins):

https://github.com/rails/rails/commit/257d65ed2ceb14dca6b1319355ed4f8a73540498

Here is the associated issue: https://github.com/rails/rails/issues/14785

As it was described in:

https://bugzilla.redhat.com/show_bug.cgi?id=1357583

This is data integrity bug, high importance, z-stream candidate.

Comment 2 Eric Helms 2016-07-28 17:09:18 UTC

Rails is provided by RHSCL and bugs relating to updating the version in a particular SCL should be directed there I feel given they maintain the SCL and patch levels on top.

Comment 4 Vít Ondruch 2016-07-29 11:31:20 UTC

I don't think that update to Rails 4.1.6+ is feasible, but I think that applying the patch linked in comment #1 should be doable.

Nevertheless, would you mind to elaborate what is the impact of the issues, to help us prioritize? From the bug 1357583, I'd say that you have workaround in place ...

Comment 5 Honza Horak 2016-07-29 11:40:04 UTC

Removing devel_ack set from previous team.

Comment 7 Lukas Zapletal 2016-08-09 07:31:12 UTC

You are right, Vít. We have a workaround in 6.2. I thought you regularly upgrade but it looks like you only backport security issues. Therefore we can close it.