B #2687: Disk snapshots dissapearing (#448)

(cherry picked from commit 41e04c7)

Author: Vlastimil Holer

source/intro_release_notes/bug2687.txt

@@ -0,0 +1,32 @@
+.. important::
+
+    There is a `bug #2687 <https://github.com/OpenNebula/one/issues/2687>`__ in database migration script which doesn't persist the calculated next snapshot IDs for existing image and VM disk snapshots. After upgrade to 5.6.x, you have to manually apply the `database patch <https://downloads.opennebula.org/packages/opennebula-5.6.0/patches/next_snapshot.rb>`__ (MD5: b7661a3bc4fa3768e6e0ff59e698f7e9). Otherwise, the OpenNebula may lose evidence of existing image/VM disk snapshots when new a one is taken.
+
+    Steps to apply the patch:
+
+    1. **Download patch**
+
+    .. prompt:: bash $ auto
+
+         $ wget https://downloads.opennebula.org/packages/opennebula-5.6.0/patches/next_snapshot.rb
+
+    2. **Stop OpenNebula**
+
+    .. prompt:: bash $ auto
+
+         $ service opennebula stop
+
+    3. **Apply patch**
+
+    The connection parameters have to be supplied as the command line options, see the :ref:`onedb manpage <cli>` for more information.
+
+    .. prompt:: bash $ auto
+
+         $ onedb patch next_snapshot.rb [database connection parameters]
+
+
+    4. **Start OpenNebula**
+
+    .. prompt:: bash $ auto
+
+         $ service opennebula start

source/intro_release_notes/release_notes/compatibility.rst

@@ -97,6 +97,8 @@ Snapshots do not reuse snapshot IDs
 
 The snapshots structure stores the next snapshot ID. So, a new snapshot doesn't reuse an old snapshot ID, even when some are removed.
 
+.. include:: ../bug2687.txt
+
 Developers and Integrators
 ================================================================================
 

source/intro_release_notes/upgrades/upgrade_38.rst

@@ -211,6 +211,8 @@ If everything goes well, you should get an output similar to this one:
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -401,4 +403,4 @@ The workaround is to temporarily change the oneadmin's password to an ASCII stri
 
     mysql> SET PASSWORD = PASSWORD('newpass');
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_40.rst

@@ -122,6 +122,8 @@ If you receive the message “ATTENTION: manual intervention required”, read t
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -255,4 +257,4 @@ Since OpenNebula 4.4, each tm\_mad driver has a TM\_MAD\_CONF section in oned.co
     ]
 
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_410.rst

@@ -140,6 +140,8 @@ If everything goes well, you should get an output similar to this one:
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -303,4 +305,4 @@ The workaround is to temporarily change the oneadmin's password to an ASCII stri
 
     mysql> SET PASSWORD = PASSWORD('newpass');
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_412.rst

@@ -176,6 +176,8 @@ If everything goes well, you should get an output similar to this one:
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -308,4 +310,4 @@ The workaround is to temporarily change the oneadmin's password to an ASCII stri
 
     mysql> SET PASSWORD = PASSWORD('newpass');
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_414.rst

@@ -163,6 +163,8 @@ If everything goes well, you should get an output similar to this one:
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -286,4 +288,4 @@ The workaround is to temporarily change the oneadmin's password to an ASCII stri
 
     mysql> SET PASSWORD = PASSWORD('newpass');
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_42.rst

@@ -117,6 +117,8 @@ If you receive the message “ATTENTION: manual intervention required”, read t
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -250,4 +252,4 @@ Since OpenNebula 4.4, each tm\_mad driver has a TM\_MAD\_CONF section in oned.co
     ]
 
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_44.rst

@@ -106,6 +106,8 @@ If everything goes well, you should get an output similar to this one:
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -184,4 +186,4 @@ The workaround is to temporarily change the oneadmin's password to an ASCII stri
 
     mysql> SET PASSWORD = PASSWORD('newpass');
 
-.. include:: version.txt
+.. include:: version.txt

source/intro_release_notes/upgrades/upgrade_46.rst

@@ -157,6 +157,8 @@ If everything goes well, you should get an output similar to this one:
 
 .. note:: Make sure you keep the backup file. If you face any issues, the onedb command can restore this backup, but it won't downgrade databases to previous versions.
 
+.. include:: ../bug2687.txt
+
 Check DB Consistency
 ====================
 
@@ -282,4 +284,4 @@ The workaround is to temporarily change the oneadmin's password to an ASCII stri
 
     mysql> SET PASSWORD = PASSWORD('newpass');
 
-.. include:: version.txt
+.. include:: version.txt