Skip to content

minor copy edits #779

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

minor copy edits #779

wants to merge 1 commit into from

Conversation

kay-kim
Copy link
Contributor

@kay-kim kay-kim commented Mar 23, 2013

No description provided.

@tychoish
Copy link
Contributor

merged and pulished

@tychoish tychoish closed this Mar 23, 2013
mongo-cr-bot pushed a commit that referenced this pull request Mar 11, 2022
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jun 16, 2025
GitOrigin-RevId: e9a3b05b37f0e9516c617e0c37ca5ea58dd7b4fb

Co-authored-by: apix-bot[bot] <168195273+apix-bot[bot]@users.noreply.github.com>
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jul 1, 2025
## Description

The ticket requests to add additional info on resolving pre-flight
checks failure when upgrading from v4.2, but there's an existing warning
in the [Upgrade Ops
Manager](https://www.mongodb.com/docs/ops-manager/current/tutorial/upgrade-ops-manager/)
that states that "Ops Manager 8.0 doesn't support MongoDB 4.2 and
earlier.":

> Ops Manager 8.0 doesn't support MongoDB 4.2 and earlier. If you're
using MongoDB 4.2 or earlier and want to upgrade to Ops Manager 8.0, you
must upgrade to at least MongoDB 4.4. If you don't upgrade to at least
MongoDB 4.4, Ops Manager fails [pre-flight
checks](https://www.mongodb.com/docs/ops-manager/current/tutorial/resolve-pre-flight-check/#std-label-fix-local-mode-start-failure)
and won't start. After upgrading to at least MongoDB 4.4, we still
recommend that you upgrade to at least MongoDB 6.0 before upgrading to
Ops Manager 8.0.

I'm including the note in the [Resolve Pre-flight Check
Failure](https://www.mongodb.com/docs/ops-manager/current/tutorial/resolve-pre-flight-check/)
so that users are aware of the reason for failure and that they should
be upgrading to at least v4.4.

## Jira Ticket

- [DOCSP-45626](https://jira.mongodb.org/browse/DOCSP-45626)

## Staging

-
[STAGING](https://deploy-preview-779--docs-ops-manager.netlify.app/tutorial/resolve-pre-flight-check/)

- [LATEST BUILD
LOG](https://app.netlify.com/sites/docs-ops-manager/deploys/67d0807e0a9ea200082689f7)

### Self-Review Checklist

- [ ]
[Define](https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions)
taxonomy
[values](https://wiki.corp.mongodb.com/display/DE/Docs+Taxonomy) at top
of page.
- [ ] Add genre facets (tutorial or reference), as in this [example
PR](10gen/cloud-docs#5042).
- [ ] Add programmingLanguage (if necessary).
- [ ] Add meta keywords (if necessary).
- [x] Resolve any new warnings or errors in the build.
- [x] Proofread for spelling and grammatical errors.
- [x] Check staging for rendering issues.
- [x] Confirm links are working.
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jul 22, 2025
* DOCPS-31571: Add upgrade information

* small changes

* wording

* feedback fixes

* vale fix

* adding clarifying info
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jul 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants