AWS elemental-cl3 documentation change
Summary
Added explicit steps to run prepare_for_downgrade.sh script and adjusted step numbering in downgrade procedures
Security assessment
Changes focus on procedural improvements for downgrade operations, adding a preparation script step. No mention of security vulnerabilities, patches, or security features. The script appears to be part of standard downgrade preparation rather than addressing security concerns.
Diff
diff --git a/elemental-cl3/latest/upgradeguide/downgrades-cl3-upg-dg-cond.md b/elemental-cl3/latest/upgradeguide/downgrades-cl3-upg-dg-cond.md index b7e4cbf5a..aac1d4851 100644 --- a/elemental-cl3/latest/upgradeguide/downgrades-cl3-upg-dg-cond.md +++ b/elemental-cl3/latest/upgradeguide/downgrades-cl3-upg-dg-cond.md @@ -28 +28,5 @@ When you downgrade, run the installer with the `--downgrade` option for each nod - 3. Run the installer as follows. For example: + 3. Run the prepare for the downgrade script: + + [elemental@hostnmae ~]$ **sudo /opt/elemental_se/web/script/prepare_for_downgrade.sh -i ./elemental_production_conductor_live247_3.23.5.12345.run** + + 4. Run the installer as follows. For example: @@ -44 +48 @@ Options are as follows: - 4. Reboot the node with the following command: + 5. Reboot the node with the following command: @@ -48 +52 @@ Options are as follows: - 5. Make sure that elemental_se restarts on this node; otherwise, you will not be able to downgrade the secondary Conductor Live node. Look for this prompt on the primary Conductor Live command line: + 6. Make sure that elemental_se restarts on this node; otherwise, you will not be able to downgrade the secondary Conductor Live node. Look for this prompt on the primary Conductor Live command line: @@ -52 +56 @@ Options are as follows: - 6. Refresh your web browser in order to load the updated web interface. + 7. Refresh your web browser in order to load the updated web interface. @@ -74 +78,5 @@ If you have worker node redundancy, downgrade the back-up nodes first and then t - 2. Downgrade the active worker nodes following these steps. See [AWS Elemental Live Upgrade Guide](https://docs.aws.amazon.com/elemental-live/latest/upgradeguide/) for more details. + 2. Run the prepare for downgrade script: + + [elemental@hostnmae ~]$ sudo /opt/elemental_se/web/script/prepare_for_downgrade.sh ./elemental_production_live_2.23.5.12345.run + + 3. Downgrade the active worker nodes following these steps. See [AWS Elemental Live Upgrade Guide](https://docs.aws.amazon.com/elemental-live/latest/upgradeguide/) for more details. @@ -86 +94 @@ Run the installer with the skip-all option. Use the following commands with the - 3. When the installer completes, **do not** reboot or restart! Run these two commands first: + 4. When the installer completes, **do not** reboot or restart! Run these two commands first: @@ -94 +102 @@ If you don't run these commands before rebooting, the node will boot into emerge - 4. Restart the node with the following command: + 5. Restart the node with the following command: @@ -100 +108 @@ On the Conductor Live web interface, a message appears to indicate that the node - 5. When the node has rebooted, the Conductor Live web interface displays a message to indicate that the node is back online. Refresh your web browser on the Elemental Live node to load the updated web interface. + 6. When the node has rebooted, the Conductor Live web interface displays a message to indicate that the node is back online. Refresh your web browser on the Elemental Live node to load the updated web interface. @@ -102 +110 @@ On the Conductor Live web interface, a message appears to indicate that the node - 6. Repeat the downgrade steps on each worker node before moving on to the next step in the downgrade process. + 7. Repeat the downgrade steps on each worker node before moving on to the next step in the downgrade process.