Bug 1549025 - MongoDB does not work on i686 properly
Summary: MongoDB does not work on i686 properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mongodb
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Skalický
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-26 09:31 UTC by Vít Ondruch
Modified: 2018-03-15 13:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 13:04:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2018-02-26 09:31:00 UTC
Description of problem:
Recently, there were some rebuild issues of rubygem-mongodb reported by Koschei:

https://apps.fedoraproject.org/koschei/package/rubygem-mongo?collection=f28
https://apps.fedoraproject.org/koschei/package/rubygem-mongo?collection=f29

It seems that when the issue happens, the build is done on i686. I just tried two rebuild on i686 and they both failed:

https://koji.fedoraproject.org/koji/taskinfo?taskID=25316483
https://koji.fedoraproject.org/koji/taskinfo?taskID=25316520

While the x86_64 build passed:

https://koji.fedoraproject.org/koji/taskinfo?taskID=25316529

The error in the test suite is always the same:

~~~
      Mongo::Error::OperationFailure:
        Majority read concern requested, but it is not supported by the storage engine. (148)
~~~

So what does it mean? What is different on i686 comparing to other architectures?

Comment 1 Jun Aruga 2018-02-26 11:15:49 UTC
I think this looks working again now.

On F28 the build is success now seeing the Koschei URL.

On F29 I did scratch build now: and the build is success. 
https://koji.fedoraproject.org/koji/taskinfo?taskID=25318023

Comment 2 Jun Aruga 2018-02-26 12:15:57 UTC
Sorry when running "fedpkg build" on F29 now, I got the error.
https://koji.fedoraproject.org/koji/taskinfo?taskID=25318984

Comment 3 Vít Ondruch 2018-02-26 13:54:00 UTC
(In reply to Jun Aruga from comment #1)
> I think this looks working again now.
> 
> On F28 the build is success now seeing the Koschei URL.

rubygem-mongo is noarch package. Any architecture can be picked up. It appears to build on every architecture except i686.

> On F29 I did scratch build now: and the build is success. 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=25318023

This build happened on x86_64, therefore it passed.

(In reply to Jun Aruga from comment #2)
> Sorry when running "fedpkg build" on F29 now, I got the error.
> https://koji.fedoraproject.org/koji/taskinfo?taskID=25318984

And this build was done on i686, therefore it failed.

Comment 4 Marek Skalický 2018-02-27 10:31:00 UTC
'To use read concern level of "majority", replica sets must use WiredTiger storage engine and election protocol version 1.' (https://docs.mongodb.com/manual/reference/read-concern/)

WiredTiger is newer storage storage engine - currently the only one supported. And it operating only on 64bit architectures.
32bit arches have only older mmapv1 storage engine. So that is the reason why this test fails on i686 (it should also on armv7). I don't see any other solution than disabling this test on 32bit arches.

Reason:
MongoDB upstream support only x86_64, ppc64le, s390x and aarch64 arches. Other arches are Fedora specific and are supported only on "community basis" (~till it works and it's not too complicated to keep it building).

Comment 5 Marek Skalický 2018-02-27 12:20:17 UTC
I guess this commit adds the failure - https://github.com/mongodb/mongo-ruby-driver/commit/f65307910c6051136e90add5c27bc2628bddc88a#diff-4906c50584ac6309174a82dbfb3a6ded (it add more testing scenarios)

So 2.5.0 and 2.5.1 are affected.

Comment 6 Vít Ondruch 2018-02-27 14:03:45 UTC
Aha, so the rubygem-mongo-2.5.0-1.fc28 got into Fedora on 2018-02-16 and then we started to observer the build failures.

May be we should consider adding something like https://pagure.io/packaging-committee/issue/751 into rubygem-mongo

Comment 7 Marek Skalický 2018-02-27 14:42:52 UTC
(In reply to Vít Ondruch from comment #6)
> May be we should consider adding something like
> https://pagure.io/packaging-committee/issue/751 into rubygem-mongo

+1

Comment 8 Marek Skalický 2018-03-15 13:04:51 UTC
If there is anything new, feel free to reopen.


Note You need to log in before you can comment on or make changes to this bug.