Closed oscarfonts closed 9 years ago
This is a very usual problem when configuring a flow and running a first update: third time I face it.
Something prevents mosaic creation, but GeoBatch says all is OK. Users won't know what happened or how to solve it.
Need to: a) log clearly the cause message (propagate the message from geoserver call), b) force flow failure, c) set the GeoStore database to its previous state (now it is inconsistent, it appears as the LayerUpdate has been ingested, but it's not in GeoServer).
This time the error cause was no write permission in GeoServer mosaic dir. Ingestion flow log, showing all is OK:
Current action event: 20121026T102326873UTC Progressing 90.0% -- Moving original data [UNREDD_ingestion_flow] Current action event: 20121026T102326874UTC Completed 100.0% -- Moving original data [UNREDD_ingestion_flow] Current action event: 20121026T102326875UTC Progressing 100.0% -- Action successfully completed [UNREDD_ingestion_flow]
For fix this issue is needed a new GB release (or obviously add a snapshot dependency)
Wrong issue closure
Created a new branch with improved exception handling in imageMosaicAction. when that branch will be merged into a tagged GB version, upgrade the related nfms-geobatch dependency.
GeoBatch says ingestion went OK, but:
-- Error in ImageMosaic: Error creating the new store: forest_mask [UNREDD_ingestion_flow]
Make ingestion flow fail when ImageMosaic is not created.