Created attachment 938096 [details] operation_failed_exception Description of problem: take snapshot failure exception for down storage Version-Release number of selected component (if applicable): JON 3.3 ER02 How reproducible: always Steps to Reproduce: 1. JON server with agnet and storage installed and running 2. Remote storage node with agent installed and connected to jon server 3. Stop one of the storage nodes 4. Schedule take snapshot operation with delete last 2 snapshots Actual results: After step2. Take snapshot operation failed with "rg.mc4j.ems.connection.EmsException: Could not load attribute value null" exception with stack trace No new snapshot is created All existing snapshots stayed Expected results: Take snapshot operation failed with meaningfull error message without a stack trace No new snapshot is created All existing snapshots stayed Additional info: screenshot and stack trace attached
Created attachment 938097 [details] exception_stack_trace
master commit ad994cbe0c0056fb9c803d97fcd8625f0d2cbf3b Author: Libor Zoubek <lzoubek> Date: Wed Sep 17 17:12:51 2014 +0200 Bug 1142356 - take snapshot failure exception for down storage We now detect storage service availability prior running operation
branch: release/jon3.3.x link: https://github.com/rhq-project/rhq/commit/ae5ff7fcf time: 2014-09-17 17:32:31 +0200 commit: ae5ff7fcf3e226292399d386e1216564d7d24173 author: Libor Zoubek - lzoubek message: Bug 1142356 - take snapshot failure exception for down storage We now detect storage service availability prior running operation (cherry picked from commit ad994cbe0c0056fb9c803d97fcd8625f0d2cbf3b) Signed-off-by: Jirka Kremser <jkremser>
Moving to ON_QA as available for test with build: https://brewweb.devel.redhat.com/buildinfo?buildID=388959
Created attachment 943492 [details] snapshot_operation_storage_down
verified in JON 3.3 ER04 screen-shot attached