Description of problem: long running sequence of sql queries initiated when a new appliance tries to insert itself into the VMDB timesout and the appliance is not associated with VMDB. Version-Release number of selected component (if applicable):5.5.0.13 How reproducible: UNCERTAIN Steps to Reproduce: 1. 2. 3. Actual results: multiple attempts to add a fourth appliance into an existing VMDB complex all fail with timeouts trying to add the new appliance into the VMDB. Expected results: new appliance should be added into existing complex Additional info: a long running set of queries about various tables and relations are running longer than 5 minutes and evoke a timeout from the evm.log file. Customer modified to sql configuration file to capture all sql queries which are included in the attached set of logs. A few items of note: - Region # = 80. References to record ids that follow will assume that key prefix. - first appliance is added with a key of '1' - second appliance is added with a key of '2' - third appliance added days after initial migration of database is added with a key of '634' - the above gap in keys suggest that there is some kind of updating of the sequence field associated with the miq_servers table that may shed some light on what is happening. - two key log sets from two appliances are provided: one from database owing appliance including postgresql.log referenced above and one from the appliance attempting to insert itself into the VMDB and timeout out. - a copy of the database has been requested.
*** This bug has been marked as a duplicate of bug 1294907 ***