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/MySQL.rst
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,12 @@
14
14
under the License.
15
15
16
16
|MySQL upgrade problems|
17
-
When upgrading newer CloudStack versions on older MySQL versions, some of the upgrade scripts may not apply fully on the database and some changes may be missing in the resulting installation.
17
+
Users who may upgrade their MySQL server after upgrading to Apache CloudStack 4.15 or later, may need to run the following SQL query to fix an issue with "cloud.nics" table's column type which may lead to exception seen in the management server logs. Users who have already upgraded their MySQL server prior to upgrading to Apache CloudStack 4.15 may not need this as this query runs as part of the 4.14.x to 4.15.0.0 database upgrade path.
18
18
19
-
Some versions of MySQL may not apply a SQL statement such as below which can be executed manually by the admin post-upgrade:
20
19
.. parsed-literal::
21
20
ALTER TABLE nics MODIFY COLUMN update_time timestamp DEFAULT CURRENT_TIMESTAMP;
22
21
23
-
After the upgrade of CloudStack, when some versions of MySQL are upgraded they may require additional corrective SQL queries to applied manually to fix the schema such as those around altering column types as illustrated above.
22
+
The issue is known to affect the following MySQL server versions:
0 commit comments