You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/upgrading/upgrade/_sysvm_restart.rst
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,9 +52,18 @@ in the system VMs.
52
52
With respect to VRs, a network restart without cleanup is initiated to during live patching to ensure all rules
53
53
are re-applied.
54
54
55
-
**NOTE:** In case there is an absolute need to upgrade the system VM template due to availability of
56
-
security patches or update in a package provided by the template, then the old workflow of recreating the system
57
-
VM will need to be followed, which would mean noticible downtime.
55
+
**NOTE:**
56
+
57
+
1. In case there is an absolute need to upgrade the system VM template due to availability of security patches,
58
+
update in a package provided by the template, or in case live-patch doesn't seem to work for any reason
59
+
then please follow the legacy method of upgrading system VMs and virtual routers by recreating the system
60
+
VM, which would mean noticible downtime.
61
+
62
+
63
+
2. There is a known limitation in the System VM / VR live patch feature. If a VPC network either doesn't have any network tiers
64
+
or has no network tier in the **Implemented** state, then live patching is skipped on the associated VPC VR(s). In such a case, use the traditional workflow
65
+
of upgrading the system VMs and virtual routers - by either restarting the corresponding network with cleanup, or restarting the system VMs.
66
+
58
67
59
68
Following matrix lists the versions of CloudStack that support live patching.
0 commit comments