Skip to content

Commit e8029d3

Browse files
Merge pull request #248457 from robswain/upgrade-note
remove old upgrade note
2 parents 970f6ca + c1f8f5a commit e8029d3

File tree

2 files changed

+1
-7
lines changed

2 files changed

+1
-7
lines changed

articles/private-5g-core/upgrade-packet-core-arm-template.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -129,9 +129,6 @@ In this step, you'll roll back your packet core using a REST API request. Follow
129129

130130
If any of the configuration you set while your packet core instance was running a newer version isn't supported in the version that you want to roll back to, you'll need to revert to the previous configuration before you're able to perform a rollback. Check the packet core release notes for information on when new features were introduced.
131131

132-
> [!NOTE]
133-
> You can roll back your packet core instance to version [PMN-2211-0](azure-private-5g-core-release-notes-2211.md) or later.
134-
135132
1. Ensure you have a backup of your deployment information. If you need to back up again, follow [Back up deployment information](#back-up-deployment-information).
136133
1. Perform a [rollback POST request](/rest/api/mobilenetwork/packet-core-control-planes/rollback?tabs=HTTP).
137134

articles/private-5g-core/upgrade-packet-core-azure-portal.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -118,9 +118,6 @@ If you encountered issues after the upgrade, you can roll back the packet core i
118118

119119
If any of the configuration you set while your packet core instance was running a newer version isn't supported in the version that you want to roll back to, you'll need to revert to the previous configuration before you're able to perform a rollback. Check the packet core release notes for information on when new features were introduced.
120120

121-
> [!NOTE]
122-
> You can roll back your packet core instance to version [PMN-2211-0](azure-private-5g-core-release-notes-2211.md) or later.
123-
124121
1. Ensure you have a backup of your deployment information. If you need to back up again, follow [Back up deployment information](#back-up-deployment-information).
125122
1. Navigate to the **Packet Core Control Plane** resource that you want to roll back as described in [View the current packet core version](#view-the-current-packet-core-version).
126123
1. Select **Rollback version**.
@@ -132,7 +129,7 @@ If any of the configuration you set while your packet core instance was running
132129
:::image type="content" source="media/upgrade-packet-core-azure-portal/confirm-rollback.png" alt-text="Screenshot of the Azure portal showing the Confirm rollback field in the Rollback packet core screen.":::
133130

134131
1. Select **Roll back packet core**.
135-
1. Azure will now redeploy the packet core instance at the new software version. You can check the latest status of the rollback by looking at the **Packet core installation state** field. The **Packet Core Control Plane** resource's overview page will refresh every 20 seconds, and you can select **Refresh** to trigger a manual update. The **Packet core installation state** field will show as **RollingBack** during the rollback and update to **Installed** when the process completes.
132+
1. Azure will now redeploy the packet core instance at the previous software version. You can check the latest status of the rollback by looking at the **Packet core installation state** field. The **Packet Core Control Plane** resource's overview page will refresh every 20 seconds, and you can select **Refresh** to trigger a manual update. The **Packet core installation state** field will show as **RollingBack** during the rollback and update to **Installed** when the process completes.
136133
1. Follow the steps in [Restore backed up deployment information](#restore-backed-up-deployment-information) to reconfigure your deployment.
137134
1. Follow the steps in [Verify upgrade](#verify-upgrade) to check if the rollback was successful.
138135

0 commit comments

Comments
 (0)