Update source/release-notes/2.4-upgrade.txt #638
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
QA testing by mike - he seemed to think this was confusing as written and implied that only mongos processes needed to be upgraded
mongo-cr-bot
pushed a commit
that referenced
this pull request
Feb 15, 2022
* Docs 15079 md5 usage in scram sha 1 (#612) * DOCS-15079-md5-usage-in-SCRAM-SHA-1 * DOCS-15079-md5-usage-in-SCRAM-SHA-1 * DOCS-15079-md5-usage-in-SCRAM-SHA-1 * DOCS-15079-md5-usage-in-SCRAM-SHA-1 * DOCS-15079-md5-usage-in-SCRAM-SHA-1 * DOCS-15079-md5-usage-in-SCRAM-SHA-1 Co-authored-by: jason-price-mongodb <[email protected]> * DOCS-15079-md5-usage-in-SCRAM-SHA-1 Co-authored-by: jason-price-mongodb <[email protected]>
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
May 22, 2025
* added note about ORR and embedded verification * moved tp behavior section
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 9, 2025
* DOCSP-39552-keyboard-update * DOCSP-39552-keyboard-update --------- Co-authored-by: jason-price-mongodb <[email protected]>
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 16, 2025
* (DOCSP-18640) Add update steps for new versions
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 23, 2025
* (DOCSP-18640) Add update steps for new versions
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 1, 2025
…ng (#638) 1. The current command listed for upgrading the broken packages should be changed from using --force to rpm -Uvh --oldpackage for safety in the 6.0, 7.0, and 8.0 documentation 2. This command is in the install and upgrade documentation, perhaps it should also be in the release notes for the next version after the affected versions 3. 8.0.0 was also built incorrectly so it needs to be added to the list in the 8.0 docs ([HELP-67044](https://jira.mongodb.org/browse/HELP-67044)) - [DOCSP-45143](https://jira.mongodb.org/browse/DOCSP-45143) - [STAGING - install OM](https://deploy-preview-638--10gen-docs-ops-manager.netlify.app/tutorial/install-on-prem-with-rpm-packages/#install-onprem) - [STAGING - 7.0 release notes](https://deploy-preview-638--10gen-docs-ops-manager.netlify.app/release-notes/application/#onprem-platform-support-1) - [STAGIN - 8.0 release notes](https://deploy-preview-638--10gen-docs-ops-manager.netlify.app/release-notes/application/#onprem-server-8.0.1) - [LATEST BUILD LOG](https://app.netlify.com/sites/10gen-docs-ops-manager/deploys/6785407c35f55b000878f8e8) ### 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). - [ ] Resolve any new warnings or errors in the build. - [ ] Proofread for spelling and grammatical errors. - [ ] Check staging for rendering issues. - [ ] Confirm links are working.
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 1, 2025
…ng-v7.0-backport (638) (#659) # Backport This will backport the following commits from `master` to `v7.0`: - [(DOCSP-45143) 8.0.0 upgrade issue and other fixes for older rpm warning (#638)](10gen/docs-ops-manager#638) <!--- Backport version: 9.6.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 1, 2025
…ng-v8.0-backport (638) (#658) # Backport This will backport the following commits from `master` to `v8.0`: - [(DOCSP-45143) 8.0.0 upgrade issue and other fixes for older rpm warning (#638)](10gen/docs-ops-manager#638) <!--- Backport version: 9.6.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 1, 2025
…ng-v6.0-backport (638) (#662) # Backport This will backport the following commits from `master` to `v6.0`: - [(DOCSP-45143) 8.0.0 upgrade issue and other fixes for older rpm warning (#638)](10gen/docs-ops-manager#638) - [Staging](https://deploy-preview-662--10gen-docs-ops-manager.netlify.app/tutorial/install-on-prem-with-rpm-packages/) - [Deploy Log](https://app.netlify.com/sites/10gen-docs-ops-manager/deploys/67867eb9fda59e000819044d) <!--- Backport version: 9.6.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 11, 2025
* dashboard section ia revamp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
QA testing by mike - he seemed to think this was confusing as written and implied that only mongos processes needed to be upgraded