Bug 714588 – dev-db/mongodb - possibility to prevent upgrade unless FeatureCompatibilityVersion is correctly set

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Jaco Kroon 2020-03-24 21:44:56 UTC]

Would it be possible to use pkg_prtend to check currently running mongodb to appropriate FeatureCompatibilityVerion and refuse to upgrade if not correctly set?

I note there is a simple ewarn in there ... well, I missed it.  And it took me from 3.4 to 4.0 ... and only 3.6 and 4.0 still in the tree so I now have no way to set featureCompatibilityVersion to 3.4 before upgrading to 3.6 ...

I'll sort that out (I'll dig out the previous stable 3.4 ebuild from git archives), but perhaps this would help in avoiding future breakage both for myself and others.  Not sure if it's possible.  Obviously mongodb has to be running to be able to do the check ... but if it it running and the vars aren't set, I suggest bailing rather than going with a mere ewarn.

Reproducible: Always

[Comment 1 Jaco Kroon 2020-04-12 21:00:06 UTC]

Hi,

Been doing some investigations of my own.  So far, assuming that the server is running, I'm able to extract the featureCompatibilityVersion:

mongo --quiet --eval "db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )"

There are obviously a bunch of issues with this:

cross-compiles.
daemon isn't running.

As such I'm not sure this is a viable goal, but I do still think that some kind of pre-merge check is in order.

[Comment 2 Ultrabug 2020-05-18 17:12:22 UTC]

I understand your frustration and problem Jaco and I'm sorry about that but I really don't think that packaging should cover such sysadmin problems

As you say it yourself, there's too little we can do for justifying the effort on mainline ebuild

Thanks for proposing and trying out!