Description of problem: migration: closing connection to clustered nodes fails after migration Version-Release number of selected component (if applicable): JON 3.2 ER1 How reproducible: 1 out of 2 (very occasionally) Steps to Reproduce: 1. install jon 3.1.2 GA with server and agent in IP1 2. install jon 3.1.2 GA agent in IP2 3. upgrade server and both agents to jon 3.2 ER1 4. install storage nodes on both IP1 and IP2 5. run migration for from postgres to both cassandra storage nodes by the following command: --cassandra-hosts=IP1,IP2 --cassandra-user=rhqadmin --cassandra-password=rhqadmin --cassandra-port=9142 --sql-port=5432 --sql-server-type=postgres --sql-db=rhq --estimate-only=false -X Actual results: connection shut down fails -> http://d.pr/f/ub56 Expected results: migration and connection shut down works without exceptions in log. Additional info:
Moving to unspecified target milestone as only JON 3.2.0 'blockers'(https://url.corp.redhat.com/bz-jon32-blockers-list-notmodified-nodocs) will make it into subsequent builds after ER5.
I think this should probably be retested against 3.3 given changes to the migrator in the last year. Setting ON_QA.
Created attachment 944580 [details] migration.log
verified in JON 3.3 ER04