If we start cinderlib from the N release with the DBMS persistence plugin on a DB where we have already run it with release N+1 then we'll get an `oslo_db.exception.DBMigrationError` exception. This is because cinderlib automatically does a `db_sync` on each initialization, but on N this will fail because there will be unknown (as in newer) migrations applied to the DB. This patch takes this possibility and checks the exception raised by `db_sync` and ignores it if the `migrate` package complains with a VersionNotFoundError. Closes-Bug: #1868145 Change-Id: I539919e01f603d19cde8750ad92e3d2b4ac2fbc7
		
			
				
	
	
		
			7 lines
		
	
	
		
			180 B
		
	
	
	
		
			YAML
		
	
	
	
	
	
			
		
		
	
	
			7 lines
		
	
	
		
			180 B
		
	
	
	
		
			YAML
		
	
	
	
	
	
---
 | 
						|
fixes:
 | 
						|
  - |
 | 
						|
    Bug #1868145: Support rolling upgrades with the DBMS persistence plugin.
 | 
						|
    Can run an N release version even if we have already run once an N+1
 | 
						|
    release.
 |