You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
I would like to add Mongo storage engine upgrade test scenario in the current upgrade(Satellite, Capsule, and CustomerDB upgrade) workflow. There is no impact on the current workflow if we include it and will achieve both the things (upgrade and mongo DB engine upgrade) in a single attempt.
We will keep it separately in current upgrade workflow and it will be executed in end of the upgrade. Mongo DB engine upgrade treats as an optional parameter, If the user wants to test MongoDB Engine upgrade along with upgrade then pass the optional parameter(like foreman-maintain, puppet version) in the current workflow.
In this release, We have observed 8 to 9 bugs which were related to this feature.
As of now, mongo DB engine upgrades as an optional parameter of an upgrade and by default it uses MMAPv1 mongo DB engine.
The text was updated successfully, but these errors were encountered:
I would like to add Mongo storage engine upgrade test scenario in the current upgrade(Satellite, Capsule, and CustomerDB upgrade) workflow. There is no impact on the current workflow if we include it and will achieve both the things (upgrade and mongo DB engine upgrade) in a single attempt.
We will keep it separately in current upgrade workflow and it will be executed in end of the upgrade. Mongo DB engine upgrade treats as an optional parameter, If the user wants to test MongoDB Engine upgrade along with upgrade then pass the optional parameter(like foreman-maintain, puppet version) in the current workflow.
In this release, We have observed 8 to 9 bugs which were related to this feature.
As of now, mongo DB engine upgrades as an optional parameter of an upgrade and by default it uses MMAPv1 mongo DB engine.
The text was updated successfully, but these errors were encountered: