OPERATIONAL DEFECT DATABASE
...
...
When setting a new primary key after upgrading from an older release (such as 1.1.1 or older), where tenants are deployed, to 1.5.0 or newer, the key migration may fail. The migration failure may cause configuration database corruption for the entire system.
Setting a new primary key may fail. When this failure occurs, system configuration corruption may occur.
Tenants are deployed on release 1.1.1 or older. Upgrade to 1.5.0 or newer (including through intermediate upgrades, such as 1.1.1 -> 1.3.2 -> 1.5.1). Set new primary key.
Mitigation to prevent failure: - Change all tenants to the configured state - Set a new primary key - Wait for key migration to complete - Return tenants to deployed state. Recovery for corruption: - Reset device to default configuration - Set the primary key to the known primary key for a known-good backup - Restore with known-good backup
Fix known causes of database corruption on primary key migration failure. While the primary key configuration may still fail if tenants are in deployed state, it should no longer cause system corruption.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
