Skip to content

Commit b13638a

Browse files
doc: add upgrade documentation
1 parent 0519d99 commit b13638a

File tree

2 files changed

+30
-35
lines changed

2 files changed

+30
-35
lines changed

charts/splunk-connect-for-snmp/templates/mongodb-6.0-upgrade-job.yaml

Lines changed: 0 additions & 34 deletions
This file was deleted.

docs/troubleshooting/general-issues.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,4 +26,33 @@ If the `mongo-fcv-upgrade-to-6` job fails for any reason, there are two recovery
2626
db.adminCommand( { setFeatureCompatibilityVersion: "6.0" })
2727
```
2828
29-
Replace `<mongodb-pod-id>` with the actual Pod ID of your MongoDB instance.
29+
Replace `<mongodb-pod-id>` with the actual Pod ID of your MongoDB instance.
30+
31+
32+
### Upgrading SC4SNMP from 1.12.3 to 1.13.0
33+
34+
When upgrading SC4SNMP from version `1.12.3` to `1.13.0`, the subchart version of MongoDB will be updated from `15.6.26` to `16.5.9`. This upgrade requires an increase in the MongoDB `Feature Compatibility Version (FCV)` from `6.0` to `7.0`.
35+
36+
To facilitate this change, a new pre-upgrade job has been introduced in SC4SNMP: `mongo-fcv-upgrade-to-7`. This job automatically updates the Feature Compatibility Version on MongoDB before the installation of MongoDB version `16.5.9`.
37+
38+
#### Pre-Upgrade Job: `mongo-fcv-upgrade-to-7`
39+
40+
- The `mongo-fcv-upgrade-to-7` job is designed to ensure compatibility by running the FCV update prior to upgrading MongoDB.
41+
42+
#### Handling Job Failures
43+
44+
If the `mongo-fcv-upgrade-to-7` job fails for any reason, there are two recovery options:
45+
46+
1. **Reinstall SC4SNMP**:
47+
48+
[Reinstall SC4SNMP](../../microk8s/sc4snmp-installation#restart-splunk-connect-for-snmp) with **Persistent Volume Claim (PVC) deletion**.
49+
50+
2. **Manually Update MongoDB**:
51+
52+
[Update MongoDB's Feature Compatibility Version](https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-standalone/#upgrade-procedure) manually by executing the following command:
53+
```bash
54+
microk8s exec -it pod/<mongodb-pod-id> -n sc4snmp mongosh
55+
db.adminCommand( { setFeatureCompatibilityVersion: "7.0", confirm: true })
56+
```
57+
58+
Replace `<mongodb-pod-id>` with the actual Pod ID of your MongoDB instance.

0 commit comments

Comments
 (0)