Bug ID 758542: OAuth database instance appears empty after upgrade from v13.x

Last Modified: Jul 03, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM, Install/Upgrade(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6

Fixed In:
15.0.0

Opened: Feb 12, 2019
Severity: 3-Major

Symptoms

The database from a prior configuration does not seem to have any tokens. The tokens are being stored in a new database with a different name.

Impact

Old database seems to have lost tokens. In the case of these two database instances: oauthdb oauthdbprod Because the name 'oauthdb' is also present in the name 'oathdbprod', the system creates a new database instance of 'oauthdb' at upgrade, so oauthdb will have an empty database.

Conditions

Upgrade from v13.x. -- The name of one OAuth database instance is duplicated entirely in another instance name (for example, 'oauthdb' and 'oauthdbprod').

Workaround

Before upgrading, do the following: 1) Copy database oauth to another database with a completely different name. 2) Copy tokens in new database to the old, empty database.

Fix Information

The new database instance is no longer created created, so the old database now retains tokens after upgrade.

Behavior Change